Replies: 1 comment 1 reply
-
I kinda feel that we need modes of operation in that sense.
Currently DC with Claude can go bit too far and start to try unplanned things. But there is also alternative approach. We have things to do and improve. Planing modes are not on short term roadmap in that sense. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Integrate an optional, automated AI review step into Desktop Commander's execution workflow before it takes action.
After generating a plan (e.g., with Claude), DC can send it to a different AI, like Gemini Pro 2.5 exp (free), for critical analysis of potential issues, risks, or improvements.
DC presents the original plan alongside the AI reviewer's feedback directly to the user.
The user must explicitly review this feedback and approve the plan before DC proceeds with execution.
Potential: This could provide a crucial safety net, since gemini would also have read capabilities in the codebase. The entire plan -> review -> approve -> act cycle stays within Desktop Commander.
Thoughts anyone? I already kind of do this with Ai-studio before I implement major changes.
Beta Was this translation helpful? Give feedback.
All reactions