When your team switches AI agents, what happens to the project context?

by•

Hi, I'm Kelly from Busabase. We're building an open-source database and workspace where the records, docs, skills, and apps a team chooses to keep can be reused by people and connected AI agents.

One problem we keep running into: an agent finishes useful work, but the result stays buried in a chat. The next person or agent has to reconstruct the project background and decisions before moving forward. In Busabase, that work can live in a shared workspace, with access controlled by permissions and review when needed.

How does your team handle this today? Where do you keep the project context that multiple agents need, and what gets lost most often when you move between tools like Claude Code and Codex? I'd love to hear what's working for you and what still breaks.

7 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.