docs: document TypeScript client boundaries - #356
Conversation
Clarify the client API boundary and related repository responsibilities. Fixes #355 Co-authored-by: openhands <openhands@all-hands.dev>
Endpoint auditContract: pinned release artifact
Actionable client-only calls (0)none Actionable server-only operations (12)
Documented non-divergences (13)Client calls intentionally absent from the filtered contract (11)
Reason: Operational Agent Server endpoints intentionally excluded from the filtered public release artifact.
Reason: Client-ahead API stacked on the pending Agent Server meta-profiles implementation.
Reason: Client-ahead API stacked on the pending Agent Server pre-flight LLM validation endpoint. Server operations covered by an exposed browser URL (2)
Reason: RemoteWorkspace.startWorkspaceSession exposes these authenticated URLs for browser iframe and file requests; they are not HttpClient method calls. |
|
🤖 OpenHands is reviewing this PR. Head commit: This comment was posted by an AI agent (OpenHands). |
all-hands-bot
left a comment
There was a problem hiding this comment.
This review was created by an AI agent (OpenHands) on behalf of the repository maintainers.
Verdict: Approve. Risk: Low.
This is a documentation-only PR (+18/-1 across three Markdown files) that adds repository ownership boundaries and cross-repository placement guidance to AGENTS.md, README.md, and CONTRIBUTING.md. The content is accurate and consistent with the repository's existing architecture description:
- The SDK → OpenAPI contract → TypeScript client → Agent Canvas flow is correctly described.
- Repository links to
software-agent-sdk,OpenHands/OpenHands, andOpenHands/automationare valid and correctly attributed. - The guidance to close and relocate misplaced PRs rather than merge them here aligns with the cross-repository boundary policy already documented in
AGENTS.md. - The
CONTRIBUTING.mdadditions integrate cleanly with the existing PR checklist.
No material bugs, security concerns, or design flaws were found. The change is internally consistent across the three files (minor wording variation between them is acceptable for audience/context). No inline comments are warranted.
Keep the cross-repository ownership model consistent with OpenHands extensions. Co-authored-by: openhands <openhands@all-hands.dev>
|
🤖 OpenHands is reviewing this PR. Head commit: This comment was posted by an AI agent (OpenHands). |
all-hands-bot
left a comment
There was a problem hiding this comment.
This review was created by an AI agent (OpenHands) on behalf of the repository maintainers.
Verdict: No material findings. Risk: Low.
This is a documentation-only PR (+18/-1 across AGENTS.md, CONTRIBUTING.md, and README.md) that adds repository ownership boundaries and cross-repository placement guidance.
The content is accurate and internally consistent:
- The SDK → OpenAPI contract → TypeScript client → Agent Canvas flow is correctly described in all three files.
- Repository links to
software-agent-sdk,OpenHands/OpenHands,extensions, andautomationare valid and correctly attributed. - The ownership split (backend behavior in the SDK, typed API access here, UI in Canvas, automation lifecycle in
automation) is consistent with the repository's existing architecture documentation. - The guidance to close and relocate misplaced PRs aligns with the cross-repository boundary policy.
- The
CONTRIBUTING.mdchecklist additions integrate cleanly with the existing PR guidance.
One minor inconsistency (not blocking): CONTRIBUTING.md omits OpenHands/extensions from its ownership list, while AGENTS.md and README.md both include it. This is a minor completeness gap rather than an error, since CONTRIBUTING.md focuses on the most common misplacement targets.
No bugs, security concerns, or design flaws were found. No inline comments are warranted.
HUMAN:
I reviewed the TypeScript client architecture and contributor guidance, then documented its API ownership boundaries and cross-repository workflow.
AGENT:
This pull request was created by an AI agent (OpenHands) on behalf of the user.
Why
Contributors need to distinguish typed Agent Server API access from backend behavior, Agent Canvas UI, and automation lifecycle code. This prevents duplicated logic and PRs being opened in the wrong repository.
Summary
AGENTS.mdandREADME.md.CONTRIBUTING.md.Issue Number
Fixes #355
How to Test
Review the three changed Markdown files for accurate repository links, API ownership, and contribution guidance.
Video/Screenshots
Not applicable: documentation-only change.
Type