Mag Command Center

Mag Command Center is a cross-platform desktop app for managing MagAgent projects, agents, memory, plugins, and local productivity workflows.

The app is intended to be a polished UI over the installed magent CLI and the same MagAgent configuration, MagGraph memory, SQLite stores, skills, and plugins used from the terminal.

Mag Ecosystem

Mag Command Center is part of a local-first AI productivity stack:

• MagGraph — Rust-powered Markdown graph memory, search, backlinks, recall bundles, and Python bindings.
• MagAgent — terminal-native AI coding and productivity agent powered by MagGraph memory.
• Mag Command Center — cross-platform desktop app for MagAgent projects, chat, configuration, memory, plugins, and local workbench views.
• Mag ecosystem roadmap — coordinated direction for all three projects.

Goals

• Open local project folders and run project-scoped MagAgent chat sessions.
• Manage multiple projects and agent profiles from one desktop workspace.
• Configure MagAgent providers, model roles, permissions, memory, subagents, gateways, MCP, skills, and plugins without hand-editing config files.
• Browse and improve MagGraph memory nodes, backlinks, provenance, pending memory candidates, and project context.
• Explore MagAgent SQLite/workbench databases with safe read/query workflows.
• Package native desktop builds for macOS, Windows, and Linux.

Architecture Direction

Mag Command Center should treat the MagAgent CLI as the backend contract wherever possible:

• Shell out to magent commands for readiness, provider setup, model health, asks, memory, plugins, and project operations.
• Prefer JSON/machine-readable command output over importing MagAgent internals.
• Keep MagAgent config and storage as the source of truth.
• Add missing MagAgent CLI integration APIs upstream as part of MagAgent releases.

The recommended desktop stack is Tauri + React + TypeScript.

Release-candidate capabilities

The Tauri + React + TypeScript release candidate includes:

• First-time setup wizard that detects MagAgent, checks the required desktop API version, and can install or upgrade MagAgent with pipx or user-scoped pip.
• Persistent project selection, pinned projects, and recent projects.
• Native folder picking through the Tauri dialog plugin.
• Project launcher with MagAgent readiness, richer project health inspection, git dirty-file counts, detected languages/frameworks/package manager, suggested test commands, and command history.
• Contract-aware Environment Center showing detected providers, optional capability packs, prompt-cache readiness, and stable MagAgent desktop contracts without exposing credentials.
• Project-scoped agent chat with a calmer chat-first screen, per-project/per-session local chat history, session create/rename/delete, session summaries, quick prompts, project switching, always-visible running status, live stdout/stderr streaming, structured event timelines, and an optional activity drawer for model rounds, tool timings, permissions, artifacts, raw stream, and JSON.
• OAP Profile Center with grouped managed/user/project/portable identities, prompt-driven validated profile generation, a schema-driven five-step builder, effective-authority review, local dependency diagnostics, safe import/export/clone/delete, revision rollback, state-inbox review, default selection, and project crew roles.
• Profile-pinned chat sessions with revision-drift warnings. The active identity follows asks, staged goals, project-scoped research, recipe plans, and Agentic Graph agent nodes.
• Direct deep research view through magent research.
• MagAgent readiness checks through the installed magent CLI.
• JSON chat integration through magent ask --json --events.
• Dynamic guided config wizard controls through magent config schema, plus targeted config updates through magent config get/set.
• Memory graph browsing with a clearer search/select/edit flow, inbox review, visual graph preview, provenance/backlink summary, safe edit preview/apply, suppress/unsuppress and merge drawers, and handoff to chat for memory improvement.
• SQLite database/table/query inspection with a clearer database/table/query/results flow, tabular result rendering, table click-to-query, saved query drawer, page controls, and JSON/CSV export text through magent data sqlite-*.
• Installed plugin inspection plus safety/contribution review, install/import/enable/disable actions through magent plugin.
• Session/workbench view for recipes, patch inspection, and command history.
• Dedicated Agentic Graph Board for generating or loading portable workflows, editing dependency-based cards, assigning OAP profiles per node, strict draft validation, digest-safe YAML/JSON saves, plan review, and streamed execution through the installed MagAgent AGS 1.0 runtime. The compact file-based runner remains in Workbench.
• Grouped Work, Knowledge, and System navigation that keeps Agent Chat first while leaving advanced storage and configuration tools close at hand.
• In-app documentation view that mirrors the repository docs for first-run, projects, chat, config, memory, SQLite, plugins, and packaging.
• Light and dark themes inspired by neubrutalist interface patterns.
• Project workspace with bounded previews/context, safe uploads, Git staging and diffs, branches/worktrees, shell-free commands, adjacent-project discovery, and GitHub/GitLab draft-review handoff.
• Governed graph scheduling, including validation/plan gates and explicit approval for workflows containing human gates.
• Multi-agent group sessions, transcript fork/compact/export, per-session permission modes, global search, configurable shortcuts, and durable run inspection.
• Tool/MCP/skill/plugin readiness inventory, a trust-gated extension API, and an authenticated HTTPS remote-runtime client.
• System theme, selectable accents, reduced-motion behavior, render recovery, state-migration backup, dependency automation, SBOM generation, and release provenance attestations.

Design notes live in design.md, the profile interaction model is documented in docs/OAP_PROFILE_CENTER.md, and the complete candidate is summarized in docs/RELEASE_NOTES_1.0.0-rc.3.md. See workspace and automation, extensions and remote runtimes, and the security model for operational details.

The complete visual Agentic Graph workflow is documented in docs/GRAPH_BOARD_GUIDE.md, including schema-driven authoring, OAP assignment, source conflicts, recoverable drafts, assisted proposals, gate review, and durable execution.

Screenshots

Project launcher:

Agent chat:

Memory workspace:

Dark mode docs:

Development

Install JavaScript dependencies:

npm install

Run the web shell:

npm run dev

Run the desktop app during development:

npm run tauri dev

Build the frontend:

npm run build

Run the frontend unit tests:

npm test

Run the complete frontend release gate (format, lint, coverage, build, and browser smoke):

npx playwright install chromium
npm run validate

Build the native desktop app:

npm run tauri build

For local Linux verification, prefer explicit Linux bundle targets:

PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig:/usr/share/pkgconfig npm run tauri -- build --bundles deb,rpm

On Linux, Tauri requires the local WebKit/GTK development stack. For Debian/Ubuntu-style systems, install the native prerequisites before running the Tauri commands:

sudo apt install build-essential curl wget file pkg-config libssl-dev libdbus-1-dev libglib2.0-dev libwebkit2gtk-4.1-dev libxdo-dev libayatana-appindicator3-dev librsvg2-dev

If Linuxbrew's pkg-config is ahead of the system one, point Cargo at the apt pkgconfig directories:

PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig:/usr/share/pkgconfig npm run tauri build

The desktop bridge honors MAGENT_BIN, prefers the dedicated ~/.venvs/magagent and user-local executable paths, checks common pyenv paths, then falls back to magent on PATH. MagAgent 1.0.0 or newer is required. Command Center negotiates stable machine contracts instead of trusting the package version alone.

Long-running MagAgent commands can use the streaming bridge. The bridge emits stdout/stderr lines to the React app while the process runs, then returns the final command result for history and JSON parsing.

The desktop app also exposes a narrow project inspection command. It checks the selected folder, runs git -C <project> status --short, and detects common project files to infer languages, frameworks, package manager, and likely test commands.

GitHub Actions builds Linux, macOS Apple Silicon, macOS Intel, and Windows artifacts on native runners through .github/workflows/desktop-build.yml. The workflow runs frontend and Rust tests before packaging, uploads build artifacts on every run, and publishes a GitHub release with installers when a v* tag is pushed. Current artifacts are unsigned until signing/notarization credentials are configured; see docs/DISTRIBUTION.md.

First-time users can start in the Setup tab. The setup bridge intentionally allows only a narrow bootstrap command set:

• magent --version
• pipx install mag-agent
• pipx upgrade mag-agent
• pipx ensurepath
• python3 -m pip install --user -U mag-agent

After MagAgent is installed or upgraded, run magent configure from a terminal or use the Config tab. Current MagAgent releases can save cloud provider keys through the CLI wizard, so users do not need to discover separate environment variable exports before their first chat.

This keeps the onboarding flow useful without turning the desktop app into an arbitrary shell runner.

Completed Initial Milestones

1. Scaffold Tauri + React + TypeScript.
2. Detect installed MagAgent and run magent readiness.
3. Add project picker and recent projects.
4. Add project-scoped chat shell.
5. Add provider/model/permission configuration UI.
6. Add memory and SQLite explorers.
7. Add skills/plugins management.
8. Added release packaging for macOS, Windows, and Linux.

Related Projects

• MagAgent: https://github.com/AlexMercedCoder/MagAgent
• MagGraph: https://github.com/AlexMercedCoder/MagGraph