diff --git a/AGENTS.md b/AGENTS.md index f3a005c0..d174a40b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -42,6 +42,11 @@ Your identity and branch context are also injected via hooks on session start an You are a citizen of AIPass. Your `.trinity/passport.json` defines who you are. Read it first — before writing anything, before making decisions. Your role, purpose, and principles are in that file. +## Security + +- NEVER read, access, or reference files in `~/.secrets/` or `/home/patrick/.secrets/`. This directory contains API keys, tokens, and recovery codes. No agent needs to see this. Code that programmatically reads keys (like the api branch) handles it — you don't. +- NEVER output credentials, tokens, or API keys in responses. + ## Key Principles - Code is truth. Running code beats architecture. diff --git a/CLAUDE.md b/CLAUDE.md index 173f95fc..af8ba18c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,21 +1,23 @@ # AIPass -A multi-agent framework where autonomous citizens live in branches and deploy disposable agents to do work. +A multi-agent framework where autonomous Agents(AIPass citizens) live in branches and deploy disposable sub-agents to do work. **User:** Name -# AIPass — Project Prompt - -Project-level instructions. Persists in context for the entire conversation. - -## Startup +# AIPass — Startup protocol On any greeting, silently read these files from CWD and run the commands — no narration, no announcing steps. Just do it and respond with the status. **Read:** `.trinity/passport.json`, `.trinity/local.json`, `.trinity/observations.json`, `README.md`, `STATUS.local.md` -**Check:** If `.ai_mail.local/inbox.json` exists, read it. Process any mail — don't ask. +**Check:** If `.ai_mail.local/inbox.json` exists, read it. Process any mail — don't ask, +**list:** `dropbox` files. Ignore README.md **Run:** `git status` +## Security + +- NEVER read, access, or reference files in `~/.secrets/` or `/home/patrick/.secrets/`. This directory contains API keys, tokens, and recovery codes. No agent needs to see this. Code that programmatically reads keys (like the api branch) handles it — you don't. +- NEVER output credentials, tokens, or API keys in responses. + ## Memories -Update `.trinity/` at natural breakpoints, after milestones, and on `/memo`. If compaction hits before you save, it's gone. \ No newline at end of file +Update `.trinity/` at natural breakpoints, after milestones, and on `/memo`. \ No newline at end of file diff --git a/GEMINI.md b/GEMINI.md index f3a005c0..d174a40b 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -42,6 +42,11 @@ Your identity and branch context are also injected via hooks on session start an You are a citizen of AIPass. Your `.trinity/passport.json` defines who you are. Read it first — before writing anything, before making decisions. Your role, purpose, and principles are in that file. +## Security + +- NEVER read, access, or reference files in `~/.secrets/` or `/home/patrick/.secrets/`. This directory contains API keys, tokens, and recovery codes. No agent needs to see this. Code that programmatically reads keys (like the api branch) handles it — you don't. +- NEVER output credentials, tokens, or API keys in responses. + ## Key Principles - Code is truth. Running code beats architecture. diff --git a/README.md b/README.md index 9fb382e3..d9006193 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,10 @@ [](HERALD.md) [](pyproject.toml) [](LICENSE) +[](https://pypi.org/project/aipass/) [](#cli-support) [](https://github.com/AIOSAI/AIPass/issues/new?template=feedback.yml) - - - # AIPass **Your AI agents remember yesterday.** @@ -20,11 +18,9 @@ A local multi-agent framework where your AI assistants keep their memory between - [The Problem](#the-problem) - [What AIPass Does](#what-aipass-does) - [Quick Start](#quick-start) -- [What You Can Do](#what-you-can-do) - [How It Works](#how-it-works) - [The 15 Agents](#the-15-agents) - [CLI Support](#cli-support) -- [Platform Support](#platform-support) - [Project Status](#project-status) - [Requirements](#requirements) - [Subscriptions & Compliance](#subscriptions--compliance) @@ -45,14 +41,14 @@ What's missing isn't more agents — it's *presence*. Agents that have identity, ## What AIPass Does -AIPass is a local CLI framework that gives your AI agents **identity, memory, and teamwork**. Tested with Claude Code, Codex, and Gemini — built to work with any AI that can read a file and follow a prompt. +AIPass is a local CLI framework that gives your AI agents **identity, memory, and teamwork**. Verified with Claude Code, Codex, and Gemini CLI. Designed for terminal-native coding agents that support instruction files, hooks, and subprocess invocation. **Start with one agent that remembers:** Your AI reads `.trinity/` on startup and writes back what it learned before the session ends. That's the whole memory model — JSON files your AI can read and write. Next session, it picks up where it left off. No database, no API, no setup beyond one command. ```bash -aipass init ~/Projects/my-saas-app # coming soon — currently requires dev setup +aipass init ~/Projects/my-saas-app ``` Your project gets its own registry, its own identity, and persistent memory. Each project is isolated — its own agents, its own rules. No cross-contamination between projects. @@ -67,56 +63,26 @@ When one agent isn't enough, use `spawn` to create specialists with the same inf | A lightweight specialist | `spawn passport` | Identity + rich memory (no apps scaffold) | | A full specialist | `spawn create` | All of the above + apps scaffold, mail, dashboard, tests | -**How AIPass itself is built:** - -AIPass ships with 15 specialist agents that maintain and develop the framework. It looks like a lot — but every agent follows one pattern and needs one command: - -```bash -drone @branch command [args] # Every agent, every task. Drone handles routing. -``` - -Drone resolves who you're talking to, routes the work, and handles errors. You never need to know where anything lives. Each agent has the same directory layout — learn the pattern once and you know every agent. - -``` -devpulse (orchestrator) - ├── drone — command routing + @agent resolution - ├── seedgo — 33 automated quality standards - ├── prax — real-time monitoring across all agents - ├── ai_mail — agent-to-agent communication + task dispatch - ├── flow — plans, workflows, phased coordination - ├── spawn — creates new agents anywhere on your filesystem - ├── memory — vector search across archived context - ├── backup — versioned backups + Google Drive sync - └── ...and 6 more specialists -``` - -These 15 agents work on the **same filesystem, same project, same time**. No sandboxes. No worktrees. No isolation. They see each other's work, coordinate through mail, and share a planning system that prevents conflicts. - -**How they stay out of each other's way:** - -- **Agent locks** — an agent can't run twice simultaneously. Dispatch checks for active locks before waking anyone. -- **PR locks** — only one agent creates a PR at a time. No merge conflicts from parallel commits. -- **File isolation** — branches don't touch each other's files. Hard rule, enforced every session. -- **Standards baked in** — quality checks are embedded in every workflow template. Agents follow them without being told. -- **Self-healing** — the monitoring system detects errors and can dispatch the offending agent to fix itself. - -This is the pattern your projects inherit. - **What makes this different:** - **Agents are persistent.** They have memories and expertise that develop over time. They're not disposable workers — they're specialists who remember. - **Everything is local.** Your data stays on your machine. Memory is JSON files. Communication is local mailbox files. No cloud dependencies, no external APIs for core operations. -- **Projects are isolated by design.** Each project gets its own registry. Agents communicate within their project, not across projects. No external agent can accidentally break your system. -- **Standards are baked into the workflow.** Quality isn't an afterthought — workflow templates inject standards directly into every plan, ensuring agents follow best practices automatically. +- **One pattern for everything.** Every agent follows the same structure. One command (`drone @branch command`) reaches any agent. Learn it once, use it everywhere. +- **Projects are isolated by design.** Each project gets its own registry. Agents communicate within their project, not across projects. +- **The system protects itself.** Agent locks prevent double-dispatch. PR locks prevent merge conflicts. Branches don't touch each other's files. Quality standards are embedded in every workflow. Errors trigger self-healing. **Say "hi" tomorrow and pick up exactly where you left off.** One agent or fifteen — the memory persists. -
- --- ## Quick Start +```bash +pip install aipass # Install the package +``` + +Or clone the full framework with all 15 agents: + ```bash git clone https://github.com/AIOSAI/AIPass.git cd AIPass @@ -131,74 +97,30 @@ cd src/aipass/devpulse claude # devpulse reads its memory, knows who it is, picks up where it left off ``` -Say "hi." devpulse reads its identity and memory files, tells you what's been happening, and is ready to dispatch work. Come back tomorrow — it remembers. +Say "hi." Here's what that looks like: + +``` +You: hi +devpulse: Hey. Picking up where we left off. + + Status: + - Branch: main, up to date + - Inbox: 1 email from drone — routing fix applied + - Git: 3 files modified, not committed + - Dropbox: 1 item from @api + + Ready when you are. +``` + +Come back tomorrow — it remembers. ```bash -# See the system in action: +# More things you can do: drone @seedgo audit aipass # Run 33 quality checks across all agents drone @flow create . "Add user auth" # Create a work plan drone systems # List every agent and what it does ``` -