Agent systems / Explore the project
Port Daddy
Coordinate multiple AI agents with visible file ownership, sessions, messages, ports, and recovery notes that help teammates resume work.
Made for
For developers managing several AI agents or concurrent development efforts who need a shared operational picture and a useful way to pick up the thread when a session changes.
File ownership and sessions
Explicit ownership helps collaborators understand who is working where, while sessions connect those claims to the activity that gave rise to them.
Start here
Identify the session and the surface of the task, giving the effort a visible place in the coordination system rather than leaving it in a single chat.
Explore the coordination documentation and architecture, then follow the book for the ideas behind it. Sessions, ownership, messages, ports, and recovery notes offer concrete starting points for thinking about parallel agent work.
Availability
Explore the project
How it works and what’s inside
Made for
For developers managing several AI agents or concurrent development efforts who need a shared operational picture and a useful way to pick up the thread when a session changes.
Parallel agents can create parallel confusion: two edits to the same file, a lost port, or work nobody can recover. Port Daddy is a coordination system that makes ownership, sessions, messages, and recovery context part of the work itself.
How it works
Workflow
Establish the work
Identify the session and the surface of the task, giving the effort a visible place in the coordination system rather than leaving it in a single chat.
Coordinate the moving parts
Track ownership, messages, and ports while work proceeds. Make collisions and handoffs easier to notice before they become a difficult integration problem.
Leave a recoverable thread
Keep recovery notes and session context so the next person or agent has a concrete starting point, including what remains uncertain or unfinished.
Inside Port Daddy
Features
File ownership and sessions
Explicit ownership helps collaborators understand who is working where, while sessions connect those claims to the activity that gave rise to them.
Operational coordination
Messages and port tracking address the practical details of concurrent development, keeping useful coordination information close to the work.
Continuity across handoffs
Durable recovery context reduces dependence on one agent's memory and makes unfinished work easier to inspect and resume thoughtfully.
Explore the coordination documentation and architecture, then follow the book for the ideas behind it. Sessions, ownership, messages, ports, and recovery notes offer concrete starting points for thinking about parallel agent work.
Related projects
Like what you see? Hire Curiositech
Back to products