Tracerelay

TraceRelay Plugin Support

Codex

Run:

bash ./scripts/install_codex_plugin.sh

It creates:

• ~/plugins/tracerelay
• ~/.agents/plugins/marketplace.json

The installer reads ./.env from the repository and writes a home-local MCP config for the plugin. Codex connects to the running docker-compose MCP server through .codex-plugin/mcp.json at http://127.0.0.1:5064/mcp by default. If you change TRACERELAY_PLUGIN_MCP_URL, rerun the installer.

Claude Code

Run:

bash ./scripts/install_claude_code_plugin.sh

It installs:

• local marketplace: tracerelay-local
• plugin: tracerelay

Rerun the installer after changing .env or plugin files so Claude Code picks up the latest TraceRelay behavior. Claude Code uses the root .mcp.json and expects the docker-compose MCP server to already be running at http://127.0.0.1:5064/mcp by default.

Natural prompts that should route well in Claude Code:

• Research ASPI and structure what matters before searching again.
• Analyze this company and use what we already learned before looking for more.
• Continue what we learned about ASPI and use prior findings before searching again.
• What changed in the latest run and why did it retry?
• Structure this company and keep the previous memory in play.
• Before searching again, tell me what information is still missing and what queries we should run.

Preferred routing in Claude Code:

• structure_subject for profiling, organizing, mapping, or structuring a subject
• continue_prior_work for follow-up work on the same subject
• task_status when a long-running TraceRelay call returns pending: true
• inspect_latest_changes for retry, schema-change, or branching review
• subject_graph when you want the persisted composite-subject topology, branch plan, or branch bundle directly
• task_relations when you want parent/child branch execution links for a task
• subject_relations when you want graph edges for a subject or scope without reopening the whole task
• plan_next_step before generic search or ad hoc action
• prepare_search_queries when external search is needed

TraceRelay may recheck the abstract family after the initial interpretation when the requested schema shape points elsewhere. Composite prompts such as comparisons, supplier/customer analysis, or relationship mapping can also persist a subject graph and child branch tasks instead of flattening every subject into one key. Use inspect_latest_changes to see initial_family, the final family, any family_revised or family_branch_selected event, the selected strategy branch, the latest chosen branch, and controller telemetry from the latest decision. Use subject_graph, task_relations, or subject_relations when you need the branch graph itself rather than the broader task trace payload. If task_evolve, structure_subject, or continue_prior_work returns pending: true, poll task_status with the returned task_id or job_id instead of retrying the original request.