We've been getting feedback about adding a /conden...
# proj-agent
e
We've been getting feedback about adding a /condense command to Agent Canvas (currently in CLI). Is this mostly a Skill thing? Or does it require more agent Engineering? [Feature]: Add Web UI commands to condense and clear context memory Want to see if we need to move this to the SDK repo, Extensions Repo, or Agent Canvas repo 🙂
h
Just made https://github.com/OpenHands/agent-canvas/issues/1407 related to missing slash commands
👌 1
l
This would go into the SDK, but I guess it's not very high priority
We could review a community pr though
e
I'm curious why you think it might not be high priority? It's probably not drop-everything-and-fix but it does seem like there's been recent chatter over the last couple weeks about it.
l
Because it doesn't help automations and none of our customers asked for it?
Which AFAIK are our priorities
In just saying this from the POV of what the full time people are working on of course, I'm happy to have someone implement it
w
The SDK already supports condensation on-demand through the
POST /api/conversations/{id}/condense
endpoint, the gap should just be wiring that up to a slash command in the canvas
l
Oh, that would make it pretty easy then. I guess we’d just need to make sure that endpoint is wired into the typescript-client and add the slash command, might be worth doing if it’s that easy
w
One caveat here: that endpoint triggers our current condensation framework, which tries to keep recent context around. I believe the folks asking for this are coming from tools like Claude Code, where the equivalent command (
/compact
) does something more akin to our complete context reset.
l
Yeah, agreed, but we could also cross that bridge when we come to it. We can always implement a different condenser (or maybe just change the parameters of our current one?)
w
The "manual context management" paradigm is different enough from our usual condensation flow it's probably best to have a separate condenser so we can optimize each use case separately