You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Built-in T3 Code docs-routing skill (or on-demand docs index) for agents
#39829
T3 Code ships 49 user documentation guides in docs/user/ (covering keybindings.md, composer.md, permission-modes.md, remote-access.md, secrets.md, devices.md, faq.md, and per-provider guides such as providers-antigravity.md, providers-claude.md, providers-codex.md, and cursor.md). Agents running inside T3 Code have no built-in way to reach them:
The <t3_code_instructions> prompt block covers tool-use rules (browser, devices, orchestration, PR linking) and stays tightly bounded by the Agent context budget CI check.
The t3-code MCP server exposes no MCP resources (list_resources returns empty).
T3 Code does not bundle a user-facing docs skill across providers (.agents/skills/ contains only contributor/testing skills).
When a user asks an agent inside T3 Code a product question—how to reload MCP servers in a live thread, what a keybinding does, how T3 Connect or 1Password secrets work, or why a provider behaves a certain way—the agent must guess from stale knowledge, inspect local ~/.t3/userdata/ files by hand, or query GitHub via gh. In practice, this causes agents to miss existing T3 features (for example, Ctrl+K → Restart agent session in docs/user/cursor.md) or give outdated advice.
Proposal
Expose T3 Code's own user documentation to agents on demand through a lightweight docs-routing index, without inflating the per-turn system prompt:
Mechanism
How it works
Context cost
Option A: Bundled docs-routing skill (similar to antigravity-guide or openai-docs)
Ship a small t3-code-guideSKILL.md with a topic-to-doc routing table pointing to bundled docs/user/*.md files for the running T3 version, exposed to harnesses that load skills (or via SEP-2640 MCP skills if #36098 lands).
One skill entry (name + one-line trigger description) until invoked; full doc loads only on demand.
Option B: T3 MCP resources (or a t3_docs lookup)
Publish the running release's docs/user/*.md files as read-only MCP resources on the t3-code server (e.g., t3://docs/user/keybindings.md) with a generated t3://docs/index.md mapping topics to URIs.
Zero prompt tokens unless the client/agent reads a resource; works uniformly across every MCP-capable provider (Claude, Codex, Antigravity/ACP, Cursor, OpenCode).
Recommendation: Start with Option B (read-only MCP resources on t3-code), optionally paired with a bundled t3-code-guide skill once cross-provider skill delivery exists. Because the t3-code MCP server already runs for every provider and knows the exact installed T3 Code version, serving version-matched docs/user/*.md from the package avoids provider-specific skill-discovery differences and avoids drift between the user's installed build and main on GitHub.
Constraints and tradeoffs
Agent context budget: Baseline context growth stays at zero for MCP resources (or one metadata line for a skill), so ordinary coding turns pay no extra context cost.
Version accuracy: Bundling docs/user/*.md into the server/desktop package ensures agents read documentation that matches the user's installed T3 Code version rather than a newer main commit or stale training data.
Client support for MCP resources: Not every provider surfaces MCP resources automatically without a hint. A compact skill (where supported) or a single-line pointer in <t3_code_instructions> resolves discoverability.
Smallest useful scope
Bundle docs/user/*.md with the server and expose them as read-only MCP resources on the t3-code server (plus a generated t3://docs/index.md mapping topics to URIs). Layer a bundled t3-code-guide skill on top once shared skill delivery (#14118 / #36098) is in place.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
T3 Code ships 49 user documentation guides in
docs/user/(coveringkeybindings.md,composer.md,permission-modes.md,remote-access.md,secrets.md,devices.md,faq.md, and per-provider guides such asproviders-antigravity.md,providers-claude.md,providers-codex.md, andcursor.md). Agents running inside T3 Code have no built-in way to reach them:<t3_code_instructions>prompt block covers tool-use rules (browser, devices, orchestration, PR linking) and stays tightly bounded by theAgent context budgetCI check.t3-codeMCP server exposes no MCP resources (list_resourcesreturns empty)..agents/skills/contains only contributor/testing skills).When a user asks an agent inside T3 Code a product question—how to reload MCP servers in a live thread, what a keybinding does, how T3 Connect or 1Password secrets work, or why a provider behaves a certain way—the agent must guess from stale knowledge, inspect local
~/.t3/userdata/files by hand, or query GitHub viagh. In practice, this causes agents to miss existing T3 features (for example,Ctrl+K→ Restart agent session indocs/user/cursor.md) or give outdated advice.Proposal
Expose T3 Code's own user documentation to agents on demand through a lightweight docs-routing index, without inflating the per-turn system prompt:
antigravity-guideoropenai-docs)t3-code-guideSKILL.mdwith a topic-to-doc routing table pointing to bundleddocs/user/*.mdfiles for the running T3 version, exposed to harnesses that load skills (or via SEP-2640 MCP skills if #36098 lands).t3_docslookup)docs/user/*.mdfiles as read-only MCP resources on thet3-codeserver (e.g.,t3://docs/user/keybindings.md) with a generatedt3://docs/index.mdmapping topics to URIs.Recommendation: Start with Option B (read-only MCP resources on
t3-code), optionally paired with a bundledt3-code-guideskill once cross-provider skill delivery exists. Because thet3-codeMCP server already runs for every provider and knows the exact installed T3 Code version, serving version-matcheddocs/user/*.mdfrom the package avoids provider-specific skill-discovery differences and avoids drift between the user's installed build andmainon GitHub.Constraints and tradeoffs
docs/user/*.mdinto the server/desktop package ensures agents read documentation that matches the user's installed T3 Code version rather than a newermaincommit or stale training data.<t3_code_instructions>resolves discoverability.Smallest useful scope
Bundle
docs/user/*.mdwith the server and expose them as read-only MCP resources on thet3-codeserver (plus a generatedt3://docs/index.mdmapping topics to URIs). Layer a bundledt3-code-guideskill on top once shared skill delivery (#14118 / #36098) is in place.Related
/and$menus.t3_thread_configure) when nothing routes them to it.All reactions