AIPass reframes agents as citizens

Hot take: this is less a new agent framework than a stance on how agent systems should be organized. The interesting idea is not more autonomy, but durable ownership, where memory and domain expertise live with the agent that actually does the work.

• –The citizen/sub-agent split is a clean operating model: persistent specialists handle domains, disposable workers handle tasks.
• –Local JSON memory, mailboxes, and project-scoped identity make continuity a core primitive rather than an add-on.
• –The tradeoff is governance: long-lived agents can drift, so the test discipline and isolation story matter as much as the architecture.
• –This feels strongest for terminal-native coding teams, especially where Claude Code, Codex, or Gemini CLI are already part of the workflow.
• –The framing is still the hard part: it’s a product about state and coordination, which is harder to sell than “agentic automation.”