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
{{ message }}
Repository navigation
[P2] Add a Claude adapter behind the secure worker contract #35
Claude workers need a separate adapter. Their tool access, model catalog, Windows support, and sandbox behavior differ from AGY and Codex.
Deliverable
Implement a Claude adapter using the contract from #31. Use live capability and model discovery where the host supports it. Document the isolation requirement for hosts without a suitable sandbox.
The adapter must honor the orchestrator's static assignment constraints. Native workers may provide concurrency, but they do not replace ownership, verification, or cleanup controls.
Acceptance criteria
The adapter launches one bounded Claude worker assignment and returns the normalized result.
It reports supported tools, structured output, model availability, effort levels, process identity, and artifacts.
It accepts internal preferences such as fast, balanced, and deep without publishing hardcoded model IDs.
It cannot create a child assignment or widen the orchestrator's security constraints.
It registers every process, worktree, and artifact with the resource ledger.
It supports cancellation, timeout, retry, quota handoff, and resume through the shared lifecycle.
Execution scope checks and final gates run before any result reaches the caller.
Unsupported sandbox or host capabilities fail closed with a recorded reason.
Fake Claude responses cover success, malformed output, cancellation, and scope failure.
Documentation states which Claude features are tested and which hosts require an isolated runtime.
Activity
anthonyandrei commentedon Sep 4, 2026
Resolved by PR #39 (#39). The merged implementation covers this issue, and the targeted acceptance tests pass. Closing as completed.