[Question] Claude Code as a third-party agent harness — status and roadmap?

Hi team,

The third-party agent harness shipped in the 2.2.0 betas is a great addition — Codex and Qoder are already supported in the console, while Claude Code is still marked "Coming soon".

**What I can see in the source** (`harnesses/registry.py`): the `claude` catalog entry is still a placeholder — `coming_soon=True` with an empty `HarnessCapabilities()` — while the framework itself (base/runtime/session/streaming plus the Codex and Qoder adapters) looks complete and well designed.

**Questions**

1. Is the Claude Code harness in active development? Any rough target release (a 2.2.0 beta or 2.3)?
2. In the meantime, what is the recommended way to use Claude Code from QwenPaw — ACP delegation via the `claude_code` runner (`npx @zed-industries/claude-agent-acp`), or another approach?
3. Will the existing ACP issues with Claude Code — #6792 (deprecated npm package name) and #4824 (protocol mismatch) — be addressed as part of the native harness work?

Thanks! Looking forward to this one.

Start with harnesses/registry.py, especially the placeholder Claude entry, and compare it with the Codex and Qoder adapters. Read ACP issues #6792 and #4824 for the reported Claude Code integration problems. This issue is done when maintainers clarify the native harness status, recommended interim runner, release outlook, and relationship to those ACP issues.

Vom Indexierungsmodell aus dem Issue-Text verfasst.