multica-ai/multica · error
you are not logged in. Run '%s' first, then start the daemon
Error message
you are not logged in. Run '%s' first, then start the daemon
What it means
Error "you are not logged in. Run '%s' first, then start the daemon" thrown in multica-ai/multica.
Source
Thrown at server/cmd/multica/cmd_daemon.go:537
// requireDaemonAuth fails fast when the user never ran `multica login`. The
// daemon child performs the same check (resolveAuth) and dies immediately,
// but the background parent can't see that exit — it would poll the health
// port for the full 45s readiness window and then print a vague "check logs"
// warning. Checking before spawning turns that silent stall into an
// immediate, actionable error. Mirrors daemon.resolveAuth: the daemon only
// authenticates via the stored config token, never MULTICA_TOKEN.
func requireDaemonAuth(profile string) error {
cfg, err := cli.LoadCLIConfigForProfile(profile)
if err != nil {
return fmt.Errorf("load CLI config: %w", err)
}
if cfg.Token == "" {
loginHint := "multica login"
if profile != "" {
loginHint = fmt.Sprintf("multica login --profile %s", profile)
}
return fmt.Errorf("you are not logged in. Run '%s' first, then start the daemon", loginHint)
}
return nil
}
func runDaemonStart(cmd *cobra.Command, _ []string) error {
if err := requireHumanLocalCommand("daemon start"); err != nil {
return err
}
foreground, _ := cmd.Flags().GetBool("foreground")
if foreground {
return runDaemonForeground(cmd)
}
return runDaemonBackground(cmd)
}
func runDaemonBackground(cmd *cobra.Command) error {
profile := resolveProfile(cmd)
healthPort := healthPortForProfile(profile)View on GitHub (pinned to 2c0912b6ec)
Solutions
- Run 'multica login' first, then start the daemon.
When it happens
Trigger: Thrown at server/cmd/multica/cmd_daemon.go:537 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of multica-ai/multica@2c0912b6ec (2026-08-15).
Data as JSON: /api/errors/4b0249ea8fe2154f.
Report an issue: GitHub.