Multi-Runtime Support for Codex, Amp, and OpenCode

Status: Partially implemented — built-in claude, codex, amp, and opencode launch support is shipped; deeper runtime parity remains

Canonical Docs For Shipped Behavior

• jackin load — --agent <claude|codex|amp|opencode> and launch behavior.
• Workspaces and Configuration File — default_agent, last-used agent behavior, and persisted state.
• Role manifest and Creating roles — role-author support for multi-agent manifests.
• Agent Authentication — current auth modes for Claude Code, Codex, Amp, and OpenCode.

This roadmap item no longer repeats shipped runtime selector, state-path, or manifest details. Use the standard docs above for current behavior.

Remaining Work

The project now has basic built-in runtime support. The remaining work is parity depth:

• runtime-native extension surfaces for Codex, Amp, and OpenCode;
• richer Codex/Amp/OpenCode config defaults and documented tuning;
• MCP / skill integration beyond simple config-file injection;
• runtime-specific auth and state behavior where Codex, Amp, or OpenCode need something more than sync, api_key, and ignore;
• clearer version/update behavior for non-Claude runtimes.

Non-Goals

• A third-party runtime marketplace.
• Automatic translation of Claude plugins into Codex config, Amp skills, or MCP servers.
• Pretending all runtimes should expose the same feature set.

Open Questions

• Which Codex, Amp, and OpenCode settings deserve first-class role-manifest fields rather than generated defaults?
• Should runtime-native skills/MCP wiring live in each runtime adapter or in a shared extension model?
• Do Codex, Amp, and OpenCode need additional auth modes beyond sync, api_key, and ignore?
• How much runtime update detection should jackin own for non-Claude CLIs?