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

MGS9013: console not built

The server answered 400 bad request to a share request because it found no built console, so a device opening the share link would load nothing.

[MGS9013] the built console was not found, so there is nothing to share; build
it with `magus run build console` and try again
  see: .../MGS9013.md

Why

A share opens a LAN listener that serves the console app to another device. The server looks for the build in MAGUS_CONSOLE_DIR, then in <root>/console/gen, and needs an index.html there. Opening a listener with nothing behind it would hand the other device a 404 in place of the app.

Resolution

Build the console with magus run build console, or point MAGUS_CONSOLE_DIR at a directory holding a built console, then start the share again. The server reads the directory when it starts, so restart it after building: magus server stop, then magus server start.

AuthPages in this section. Tokens and grantsHow the magus server decides who may use which route. Four token classes told apart by prefix, a grant of none, read or write per surface, a need declared by every procedure, one rule for minting, the trust model, and what the activity trail records about each. MGS9001: bearer token rejectedThe server refused a request because the bearer token it carried was wrong, expired, or revoked. This is the usual reason an MCP client cannot connect. MGS9007: host not allowedThe server refused a request whose Host or Origin header names a host it does not serve. This is the DNS-rebinding guard.
MGS9013authconsoleshare400
Last updated (95680f58)
Earlier changes on this page (1)

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.

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.

Console app

One of the console's applications (Runs, Log Viewer, Graph Explorer, Dashboard, Activity Trail, Settings). "App" rather than "page" because one is never a document you navigate to: it is mounted into a tab, or into a pane beside another one. Each is single-instance - opening one you already have focuses it instead of duplicating it.

The glossary term is two words on purpose. As a bare "App" the auto-linker matched every unrelated "app" in the docs - a ChatGPT desktop app, a Postgres app - and pointed each at this definition. See reference/console.

Conventions

Placeholders

Angle brackets mark a value you replace with your own - never type the brackets:

magus run <target>
magus completion <shell>    # e.g. bash, zsh, fish

<target>, <path>, <shell>, <name> and the like are stand-ins, not literal text.