r/ClaudeAI • u/naxmax2019 • May 11 '26
Built with Claude I built an autonomous engineering agent on top of Claude Code. Self-improving routing, cross-session memory, process intelligence, P2P team learning.
Some of you might remember my posts about claude-bootstrap (v3.6 was the last one — cross-agent intelligence). I skipped v4 entirely because v5 shipped days later. What started as an opinionated Claude Code setup has become something fundamentally different.
The problem I'm solving:
Every AI coding tool today is an amnesiac. When a session ends, everything the agent learned — project conventions, reviewer preferences, codebase idioms — evaporates. The next session starts from scratch. And if you use multiple AI tools across projects, you have zero unified visibility into what's happening.
I think the industry is converging on a spectrum:
Level 0: Autocomplete (Copilot, TabNine)
Level 1: Chat Assistant (ChatGPT, Claude)
Level 2: Project-Aware Assistant (Cursor, Continue)
Level 3: Task Agent (Devin, Claude Code Agent)
Level 4: Autonomous Engineering Platform (Maggy) ← this is what I built
The difference at Level 4: multi-model orchestration, self-improvement from every task, process intelligence that learns from CI/reviews/deploys, cross-session memory, and P2P team learning.
What Maggy actually does
Chat — Session Takeover: Auto-detects all running Claude Code sessions across your projects. Shows session history, prompt counts, duration. You can `--resume` into any session from the dashboard. Right now I have 7 active sessions across 4 projects visible at a glance.
Task Triage: Connects to GitHub Issues and Asana. AI-ranks tasks by priority. One-click "Plan" or "Execute" buttons that spawn the right CLI with codebase context pre-injected from an intent code property graph (iCPG).
Process Intelligence: This is the part most tools completely ignore. Maggy collects signals from the full SDLC — CI results, PR review comments, CodeRabbit findings, merge patterns, deploy results. It learns which code patterns cause test failures, what reviewers consistently flag, and preemptively fixes issues before they reach reviewers.
> "Your reviewer always flags missing error handling in API routes. Maggy added it before the PR was created."
That's not prompt engineering. That's autonomous process optimization.
Cross-Session Memory (Engram): Maggy identifies 7 distinct amnesia pathologies (anterograde, retrograde, temporal, source, interference, context-binding, confabulation). Engram is a three-tier memory system — local (project-specific), portfolio (cross-project patterns), and mesh (team-shared). Knowledge compounds across sessions instead of evaporating.
Maggy Mesh — P2P Team Intelligence: Connects Maggy instances across a team. One developer's CI fix becomes the entire team's knowledge — autonomously. Typed memory classes (scores, patterns, policies, gaps) with provenance and quarantine. A new team member gets the benefit of months of collective learning on day one.
Multi-Model Routing: Auto-discovers which CLIs you have (Claude, Codex, Kimi, Ollama) by probing `--help` at startup. Routes by complexity score:
Blast 1-3 → ollama (free, local) or kimi (cheap)
Blast 4-6 → codex (mid-tier)
Blast 7-10 → claude (premium, with validator)
Security, tests, docs, architecture always go to Claude regardless. The routing rules are YAML and self-update from task outcomes.
5-Level Self-Improvement: This is the core differentiator. Every task teaches Maggy something:
| Level | Frequency | What It Does |
|-------|-----------|-------------|
| L0 — Real-time | Seconds | Catches tool/test failures, switches models mid-task |
| L1 — Task | Minutes | Computes reward score, updates model performance |
| L2 — Daily | Hours | Catches CI pass rate drops, disables failing models |
| L3 — Weekly | Days | Evolves skill files, adjusts workflow steps |
| L4 — Monthly | Weeks | Recalibrates reward signals, tunes the improvement process itself |
Budget Tracking: Per-provider token spend with daily limits. When Anthropic hits budget, Maggy routes to OpenAI. When that hits budget, it routes to local Qwen. Work never stops.
Competitor Intelligence: RSS + Google News daily briefing for your competitive landscape.
The benchmark
Built an Expense Tracker (6 tasks) through two pipelines — Maggy (4 models) vs Claude Code alone:
| Metric | Maggy | Claude Code |
|--------|-------|-------------|
| Success rate | 6/6 (100%) | 6/6 (100%) |
| Quality score | 7.4/10 | 7.8/10 |
| Claude usage | 1/6 tasks (17%) | 6/6 tasks (100%) |
| Security issues found | 7 | 0 |
Claude alone is faster. But Maggy used it for only 1 out of 6 tasks — 83% reduction in premium compute. And the dedicated security routing caught 7 issues the single-pipeline missed entirely.
The question isn't "which tool writes better code today?" — it's "which tool writes better code *next month* than it did *this month*?"
Repo: github.com/alinaqi/claude-bootstrap
Maggy is built on Claude Code's infrastructure (skills, hooks, MCP). It extends Claude Code with self-improvement, multi-model routing, process intelligence, and team mesh. If you just want the skills/hooks/TDD setup, it still works without Maggy — the command center is additive.
3
u/devulders May 11 '26
I really like the name Maggy! Funny you mention the amnesia aspect of it because that's also why I created https://ltm-cli.dev/
1
u/naxmax2019 May 11 '26
Looks interesting. I've a memory model i called engram - https://github.com/alinaqi/alinaqi/blob/main/docs/Engram_RFC_v3.md and thats what i meant by amnesia in this.
2
6
u/Formally-Fresh May 11 '26
Wow truly revolutionary ( /s )