Browse documentation

Technical documentation / Reference

magi-code 0.107.0

New features

Redesigned Settings

Settings is now organized into six task groups instead of tabs, with one search box across all groups and a Browse view listing every setting. Model, tool, skill, and subagent availability are edited together as one draft for the selected scope.

How to use: Open Settings, pick a task group or type to search, and press Enter to open a result. Press Tab to move focus between the list and the footer actions. Changes stay in a draft until you save. Review shows them first, and closing Settings or switching scope with unsaved changes offers Save, Discard, or Stay. Inherited values are labeled. Overriding a value applies only to the current scope, and Reset removes that override. Catalog refresh, skill rescans, cache deletion, and MCP approvals still take effect immediately and are not part of the draft.

Beta features setting

A new beta setting, off by default, controls access to Progressive Session Maintenance (PSM) and Jev.

How to use: In Settings, open Beta features from the root list and turn on Enable beta features, or set "beta": true in Global or Project settings. While beta is off, the page shows an overview of PSM and Jev. Once it is on, their settings appear there, and all seven Jev check categories are grouped under Jev, below Enable Jev tooling.

Herdr App agent status

When used with Herdr App, magi-code now shows as idle, working, or blocked in its Agents panel. It reports blocked while waiting for you to approve a Bash command.

How to use: Set automation.integrations.herdr.enabled to true and run magi-code in a terminal started by Herdr App. No bridge installer, HERDR_ENV, or HERDR_PANE_ID is needed. If the Herdr pane-socket variables are set, pane-socket reporting still takes precedence.

Claude Code setup-token login

The claude-subscription provider now accepts a long-lived token from claude setup-token, as well as a stored claude.ai login.

How to use: Run claude setup-token, then export CLAUDE_CODE_OAUTH_TOKEN in the shell that launches magi-code. The Claude CLI picks the credential and prefers this token when both are available. magi-code never reads or stores it. Usage information is unavailable for setup-token logins. To stop using the token, unset the variable before launching.

Fixes

Other changes

Edit this page on GitHub ↗