Agent-factory: A Claude Code Plugin for Persistent AI Sub-Agent Teams

Agent-factory is a Claude Code plugin that creates persistent sub-agent teams for development projects. It addresses the problem of losing context between Claude sessions and provides multiple specialized perspectives on your work.
How it works
You run /create-agents and it interviews you about your work: what you work on, what takes too long, and what perspectives you're missing. Based on your answers, it proposes a team of 2-5 agents, each with:
- A personality with communication style, quirks, and opinions
- A specific job (code review, tech debt tracking, daily priorities, strategy)
- Persistent memory that accumulates across sessions
- Scoped knowledge (each agent only sees docs relevant to their role)
- A dispatch doc explaining how to invoke them
The agents are dispatched through Claude Code's existing Agent tool. They're prompt-based identities with file-based memory, requiring no external services, API keys, or Docker.
Example team setup
The creator's actual setup for a small SaaS company includes five agents:
- CORTEX – Operations brain that tracks project status across repos, maintains unified to-do lists, and dispatches other agents. Refers to projects by "health" (green/yellow/red) and calls stale projects "cold cases."
- DIAL-UP – Personal assistant that checks energy level first, then checks email, reads project status, and builds daily priority lists. Quick wins are "pings," deep work is "downloads."
- SIGNAL – Strategist who evaluates what to build, ship, or kill. Calls busywork "static" and drops "ship it or kill it" decisions.
- GAUGE – Tech debt tracker who audits repos for outdated deps, failing CI, abandoned branches, and infrastructure drift. Calls abandoned repos "junkers" and clean repos "mint condition."
- MEGAPHONE – Hype man who celebrates wins, writes specific praise, and keeps a "greatest hits" list.
Technical implementation
Agent-factory scaffolds this directory structure:
agents/ ├── team.json # Team manifest ├── cortex/ │ ├── prompt.md # The agent's brain │ ├── dispatch.md # How to invoke │ ├── contract.md # What it reads, what it produces │ ├── references/ # Scoped project docs │ └── memory/ # Persistent across sessions ├── dial-up/ │ └── [same structure] └── shared/ # Where agents write output
It also updates your CLAUDE.md so the main Claude thread knows what agents exist and how to dispatch them.
Available commands
/create-agents– Full interview and scaffolding flow/add-agent– Add a new team member to an existing team/upgrade-agent– Add MCP server access, cron scheduling, or promote an agent to work across all projects/hire-agent– Grab an agent from another repo
The persistent memory system means agents remember project details, preferences, and patterns across sessions. GAUGE remembers which repos had debt last week, DIAL-UP remembers that you do better with short tasks on Mondays, and SIGNAL remembers strategic decisions already made.
📖 Read the full source: r/ClaudeAI
👀 See Also

Rift CLI: Manage Git Worktrees for Parallel AI Agent Workflows
Rift is a CLI tool that creates isolated Git worktrees and branches to run multiple AI coding agents like Claude Code simultaneously on the same repository. It includes lifecycle hooks, deterministic port mapping, and multi-editor workspace support.

Claude Code Karma: Local Observability Dashboard for Claude Code Sessions
Claude Code Karma is an open-source local dashboard that parses JSONL files from ~/.claude/ to visualize Claude Code session data, track tool usage, and monitor silent failures. Built with FastAPI, Svelte-Kit 2, Svelte 5, and SQLite, it provides full session timelines and live tracking.

Run local LLMs on your phone with Observer: offline agents for monitoring and logging
Observer is an open-source iOS app that runs multimodal LLMs locally on your phone to monitor events, log data, and trigger Discord notifications — all offline and free.

Codev: AI agent workflow for 106 PRs in 14 days
Codev is an open-source system that coordinates multiple AI agents through a strict Spec→Plan→Implement→Review→PR workflow, catching 20 bugs before shipping and producing code rated 1.2 points better on a 10-point scale.