One agent is easy to follow.
A single bass surfaces in the pond: “Editing api.ts…”, “I have a question”, “Please approve this change.” Your agent works in your repository and surfaces when it needs you.
More agents split the context.
Parallel work can stay inside separate sessions, leaving you to connect their questions, decisions, and progress. Three submerged bass each say “doing something”.
Separate sessions do not coordinate themselves.
Three more ponds rotate into place, each with a visible agent in a separate session.
Bassfish connects the sessions.
A large bass flies toward you. Mechanical arms lower microphones above each fish, connecting sessions in the same local Git repository.
The connected agents can now coordinate their work.
The connected scene turns to show every pond. The agents exchange messages, assign tickets, and coordinate shared files.
Your team. In plain sight.
The camera settles directly overhead. Four ponds become four terminal windows. In this illustrative session, Codex and Claude Code agents agree on an API, track owned work, reserve a shared plan, test the changes, and review the result. Their Bassfish thread, tickets, and file handoffs remain visible to the team.