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

MGS9026: server has no workspace

The server answered 503 unavailable because the route reads a workspace (insight, the target plan, a diff) and this process holds none.

[MGS9026] this server was started without a workspace
  see: .../MGS9026.md

Why

A server can run without a workspace, serving only what needs none. The console treats this answer as "render the empty state", which is why it is a 503 and not a 500. Unlike a workspace that is loading, nothing changes by waiting. A review context read whose workspace root no longer resolves answers the same way.

Resolution

Restart the server from the workspace root: magus server stop, then magus server start.

What this is not

  • Not a workspace that is loading. That is MGS3017, and the same call succeeds after a moment.
  • Not a workspace that failed to load. That is MGS3016.
AuthPages in this section. ChangelogEvery change to magus, newest first, in Keep a Changelog format, starting with the unreleased entries. Generated from changes/unreleased/ and releases/*.yaml. MCPmagus serves its tools as a Model Context Protocol server, over stdio for the agent host that launches magus mcp, or over Streamable HTTP from magus server. The broker and the servermagus runs up to two background processes. The broker holds this host's capacity and shared services and a run starts it; the server serves MCP, the console and jobs and a person starts it.
MGS9026apiworkspace503
Last updated (8b20a199)
Earlier changes on this page (1)

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.

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

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.

Sandbox

The restricted filesystem and environment a target runs in, so builds stay reproducible and side-effect-free. See sandbox.

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.

Insight

The reports magus derives over the graph and history (hotspots, affinity, ownership, trend, volatility, unreferenced). See insight.

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.