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

MGS9010: console file withheld

The server answered 404 not found for a path under /console/ that is not part of the console's app shell.

[MGS9010] the console mount serves only the app shell; read data through the
authenticated API
  see: .../MGS9010.md

Why

/console/ is served without a token so the app can load and then ask for one. The console build directory also holds files that are not the shell, such as the hosted demo's knowledge graph, and those must not reach a caller with no token. The mount serves an allowlist of shell file types (HTML, scripts, styles, fonts, images, the manifest) and answers 404 for everything else, including dotfiles, directory listings, and shell paths that do not exist.

Resolution

Read workspace data through the authenticated routes (the Connect services and /api/v1/), with a bearer token. A shell asset that should load but gets this code has an extension outside the allowlist.

MGS9010authconsolestatic404
Last updated (95680f58)
Earlier changes on this page (2)

Full history ↗ · Blame source ↗

Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Service

A long-running or shared process magus manages across runs, distinct from a one-shot target. See services.

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.

Knowledge graph

The queryable graph of a workspace's spells, targets, docs, and code relationships; query it with magus query/explain/path. See knowledge.

Conventions

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