Maggy: An Autonomous Engineering Platform on Claude Code with Cross-Session Memory and P2P Team Learning

A developer on r/ClaudeAI has built an autonomous engineering platform called Maggy on top of Claude Code. It addresses the core problem of AI coding tools being amnesiacs — knowledge from one session doesn't carry over. Maggy implements cross-session memory, process intelligence from the full SDLC, and P2P team learning, placing itself at Level 4 on the industry spectrum (autocomplete → chat assistant → project-aware assistant → task agent → autonomous engineering platform).

Core Features

• Chat — Session Takeover: Auto-detects all running Claude Code sessions across projects. Shows session history, prompt counts, duration. You can --resume into any session from the dashboard. Currently supports 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 spawn the right CLI with codebase context pre-injected from an intent code property graph (iCPG).
• Process Intelligence: Collects signals from CI results, PR review comments, CodeRabbit findings, merge patterns, deploy results. Learns which code patterns cause test failures and what reviewers consistently flag — preemptively fixes issues before PR creation. E.g., “Your reviewer always flags missing error handling in API routes. Maggy added it before the PR was created.”
• Cross-Session Memory (Engram): Identifies 7 amnesia pathologies (anterograde, retrograde, temporal, source, interference, context-binding, confabulation). Three-tier memory: local (project-specific), portfolio (cross-project), mesh (team-shared). Knowledge compounds across sessions.
• 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. New team members get months of collective learning on day one.
• Multi-Model Routing: Auto-discovers available CLIs (Claude, Codex, Kimi, Ollama) by probing --help at startup. Routes by complexity score: Blast 1-3 → ollama or kimi; Blast 4-6 → codex; Blast 7-10 → claude. Security, tests, docs, architecture always go to Claude. Routing rules are YAML and self-update from task outcomes.
• 5-Level Self-Improvement: Every task teaches Maggy something. Levels: L0 real-time (seconds, catches tool/test failures, switches models mid-task), L1 task (minutes, reward scores), L2 daily (hours, CI pass rate drops disable models), L3 weekly (days, evolves skill files), L4 monthly (weeks, recalibrates reward signals).
• Budget Tracking: Per-provider token spend with daily limits. When Anthropic hits budget, routes to OpenAI; when that hits, routes to local Qwen.
• Competitor Intelligence: RSS + Google News daily briefing for competitive landscape.

Benchmark: Expense Tracker (6 tasks)

Metric	Maggy (4 models)	Claude Code alone
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

Maggy achieved 83% reduction in premium compute while catching 7 security issues missed by the single-pipeline approach.

Impact

This isn't just another wrapper — the self-improving routing and cross-session memory represent a genuine shift toward autonomous engineering platforms. For teams tired of context loss and tool fragmentation, Maggy shows what's possible when knowledge compounds instead of evaporates.