Track additional integrations with existing coding and agent tools

Overview

Registered integrations are OpenCode, Codex, Claude Code/Desktop, CLion and RustRover. Browser-use, VS Code/Cline, IntelliJ, Xcode, Zed and personal-agent adapters are not registered; source explicitly requests investigating this breadth.

Priority: P2 / post-mvp. Impact: roadmap improvement. Initial planning estimate: Medium; refine after inventory. This issue does not add a release blocker.

Current evidence

Registered integrations are OpenCode, Codex, Claude Code/Desktop, CLion and RustRover. Browser-use, VS Code/Cline, IntelliJ, Xcode, Zed and personal-agent adapters are not registered; source explicitly requests investigating this breadth.

• Source: src/commands/cmd_editors.cpp#L75
• Source: src/commands/cmd_harness.cpp#L24

Design and implementation plan

Create a compatibility inventory, choose adapters by actual endpoint support, reuse generic serving/configuration and upstream tooling; do not promise every ecosystem example. Separate child work by adapter when selected.

1. Reconcile the current implementation and any already completed work with the evidence above.
2. Record the owner, selected scope, dependencies and unresolved decisions before implementation.
3. Implement or execute the selected scope using existing components and artifacts.
4. Attach reproducible validation or outcome evidence and record any deferred work.

Acceptance criteria

• Inventory browser-use, VS Code/Cline, IntelliJ, Xcode, Zed and Hermes/OpenClaw; identify manual versus first-class integration.
• For each selected adapter, preserve existing config, validate absent executable, tool use, streaming/cancel and real model task.
• Mark unsupported integrations truthfully; no new proprietary coding agent.

Related work and deduplication

No existing issue has this acceptance scope; existing release defects remain separate.

No exact existing issue found in the all-state inventory.

Requirement provenance

Reconciled September 13, 2026 against WALLY_CLOUD_PRODUCT_SOURCES.md (SHA-256 e601b7b154b750965fa8d25d4533d3542621bd00b3bb30038c1fae553a549e7b) and the consolidated requirements report. Historical proposals are not evidence of current delivery, customer agreement or approved pricing.

Start by reviewing src/commands/cmd_editors.cpp#L75 and src/commands/cmd_harness.cpp#L24, then reconcile those registrations with the requested integration inventory. Document ownership, dependencies, selected adapters and unresolved decisions before implementation. Done means selected integrations have reproducible validation evidence, unsupported ones are marked honestly, and deferred work is recorded.