Maggy — srooter>'s open-source AI engineering harness.
From the team behind srooter>: Maggy is our open-source harness that turns Claude Code, Codex, Kimi, and Gemini CLI into a test-enforced, quality-gated workflow — with cost-aware routing across 13 model tiers, cross-session memory, and a plugin system. Run it locally, own every line. Point it at srooter> when your team needs a governed gateway.
git clone https://github.com/alinaqi/maggy.git && cd maggy && ./install.sh
- Run your own multi-model routing locally — your keys, cheapest capable model per task.
- Add a real engineering harness to your CLI — TDD, gates, memory, agent teams.
- Self-host and own it end to end — open source, no account, no gateway required.
Two parts, one repo
Start with Bootstrap in 30 seconds; add the Maggy server when you want routing, protocols, and the dashboard.
An installable config pack — 67 skills, hooks, rules, templates — that drops into ~/.claude/ and applies on your next session. ~30-second install; works with Claude Code, Codex, Kimi, and Gemini CLI.
An optional local FastAPI server + web dashboard adding 13-tier routing, skill protocols, the Cortex code graph over MCP, Polyphony isolation, and plugins. maggy serve → localhost:8080
Core systems
Click any system for the details.
Every task goes to the cheapest model that can actually do it.
Deterministic, intent-matched workflows — not just prompts.
Tests tell you it passes; Telos tells you it fulfils its intent.
A queryable code graph any harness can use over MCP.
Run multiple agents on one repo without file conflicts.
Memory that survives compaction and persists across weeks.
Stores why code exists, not just what it is.
A six-agent TDD pipeline with enforcement that doesn’t depend on remembering.
Routing — 13 tiers, cheapest capable wins
Every message is scored 1–10 for complexity and classified by task type (locally, by Qwen3). Trivial asks stay free and local; hard architecture climbs to Claude. Budget-capped, with auto-demotion.
| T0 | Qwen3 (local) | Classification, triage, free bulk ops |
| T1 | Gemini Flash-Lite | Bulk extraction, pipelines |
| T2 | DeepSeek Flash | Docs, tests, scaffolding |
| T3 | Gemini Flash | Multimodal, vision, audio |
| T4 | DeepSeek Pro | Complex coding, refactors |
| T5 | Gemini CLI | Multi-file agentic coding |
| T6 | AGY | End-to-end (git + code + test) |
| T7 | Kimi | Long-context analysis |
| T8 | Gemini Pro Search | Deep research, 2M context |
| T9 | Grok | Competitor intel, reasoning |
| T10 | Codex | Bulk generation, security-sensitive |
| T11 | Claude Sonnet | Quality-critical code, debugging |
| T12 | Claude Opus | Architecture, security, ADRs |
Plugins — drop-in extensions
A simple plugin system: drop one in and it hooks into Maggy's events. Ships with several out of the box.
Turns shipped work into posts and publishes to LinkedIn, X, and Reddit — with a voice engine (plain-text, no em-dashes) and a comment-reply heartbeat.
GitHub, Asana, and Monday providers wire tasks and issues into the harness.
Telos ships as a plugin; write your own with a small plugin.yaml + plugin.py.
What makes Maggy different
Most “AI engineering” tools are either an autonomous agent loop (Hermes-style) that replaces your CLI, or a thin wrapper that adds nothing. Maggy is a discipline and routing layer that augments the tools you already use.
| Maggy | Autonomous agent frameworks | Raw Claude Code | |
|---|---|---|---|
| Multi-model routing | Yes — 13 tiers, cheapest capable model | Usually single model / BYO loop | No — one model for everything |
| Discipline enforced | TDD stop-hooks + quality gates + ADRs | Optional, prompt-dependent | None |
| Cross-session memory | Engram / Mnemos — survives compaction | Rare / vector-store bolt-on | Lost each session |
| Code intelligence | iCPG + Cortex MCP (why code exists) | Usually plain RAG over files | None |
| Parallel safety | Polyphony — Docker-isolated workspaces | Manual / conflicts on shared repo | N/A |
| Works with your CLI | Augments Claude Code / Codex / Kimi / Gemini | Replaces your tools with its own | — |
| Open source | MIT, 1100+ tests, self-hostable | Varies | Closed |
What it looks like
You: "review the auth middleware for timing attacks" → Blast score: 8/10 (security + architecture) → Routed to: Claude (Tier 12) → ADR gate: found docs/adr/0003-jwt-strategy.md → injected as context → Review runs with full architectural context You: "push to git" → Intent matched: git-push protocol → ✅ lint · ✅ typecheck · ✅ tests · ✅ commit (AI-written) · ✅ push
Maggy and srooter>
They fit together. Maggy is the harness — local, free for individual developers, picking the right model and enforcing engineering discipline. srooter> is the gateway — the governed, audited, multi-tenant layer a team routes all of that traffic through for budgets, policy, and compliance. Point Claude Code at either; use Maggy solo and free, add srooter> when a team needs governance. Neither locks you in.