https://docs.all-hands.dev/ logo
Join Slack
Powered by
when i attempt to use Agent Canvas as my daily dri...
# proj-agent-canvas
s
when i attempt to use Agent Canvas as my daily driver, i think the primary reason that i return to CLI tools is context window info. it's in the status bar of everything i use heavily has somebody already solved? this PR seems related for a stats tab--but no idea if that PR is right way to do it github.com/OpenHands/agent-canvas/pull/1863
đź‘€ 1
l
Hey @straight-dog-12443, here’s an agent driven reply:
Mostly yes, with one important correction: Agent Canvas already has the underlying context-window information, but PR #1863 does not recreate the always-visible status-bar experience they’re describing.
• Current Canvas shows context usage in the metrics modal, accessible through the conversation’s ellipsis menu → “Display cost.” It includes tokens used, context-window size, percentage, and a progress bar. See theexisting context-window section.
• PR #1863moves similar information into a Usage tab in the right drawer. That improves discoverability, but the drawer can be closed and still requires navigation.
• Codex CLI displays`context-remaining`in its footer by default, with`/status`available for more detail. That ambient visibility is the key difference. See theCodex configuration referenceandCLI commands.
My recommendation would be:
1. Add a compact, always-visible indicator such as`72% context left`to the conversation chrome or footer.
2. Make it clickable to open the richer Usage panel or existing metrics modal.
3. Keep manual compaction and provider-balance probing in their own PRs.
Do you think that this design would be good? Also would be interested in feedback from @breezy-kilobyte-39430 on the design
s
sounds ideal to me
b
Reviewing it today
🙏 1
@straight-dog-12443 @limited-student-10747 I've done some design tweaks here: github.com/FraterCCCLXIII/openhands-agent-canvas/…/context-window-meter In that branch I have the new meter popover added so I can see how they look and work side-by-side. I believe we still have to separate this into multiple PRs but I wanted you both to take a look first. I've removed the modal all together but have retained the item in the original item which now opens the drawer. We can remove it eventually but I think it's best to retain it in case some people still access it from there. It will open the right drawer and not the modal now. One question: we show a line for budget limit but I don't know of anywhere a user can set it. Is this a cloud-only feature or am I missing something? My last note is that we need to make sure that when I user clicks the compress interaction they need to see if it worked or not in a toaster. @straight-dog-12443 can you make sure that is wired properly?
🙏 1
s
yess'r! will check it out this evening and report back
ran the branch locally. landed on the onboarding wizard, hit "Skip for now", and the app dies:
An error occurred
useConversationId must be used within a route that has a conversationId parameter
error boundary, no sidebar, no composer. reload doesn't bring it back, stays dead until i clear localStorage. so it's the first-run path, skip onboarding and you're stuck. console logs it twice, raw and then "React Router caught the following error during render". built 3323de4f as well and home comes up fine there. the meter's in that working build too. didn't chase it past that but happy to help if i'm able. lmk on the toaster, couldn't get to it so there's no clicking it yet.
l
@millions-afternoon-47582 I assigned this to you, could you help finish @breezy-kilobyte-39430’s PR? github.com/OpenHands/OpenHands/issues/16170
m
Yes, I'll take a look. Thank you very much! thankyou
b
@limited-student-10747 did that get integrated with with the work from George?
l
Oh, I haven’t had a chance to take a look at it yet
If it’s solving the same problem we should take a look and solve both at the same time
b
I had made the branch for him to pull work from and integrate with what he was working, I did a design pass and made sure the new context popover in the chat composer matched what we were doing with the usage page in the right drawer (also made some design tweaks). I know he was meant to separate some things out into separate PRs including the newer condense context interaction. My branch has that because I did a design pass but it hasn't been reviewed and was really meant as "here is what it should look like, use it for your final work." I think there was an open question about the completion toaster needing to appear if condense was successful (or not) that was not complete.
đź‘Ť 1
s
I re-read this thread and wasn't sure if anything was wanted from me. I wanted the meter working on my system so I fixed the first-run crash, got the meter showing, and checked the toaster wiring — it toasted success when nothing had compacted. Fixed that too and verified with a real compaction, screenshot attached.
l
Hey @straight-dog-12443 if you have a prototype feel free to send it in (as a general rule). I asked Hiep to take it over the line, but if he just needs to review it and merge then all the better!
🙏 1
s
🙌 1
l
Requested review from @millions-afternoon-47582, if you have a moment amongst your other priorities please take a look!
thankyou 1
m
Hello @straight-dog-12443, As part of our pull request requirements, we include a demo video or screenshot in the pull request description. Could you please add a demo video to demonstrate the output? Thank you very much! thankyou
s
Sorry about that. Added pic
thankyou 1
m
Hello @straight-dog-12443, I’ve left a comment on your pull request Thank you very much! thankyou
🙏 1
@straight-dog-12443, I’ve approved and merged the pull request. Thank you very much for your work on this! thankyou
đź‘Ť 1
🙌 1
🙏 1
Open in Slack
PreviousNext
Powered by