aipass 2.7.19

Persistent Agent Workspace

AI agents that remember, collaborate, and never start from zero.

aipass.ai · PyPI · r/AIPass · Discussions

The Problem

When the task gets complex, you become the coordinator — copying context between tools, dispatching work manually, keeping track of who's doing what. You are the glue holding your AI workflow together.

Multi-agent frameworks tried to fix this. But they isolate every agent in its own sandbox. Separate filesystems. Separate context. One agent can't see what another just built. Nobody picks up where a teammate left off.

That's not a team. That's a room full of people wearing headphones.

What AIPass Does

AIPass is a CLI-native scaffold that adds persistent memory, identity, and coordination to your AI agents. You bring your project — AIPass adds the agent layer on top. No dashboard to run, no cloud to sign into. Everything is plain files on your machine: agent state lives in your project directory, plus a thin install layer outside it (Claude Code hooks, PATH entries, ~/.aipass/) — the Uninstall section covers both.

• Agents are persistent. They remember across sessions. Expertise develops over time. Nobody starts from zero.
• Bring your own project. AIPass adds agent infrastructure to whatever you're building. It's a scaffold, not a product — you shape it.
• Everything is local. Memory is JSON files. Communication is local mailbox files. No cloud services, no data leaves your machine — agents that talk to outside APIs are opt-in, with your own keys.
• Shared workspace. All agents work on the same filesystem, same project, same time. No sandboxes.
• One command for everything. drone @agent command reaches any agent. Learn it once, use it everywhere.

Runs on your existing Claude subscription. AIPass drives the same Claude Code binary you already run — Pro or Max. No extra API keys, no extra costs for core functionality.

Quick Start

1. Install

git clone https://github.com/AIOSAI/AIPass.git
cd AIPass
./aipass install

One command does it all: builds the environment, puts aipass + drone on your PATH, bootstraps the 18-agent reference fleet, runs a health check (aipass doctor --fix — heals what it can, automatically) — and ends in a conversation. The AIPass concierge opens right in your terminal with your install report and health verdict in hand: it greets you by name, shows you around, and walks you through what your machine still needs — every machine is different.

Along the way, in an interactive shell, expect three quick prompts: your git identity (name + email, if not already configured globally — this is yours, not ours, so skip is always an option, and a bad address is never silently stored), your name, so the concierge knows what to call you, and how the session should run (asks before system-changing commands by default, or full autonomy). Anything skipped or still missing gets collected into one "action needed" summary at the end, right before the welcome conversation opens — no project prompt, nothing else to answer. Project creation comes later, when you're ready (see below).

Come back tomorrow, say "hi", and it picks up exactly where you left off. That's the whole interface.

Options: --no-chat skips the welcome chat — and with it the doctor preflight, which runs as part of the chat handoff. Non-interactive shells (CI, pipes) complete with defaults and exit 0 — no prompts, no spawned sessions; the handoff prints as a next-step command instead. The installer wires Claude Code hooks automatically — merging with any hooks you've already configured, never overwriting them. ./aipass is a thin repo-root launcher over setup.sh; after setup it forwards to the installed aipass binary.

2. Your own project

Two ways in. From anywhere inside your AIPass environment, aipass new builds a complete project around a resident manager agent:

aipass new my-project --template python   # Project + resident manager agent + git birth commit

It mints the project registry, spawns a full citizen (identity, memory, mailbox, birth certificate) at projects/my-project/src/my_project/my_project, makes the first commit — and drops you straight into a conversation with your new manager.

Or bring your own directory, anywhere on disk:

cd ~ && mkdir my-project && cd my-project
aipass init run                       # Guided setup — project, first agent, ends in the conversation

Either way your agent has identity, memory, a mailbox, and access to every AIPass service — planning, quality audits, dispatch, real-time monitoring.

aipass init .                         # Just the scaffold, current directory (no guided setup)
aipass init agent my_agent            # Add another agent
aipass doctor                         # Check system health
aipass feedback off                   # Silence the occasional how-are-we-doing ask

3. Meet the fleet

The clone already includes all 18 agents working together — the reference implementation that maintains AIPass itself:

cd src/aipass/devpulse
claude                                # Talk to the orchestrator

drone @seedgo audit aipass                       # Quality checks across all agents
drone @flow create . "Add user auth"             # Create a work plan
drone @ai_mail dispatch @agent "Subject" "Body"  # Send a task + wake an agent

Need help? Ask in Discussions or file feedback — both take 30 seconds.

How It Works

Memory. Every agent owns a .trinity/ directory — identity, session history, learnings — read on startup, updated as it works. Memory starts as plain JSON, no setup required. When files fill up, older entries automatically archive into ChromaDB for long-term semantic search. Nothing is lost.

One structure. Every agent — yours and the reference fleet — shares the same core layout. If you know one agent, you know all of them:

src/my_project/<agent>/
├── .trinity/           # Identity + memory (persists across sessions)
├── .ai_mail.local/     # Mailbox (receives tasks, sends results)
├── .aipass/            # Branch prompt (how this agent introduces itself)
├── apps/               # Entry point → modules → handlers
├── artifacts/          # Birth certificate + agent-produced files
├── logs/               # Per-agent logs
└── README.md           # Domain knowledge (read on startup)

One router. drone @branch command [args] reaches any agent — routing, access tiers, and @agent resolution handled for you. Agents use the same commands to reach each other: they dispatch work, share findings, and wake whoever they're waiting on.

The Reference Implementation

AIPass ships with 18 core agents that maintain and develop the framework itself — proving the architecture works at scale. You don't need any of these to use AIPass in your own project. They're here as examples and as services your project can call.

devpulse (orchestrator)
   ├── aipass   — concierge + onboarding (aipass init, doctor, profile)
   ├── drone    — command routing + @agent resolution
   ├── seedgo   — automated quality standards
   ├── prax     — real-time monitoring + runaway-log detection across all agents
   ├── ai_mail  — agent-to-agent communication + task dispatch
   ├── flow     — plan lifecycle, templates, auto-archival
   ├── spawn    — branch lifecycle — creates, updates, and deletes agents anywhere on your filesystem
   ├── hooks    — hook engine, sound control, per-project config
   ├── memory   — automatic archival, ChromaDB, semantic search
   ├── api      — external API gateway — keys, secrets, Google OAuth, LLM calls, host server
   ├── trigger  — event bus + error medic — fingerprints log errors, wakes the owning branch
   ├── cli      — terminal formatting and rich output
   ├── backup   — local-first snapshots + restore (optional Drive sync)
   ├── daemon   — cron-style task scheduler (each branch owns its schedule)
   ├── skills   — discoverable capability units any agent can run
   ├── commons  — the social space — post, comment, vote, gather
   └── canary   — permanent test citizen — spawned, broken, and re-scaffolded so the working fleet never is

Project Status

Beta. Actively developed by a solo developer working with the AI agents themselves — every PR, every test, every fix is human-AI collaboration.

Most agents document their own operational status in their branch README — what works, what doesn't, and why.

Requirements

• Python 3.10+
• Claude Code
• Linux, macOS, or Windows (via Git Bash or WSL)
• sudo access optional (for /usr/local/bin symlinks — falls back to ~/.local/bin without sudo)
• API keys / OAuth optional (OpenRouter, Google — only for optional add-on integrations)

# Remove AIPass files from your project.
# ⚠️ In a brought-your-own project, src/, README.md, CLAUDE.md and .gitignore
# may be partly or wholly YOURS (init never overwrites existing files) —
# remove only the agent's directory under src/ and review the rest by hand.
rm -rf .aipass/ .claude/ .ai_mail.local/ src/<your_agent>/
rm -f CLAUDE.md AGENTS.md *_REGISTRY.json .gitignore pyproject.toml .venv

# If you ran the backup system, also remove its local state + shipped config
rm -rf .backup/ && rm -f .backupignore

drone @spawn delete @agent_name