https://docs.all-hands.dev/ logo
Join Slack
Powered by
I've been pushing Agent Canvas pretty hard lately,...
# success-stories
w
I've been pushing Agent Canvas pretty hard lately, vibecoding some personal projects I find the current experience sort of frustrating. I'll have 17 ideas for fixes, but managing 17 agents is too much. I can throw them all at the same convo, but the agent gets confused. Some of the ideas are big, some are small. Some of the ideas touch similar parts of the codebase and need to be sequenced; others can be easily parallelized. Some ideas should get Fable, others should get Sonnet. Also annoying to have to watch each convo, wait til it finishes, see what's been done, and say "push to main" or "open a PR" over and over again. So I built a Manager! I have a UI where I can rapidly submit tickets. There's a 1m cron automation that checks the board and kicks off conversations as necessary. It will funnel similar tickets into the same convo, and knows to hold off on tickets that will conflict with WIP. It also knows to keep at most N conversations going at once. This feels way nicer--I'm not really babysitting conversations anymore, just firing off tickets and then clicking "verified" once I've confirmed the feature has landed
👀 4
🐾 1
👍 1
l
This is cool! Kinda like what Vibe Kanban was supposed to be? But completely enabled by what we already have in the agent server
✅ 1
w
nod exactly
I had a kanban interface before but never used it. The unlock here is that I have one board per workspace which feels so much better
also it only manages the tickets--if I create a conversation outside the kanban board it doesn't show up here. which is good IMO
yet another use case for a "Skin" UI
👍 1
c
This is kinda like my old Secretary, but with a UI
I've been thinking to bring it in OpenHands, under some shape. AmpCode has introduced recently a “Puck”, an agent with a specific avatar and name, who manages the Amp threads
s
This is great! With agents getting better, I do think the default interface for coding will move from individual conversations to tickets/issues/epics, with quick access to the conversations trying to solve those. How can we make something like this easily usable for our users?
w
If we get my dream plugin/extension system in place we should be able to ship it that way 🙂
👍 2
c
Your skins PR is in draft, but I've been using it and it's fine. Do you want it ready for review?
w
It's a HUGE change and very vibecoded, I think we'd need broader buy-in from @limited-student-10747 and @hundreds-twilight-32833 before moving forward w/ Skins (and probably a different name 😅). There are a few different ideas going around about how to build a concept of extensions
c
Yeah. We have somehow now a strange concept of “canvas extensions “ in the sdk too
I tended to think that “apps” as applied to a new page kinda fits
h
Names are hard 🫠
l
I think we’re planning on making the extensions to add to the sidebar
2 Views
Open in Slack
Previous
Powered by