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

MGS3033: buzz transform failed

The message following the code names the failed part of the request or includes the Buzz compiler/runtime diagnostic.

What to do

  • Supply exactly one of script or path, and pass JSON data through input.
  • Define transform(input: any, args: [str]) and return a JSON-encodable value.
  • Fix any nested BZZ#### compiler or import diagnostic first.
  • File imports, native FFI, and workspace-changing host modules are not offered by this MCP transform. Workspace queries and actions go through the client tool. Use the regular magus buzz CLI for scripts that need the rest of the host.
  • If the worker reports an invalid response, report it as a Magus bug with the diagnostic and server version.
Sandbox diagnosticsLanding page for the sandbox that confines magus spells to the workspace, plus its MGS2xxx diagnostics for denied reads, writes, execs, and env leaks. magus buzzRun Buzz from a REPL, a file, stdin, or an inline snippet, with the Buzz stdlib, every magus host module, and the magus namespace available. ADR 0005: deterministic answersThe v0.5.0 finishing pass, recorded in full. A stalled multi-agent change showed where agents improvise and where magus stays silent. The person drives; magus answers from the graph, the job store and typed APIs, and prints what to run. Every idea and use case raised during the pass is listed here with its state, so this page is also the plan. magus documentationThe magus documentation hub covering install, targets, spells, charms, operations, engines, remote caching, MCP, telemetry, and the interactive playground.
MGS3033mcpbuzztransform
Last updated (2064080d)
Glossary

Workspace

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

Module

A magus stdlib namespace a magusfile imports for host capabilities: filesystem, exec, vcs, and more. See the module reference.

Buzz

The language magusfiles are written in (the .buzz engine). See engines.

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.

Conventions

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