One client. Five runtimes.
Each first-party adapter translates one coding agent's events into the Helmora Protocol and reports its real capabilities. Shared UI stays consistent; runtime-specific controls appear only where they work.
First-party adapters
Built into the current private pre-alpha and maintained with pinned runtime contracts and adapter-specific regression suites.
Claude Code
Persistent SDK sessions plus local hooks for streaming, approvals, structured questions, diffs, plans, models, effort, permissions, usage windows, account profiles, workflows, and external-session updates.
Codex
Hosts the pinned Codex app-server protocol for sessions, streamed tools and diffs, approvals, questions, plans, reviews, models, reasoning effort, permission posture, usage windows, MCP, and external-thread mirroring.
GitHub Copilot
Pinned Copilot SDK integration with streaming, approvals, structured questions, background-task lifecycle, per-chat model selection, working-directory changes, and monthly plan usage.
OpenCode & Goose
One reusable Agent Client Protocol adapter with per-runtime presets. OpenCode and Goose ship today; a new ACP runtime is a preset row plus verification, not a new adapter.
OpenClaw
Frozen integration. Existing pairings keep working, but new OpenClaw setup was retired from the product in August 2026 and the adapter no longer receives feature work.
Not in the current build.
Protocol research is not adapter availability. These runtimes should not be inferred from schema names, planning docs, or UI placeholders.
No Helmora adapter
Researched in mid-2026 and removed from the active plan; the generic ACP core took its roadmap slot. Not wired into the bridge or app.
Preset-shaped, but verified first
The generic ACP core makes a new ACP runtime a preset row — but a runtime is only supported once its preset ships and is verified. Speaking ACP alone does not make an agent work in Helmora.
No adapter today
A subprocess wrapper has been discussed, but it is not part of the current bridge or release scope.
A deliberate boundary.
The adapter SDK and repository are proprietary during pre-alpha, so there is no public extension package or build-your-own guide yet. MCP servers are managed through each supported runtime rather than presented as separate Helmora agents.