Post

A good part of my time working on AgentControl (side-project, it's my primary tool. Main project is still LinkBunny) recently has been managing the amount of information I have in my agent transcripts.

I think that's a major benefit of building my own orchestration tool. It's not as easy to do (or is it even possible) using a stock coding agent app/cli. In this case I make it collapse the cli callback which has excessive information. From vs to:

Collapsing the callback is what a stock CLI leaves to the model. The full output enters context once, then every later turn carries it. Cutting it before it lands is a cost decision as much as a readability one.

Yes, if you use a stock CLI, it's harder to do this properly. It's possible though, you wrap the call and write the full output to a file, which is probably a good practice any way, for the model to read if it needs/want to. I have my own orchestration tool, so it's slightly easier for me.

0 reposts0 likes

No replies yet.