Skip to content

T-TI5B-harness-targets-codex-cursor-gemini

Status: closed/done · Impact: high · Complexity: large

Prove the canonical model reaches three more, structurally-different control planes. Each renders the same capabilities/hooks/MCP/permissions/docs in its own idiom, so one edit propagates everywhere.

LocationRole today
plugin/lib/services/harness/exporters/Only claude + json + a skills-only codex stub. No cursor/gemini; no MCP/hooks projection.

Full codex (AGENTS.md + prompts + config.toml [mcp_servers]), cursor (.cursor/rules/*.mdc + mcp.json + commands), and gemini (GEMINI.md + .gemini/settings.json + TOML commands) targets, each mapping the model to native constructs and noting where a host lacks a concept.

  1. Add cursor.ts and gemini.ts; upgrade codex.ts to project MCP + config.
  2. Register all in the target registry.
  3. Per-target tests pinning the native shape.
LocationKindChange
plugin/lib/services/harness/exporters/codex.tsmodifyAdd config.toml + MCP.
plugin/lib/services/harness/exporters/cursor.tsnewCursor target.
plugin/lib/services/harness/exporters/gemini.tsnewGemini target.
plugin/lib/services/harness/exporters/index.tsmodifyRegister targets.
  • harness export codex|cursor|gemini each emit their native surface incl. MCP.
  • Each target has shape-pinning tests.
  • tsc + tests green.

Round-trip importers for the new hosts.


← Back to Tasks