This message was deleted.
# proj-agent-canvas
d
This message was deleted.
c
🤔 interesting! I have an experimental PR here - basically, it allows the agent to propose things for the user to get them remembered. Core change is basically this: https://github.com/All-Hands-AI/OpenHands/blob/5fce3d64d41647f4dac1ae4afd69313ee4c[…]openhands/agenthub/codeact_agent/prompts/memory_instructions.j2 What do you think if this UI/UX would impact this agent workflow? https://github.com/All-Hands-AI/OpenHands/pull/7334
OR do you think is more like an addition: allow user to reference existing event, and manually specific things that should be added to agent's long term memory?
f
Rough outline looks good. Made a quick note on what would improve the user experience.
b
TBH I struggle to understand exactly what this button is for. Is it for splitting the conversation into two threads, that run in parallel? That would be cool. Or is it more: save information about this event for future-conversations?
👍 1
l
I think both Robert’s idea (user-centered) and Xingyao’s idea (agent-centered) are good. Either way we probably want a UI like what Robert proposed to determine where it’s saved. I’m in favor of this! One thing to consider though, we have a long-standing issue open of viewing existing microagents in the UI. It seems like both functionalities (viewing existing and adding new microagents) should be part of the same UI?
👍 1
w
I have an experimental PR here - basically, it allows the agent to propose things for the user to get them remembered.
The way I'm reading this, the agent would modify repo.md automatically, and push those changes in the same PR I'd be curious to see how it actually performs. My guess is the agent will be way too aggressive about putting changes in there, and the repo.md will become wildly bloated over time. But happy to be proven wrong here!
👍 1
TBH I struggle to understand exactly what this button is for.
Is it for splitting the conversation into two threads, that run in parallel? That would be cool.
Or is it more: save information about this event for future-conversations?
The goal here is to save more information for future conversations. It kicks off a second conversation to actually do the process of editing the file and opening a PR (which is maybe overkill, but it's the easiest way to do things) And that does set us up for "conversation forking", which is another feature we'd like to add
💡 1
c
Carlos makes a very good point IMHO, maybe in part because other tools have a "branch off" or "summarize and start new conversation" button there. So it feels like that kind of feature. 😅
nod 1
f
From a user perspective, to Graham's point, viewing the existing micoagents and as a user seeing as how they are called / used together is going to be a big win. I've talked to teams who have central code prompt repositories and they just pull them in and use combinations from other users they know have worked.
c
as a user seeing as how they are called / used together is going to be a big win
this is already implemented in main should be get shipped in the next release 🙂
🎉 1
but yeah, we definitely need UI for microagent management (add/delete/share)