Codev 2.0?

[waleedkadous]

I'm starting to think about Codev 2.0. Here are my initial thoughts. What do you all think?

• Protocol adherence is not great. When you spawn a builder to follow spider, it doesn't always follow all the steps. I am thining of adding a dterminisitic checklist core that the non-deterministic agents defer to so we can reliably adhere to protocols.
• The agent farm implementation is pretty fragile. Move away from ttyd and raw html to something like react/vite + xterm.js + web sockets.
• I did look at rewriting Codev as a vscode extension but it just wasn't a good fit in terms of things like the detailed terminal monitoring we send.
• I think the tower (overview of all the different agent farms running) is under used. I am thinking of moving the tower to run in the cloud and have different agent farms connect to it. That way, you can do things like check how your agent farms are running from your cell phone and give them instructions to unblock them. The tower itself might need its own agent.

Thoughts?

[abdullah-alnahas]

I’m fully on board with the first point. Making the framework itself enforce protocols (rather than relying just on the agent) feels like an essential feature to me. but maybe also leaving room for protocol-free engagement as well.

I have also been thinking lately about a 'smooth' way for users to define their own protocols. I don't want to suggest something clumsy; but maybe there could be a standard 'recipe' for adding a new protocol?

• Perhaps saving it to a personal fork or a local config?
• Or maybe even pulling from a 'marketplace' or Hub (though that might be over-engineering it for now)?
  Or maybe this is a rare use case and not worth the complexity yet?

On a practical note: being able to run several architects simultaneously for different repos would be huge. A typical workday for me involves juggling two repos at once (and the crazy days involve 3 or 4), so concurrency support is high on my wish list.

One last small thought: could adopt be augmented to ask the agent to write codev docs for a legacy project, as if it had been built with codev from the beginning?