Multi-platform support — Codex, Cursor, OpenCode, Gemini CLI adapters (roadmap)

[ZaxShen]

Vision

TMB shouldn't be Claude-Code-only forever. The bro doctrine — Human → bro → SWE with pr-reviewer as push gate, Lego templates, lazy bootstrap, full audit trail in SQLite — is platform-agnostic in concept. Today's implementation is Claude-Code-shaped, but most content (skills, agent templates, planning protocol, MCP server) ports cleanly.

This issue tracks the per-platform adapter roadmap.

Structural readiness (PR #73)

• .codex-plugin/ placeholder
• .cursor-plugin/ placeholder
• .opencode/ placeholder
• gemini-extension.json placeholder
• Per-platform persona files (CODEX.md, CURSOR.md, GEMINI.md)
• docs/multi-platform.md strategy doc

What's already cross-platform

Asset	Status
skills/tmb_*/SKILL.md	✓ Portable (frontmatter + body schema is shared across Claude/Codex/Cursor)
templates/skills/*	✓ Portable (plain markdown)
templates/agents/*.md body	✓ Portable
mcp/trajectory-server/	✓ Portable (MCP is the cross-platform standard now)

What's currently Claude-shaped

Asset	Per-platform work needed
templates/agents/*.md frontmatter	tools:, model:, isolation:, skills: are CC conventions; adapter translates
hooks/hooks.json + scripts/hooks/*.sh	Each platform has different hook event names + decision protocol
CLAUDE.md (bro persona trigger word + first-action chain)	Trigger mechanism is CC-specific; doctrine portable

Per-platform sub-issues (open as work begins)

• Codex adapter — fill in .codex-plugin/plugin.json, write CODEX.md persona, port hooks where applicable. Sync to OpenAI's marketplace channel via scripts/sync-to-codex-plugin.sh (per Superpowers' pattern).
• Cursor adapter — fill in .cursor-plugin/plugin.json, write CURSOR.md, author Cursor-format hooks under hooks/cursor/.
• OpenCode adapter — author .opencode/plugins/tmb.js entry point.
• Gemini CLI adapter — fill in gemini-extension.json properly, write GEMINI.md persona with @./skills/... references.
• (Maybe) GitHub Copilot CLI — research adapter shape.

Trigger to act on per-platform sub-issues

When ≥3 distinct users ask for support on a specific platform, OR when a paying customer makes it a contract item, the corresponding adapter sub-issue gets opened and prioritized.

Until then: placeholders stay placeholders. The repo benefits from structural clarity even if no adapter ships for years.

Related

• PR 🌐 chore: multi-platform placeholder structure (Codex, Cursor, OpenCode, Gemini) #73 — placeholders + strategy doc
• obra/superpowers — canonical example of the multi-platform pattern in the AI-skills ecosystem

[ZaxShen]

Issue tracking moved to Linear. This issue continues as TRU-14: https://linear.app/trustmybot/issue/TRU-14

GitHub issues are no longer the active tracker for this project — see the Linear workspace for current state. Closed-as-migrated, not closed-as-resolved.

[ZaxShen]

Disregard the prior 'closed-as-migrated' comment. GitHub remains the public issue tracker for this project — file new issues, PRs, and discussion here as normal. TMB team mirrors this issue internally to Linear (TRU-14) for our own workflow, but that mirror is auto-synced from GitHub — contributors don't need a Linear account.

[ZaxShen]

Closing — focusing on v0.8.x. Planning lives on GitLab milestones (v0.8.0 / v0.8.1). Will re-mirror active items to GH once tri-source schema sync (#48) lands.