Conversation
Standardize the way CLI agents are integrated into the application by configuring them to use the `acp` subcommand. Removed legacy custom output parsing logic specific to each agent, replacing it uniformly with the centralized `parseAcpMessage` utility. This minimizes maintenance effort and standardizes the tool invocation events parsed from standard outputs.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Standardize the way CLI agents are integrated into the application by configuring them to use the `acp` subcommand. Removed legacy custom output parsing logic specific to each agent, replacing it uniformly with the centralized `parseAcpMessage` utility. This minimizes maintenance effort and standardizes the tool invocation events parsed from standard outputs.
|
1 participant
Refactored all agent integrations (
aider.ts,claude-code.ts,cursor-agent.ts,copilot.ts,gemini.ts, andopenclaw.ts) to use the Agent Client Protocol (ACP) CLI subcommand interface. Eliminated heavy bespoke log parsing within the agent classes in favor ofparseAcpMessage, which correctly handles JSON-RPC 2.0. Cleaned up redundant helper functions and non-ACP CLI arguments.PR created automatically by Jules for task 7708498430489585632 started by @juninmd