Conversation
Documents ACPAgent usage, configuration, metrics, and cleanup with a ready-to-run example referencing examples/01_standalone_sdk/40_acp_agent_example.py. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
all-hands-bot
left a comment
There was a problem hiding this comment.
🟡 Acceptable - Documentation is clear and practical, but has organizational issues and unverified syntax.
Key Issue: Important information about ACP delegation model is scattered. The fact that this replaces direct LLM calls (no API key needed, server manages everything) should be front and center, not discovered at line 143.
|
@OpenHands read the PR and apply all suggestions |
|
I'm on it! simonrosenberg can track my progress at all-hands.dev |
- Replace 'wrap focus={5-7}' with 'highlight={5-7}' per Mintlify standards
- Remove 'wrap' attribute from other code blocks
- Add Note callout explaining key differentiator (no LLM_API_KEY needed)
- Move 'What ACPAgent Does Not Support' section after Basic Usage
- Expand permission auto-approval explanation with security context
Co-authored-by: openhands <openhands@all-hands.dev>
SummaryI've successfully applied all review suggestions from PR #351. The changes have already been committed and pushed to the Checklist of Review Suggestions Applied:
Commit Details:
The changes are concise and focused solely on addressing the review feedback. No extraneous modifications were made. |
all-hands-bot
left a comment
There was a problem hiding this comment.
🟡 Acceptable - Good improvements from previous feedback, but missing the "how to run" instructions that users need.
Key Issue: You import RunExampleCode but never use it, and provide no alternative bash block. Users reading this will see example code but no clear command to execute it.
|
@OpenHands please read the reviews and fix them |
|
I'm on it! simonrosenberg can track my progress at all-hands.dev |
all-hands-bot
left a comment
There was a problem hiding this comment.
🟡 Acceptable - Docs are functional but still have unresolved usability issues from previous rounds.
- Remove unused RunExampleCode import
- Fix highlight range from {5-7} to {5,7-9} to skip blank line
- Add bash code block with 'Running the Example' instructions
Co-authored-by: openhands <openhands@all-hands.dev>
SummaryI've successfully addressed the two outstanding review comments on PR #351: Changes Made:
Checklist:
Commit: |
all-hands-bot
left a comment
There was a problem hiding this comment.
🟡 Acceptable - Previous issues have been addressed. Document is functional and practical, but could be more concise.
sdk/guides/agent-acp.mdx
Outdated
| 4. The server processes the request using its own LLM and tools, streaming session updates (text chunks, thought chunks, tool calls) back to the SDK | ||
| 5. The SDK accumulates the response and emits it as a `MessageEvent` | ||
| 6. Permission requests from the server are auto-approved — this means the SDK automatically grants any tool execution or file access the server requests, so ensure you trust the ACP server you're running | ||
| 7. Token usage and cost metrics from the ACP server are captured into the agent's `LLM.metrics` |
There was a problem hiding this comment.
🟡 Suggestion: This 7-step procedural breakdown is verbose for a usage guide. Users don't need to know that the SDK calls conn.prompt() internally or that it emits a MessageEvent.
Condense to 3-4 key architectural points:
- Subprocess delegation: ACPAgent spawns the ACP server and communicates via JSON-RPC
- Server-managed execution: The ACP server handles its own LLM calls, tools, and context
- Auto-approval: Permission requests are auto-approved (trust your ACP server)
- Metrics collection: Token usage and costs are captured automatically
The current version reads like implementation docs rather than user-facing guidance. Keep it at the conceptual level — users care about what happens (delegation model), not how the SDK implements it (method names, event types).
There was a problem hiding this comment.
Interesting nit. I tend to agree with the agent, FWIW though, I was thinking about this on other issues: sometimes we really seem to need some docs for the agent, and some other doc for the human.
I'm looking into a custom llms.txt for this... Maybe. Or shadow docs. Or invisible comments 😅
|
@OpenHands please apply all the PR reviews and suggestions |
|
I'm on it! simonrosenberg can track my progress at all-hands.dev |
Address review feedback to reduce verbosity in the 'How It Works' section. Changed 7-step procedural breakdown to 4 concise bullet points focusing on: - Subprocess delegation - Server-managed execution - Auto-approval - Metrics collection This keeps content at the conceptual level users care about, rather than implementation details (method names, event types). Co-authored-by: openhands <openhands@all-hands.dev>
SummaryI've successfully applied the outstanding PR review suggestion for PR #351. Change Made:
The Change:Before: A 7-step numbered list with implementation details like After: 4 key architectural bullet points:
Checklist:
Commit:
|
Summary
sdk/guides/agent-acp.mdxdocumentingACPAgentusage, configuration, metrics, and cleanupexamples/01_standalone_sdk/40_acp_agent_example.pyfrom software-agent-sdk#2133docs.jsonContext
This branch is needed by the
check-documented-examplesCI job on software-agent-sdk PR #2133, which checks out a matching docs branch (feat/acp-agent) to verify that new examples are documented.🤖 Generated with Claude Code