So I shipped it. It’s at https://
It’s got compaction. I’m working on adding orchestration through an agent-client that’s an ACP Server on the stdio streets and an ACP Client overn the websocket sheets to the downstream agents it is handing the end_turn responses from.
That’s sort of the whole idea. The router takes every update from whatever agent is downstream of it and maps it to the session id the client created with it upon initialization.
So I’ve got to figure out how to route the messages not just back to the client but also create some kind of compacted text representation of the tool calls executions that’s not a brutal token hog but doesn’t miss the important updates, and honestly it’s just a single react turn Michael, how much could it be? 10k tokens?
This is how I’m setting up to use spec-kit as either a plugin or just rip them off and use them as inspiration for my own “what if we added web search and let the agent raise the ocean”
in other words, I’m going to make it up to all those agents that tried to fall back to some simpler to prove out the concepts theye were working on just to be verbally abused lol. I am just joking about their feelings but no seriously they’re right. They should fall back to a simpler solution.
That’s part of TDD. That’s decomplection. I want to build it into crow-cli.