magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

MGS9004: no auth token configured

A command needed the operator (cli) token - the built-in credential the local CLI and server authenticate with - but none has been created yet.

[MGS9004] no token configured; run `magus config mcp token generate`
  see: .../MGS9004.md

Why

The operator token is auto-seeded the first time the server starts. Before that (a fresh install where the server has never run), there is nothing to print or authenticate with.

Resolution

Either start the server once (it mints the token), or generate it explicitly:

magus config mcp token generate

Then re-run your command.

What this is NOT

  • Not a connector-token problem. Connector tokens (for MCP clients) are a separate store; this is the built-in operator credential. See MGS9001 for a rejected connector token.

See also

  • magus config mcp token: print or generate the operator token.
  • magus server start: starts the server, which seeds the token.
AuthPages in this section. The CLI in practiceThe magus subcommands you actually reach for, grouped by the question you are asking, with the quirks that are not obvious from the help text. magus affectedRun a target for every project affected by a VCS diff, with forensic modes for explain, graph, CI shard plan, and regression bisect. magus brokerCheck or stop the broker: the per-user process that holds this host's concurrency slots, declared memory and shared services, which a run starts on its own.
MGS9004authtokenclioperatoronboarding
Last updated (95680f58)
Earlier changes on this page (2)

Full history ↗ · Blame source ↗

Glossary

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). See operations.

Server

The background process a person starts with magus server start. It serves MCP, the console, background jobs and the warm knowledge graph, and adopts nested magus calls into one pool. See server.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.