You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problem or use case are you trying to solve?
Make toggling confirmation mode not reset session and prevent agents from moving too quickly and making changes to things they shouldn't be. I find that agents will create a bug in one place and then try to figure out a workaround by changing things in another place. It would be nice to be able to easily control what the agent is allowed to edit.
Describe the UX of the solution you'd like
Confirmation mode moved onto main page next to Agent Waiting. A confirmation mode settings modal that would allow for configuring when confirmation mode can be automatically turned on. Be able select actions, folders or files that would trigger confirmation mode to be turned on.
Do you have thoughts on the technical implementation?
Expanding on the confirmation mode that's already in place. Possibly even allowing a microagent to trigger confirmation mode if it notices agents are doing something questionable.
The text was updated successfully, but these errors were encountered:
What problem or use case are you trying to solve?
Make toggling confirmation mode not reset session and prevent agents from moving too quickly and making changes to things they shouldn't be. I find that agents will create a bug in one place and then try to figure out a workaround by changing things in another place. It would be nice to be able to easily control what the agent is allowed to edit.
Describe the UX of the solution you'd like
Confirmation mode moved onto main page next to Agent Waiting. A confirmation mode settings modal that would allow for configuring when confirmation mode can be automatically turned on. Be able select actions, folders or files that would trigger confirmation mode to be turned on.
Do you have thoughts on the technical implementation?
Expanding on the confirmation mode that's already in place. Possibly even allowing a microagent to trigger confirmation mode if it notices agents are doing something questionable.
The text was updated successfully, but these errors were encountered: