Skip to main content
Run mandala with no arguments for the guided terminal. Type / to open the command palette. Commands appear only when they are valid for the current selection and work-item state. Use mandala <command> for scripts and automation. Add --json to receive a stable JSON envelope.

Authentication and workspace

Interactive equivalents include /login, /auth-status, /logout, and /workspace.

Agents

Use /agents for the guided manager. Its focused commands are: To run an active agent against real cataloged workspace data:

Sandbox and fixtures

Inbox and review

Scripted equivalents use mandala work list|inspect|show|ask|approve|edit|reject|resolve|rework|decide|execute. Mutating workflow commands require terminal confirmation. Approval or edit can also use --execute to consume the returned execution capability immediately, but the decision and execution remain separately audited.

Context and settings

Settings changes require the current configuration version and a reason. A stale version fails rather than overwriting someone else’s newer change.

Conversation

mandala chat [bounded phrase] and direct text in the interactive client route read-only questions through the contextual chat boundary. mandala parse <bounded phrase> shows how a bounded request resolves. Questions can explain work and workspace data. State changes still use the typed commands above and their confirmation checks.