Roadmap
Runtime, integration, and deployment status in one place.
Convoy exposes more runtime slugs and integration surfaces than it can fully execute today. This page is the single source of truth for which runtimes and surfaces are actually supported end to end versus where the config exists but execution is incomplete. Keep this page honest — do not re-scatter status notes across feature pages.
Runtime execution
| Runtime | Thread execution | Config surfaces | Notes |
|---|---|---|---|
| Claude Code | Supported | CLI, MCP, skills, init | The production runtime: interactive approvals, plan mode, steering, live deltas (on by default), resume. |
| Codex | Supported | CLI, MCP config, skills, init | Default app-server transport (codex-cli ≥ 0.142): mid-run approvals and questions, Plan mode, steering, live deltas, context-window meter. convoy connect --codex-exec falls back to codex exec --json: Agent/Sandboxed modes, model + reasoning-effort selection, resume, no mid-run interaction. |
| OpenCode | Supported | CLI, MCP config, skills, init | Interactive opencode serve + SDK transport: Agent/Ask-to-approve/Plan modes with in-thread approvals and questions, dynamic per-machine model catalog with per-model variants (reasoning effort), streaming deltas, resume. Requires OpenCode ≥ 1.14.19. |
| Amp / Droid / Cursor / Gemini / CodeRabbit / Copilot / Other | Not implemented | Generic backend runtime registered, "Soon" badge in the UI | No CLI-side runner yet. Running a thread against these slugs will fail explicitly. |
Meaning of the columns:
- Thread execution — whether
convoy connectcan actually run threads for this runtime. - Config surfaces — whether Convoy writes config, installs skills, or offers selectors for the runtime even though execution is not live.
See Adding a runtime for what it
takes to move a runtime from "config only" to "executable".
Planned / experimental deployment paths
- Self-hosted Convex — Convoy was built against managed Convex. Running
the full stack against self-hosted Convex is possible in principle but is
not tested end to end. See
Self-hosting (Experimental).
How to interpret "planned" copy elsewhere
When another docs page mentions a runtime or integration as "planned" or "experimental", it should link back here for current status rather than repeating the caveat. If you see a stale scatter, fix it in the same PR.