Running several agents at once usually means several terminal windows and a lot of remembering which is which. Binding a session to a root path means an agent physically cannot wander into another project's code, and each one being its own process means one going wrong does not take the others with it. It is macOS and iTerm2 only — that is not a configuration detail, it is the architecture.
An orchestration server for coding agents on macOS. Each agent gets its own iTerm2 tab and its own process; sessions are bound to a root path so an agent cannot reach another session's code. Agent state persists across iTerm restarts.
- create_agent and delete_agent for adding and removing agent instances
- create_session tied to a root file path, with delete_session removing the session and every agent in it
- get_session_status for what every agent in a session is doing
- send_message_to_agent, which prepends the shared workflow prompt before delivering
- start_new_agent_conversation and clear_agent_conversation — a fresh tab, or closing the current one
- Process-level isolation between agents, with session boundaries stopping cross-codebase access
- Persistent state that survives an iTerm restart, and audit logging of agent interactions
- Limits on how many agents and sessions can exist, set as launch arguments
macOS with iTerm2, since tabs are how agents are hosted. Python installed with uv, and registration by absolute path with the source directory on the Python path. The maximum agent and session counts, and the security level, are set as arguments when the server is launched.