Extending TF Code
TF Code can be extended with extensions: one installable bundle that adds tools, slash commands, subagents, skills, hooks, MCP servers and standing context at once.
If your team has conventions an agent keeps getting wrong, an extension is how you fix it once and share it, instead of pasting the same prompt into every session.
One bundle, everything in it
writing-companion/
├── tfcode-extension.json # the manifest
├── TFCODE.md # context added to every session
├── commands/writing/polish.md
├── agents/writer.md
├── skills/house-style/SKILL.md
└── tools/count-words.ts
Use one
tfcode extension link ~/src/writing-companion # live edits
tfcode extension approve writing-companion # if it ships code
tfcode extension list
Enable the capability once in tfcode.json:
{ "perks": { "extensions": true } }
Anything that ships code needs an explicit approval, keyed by the bundle's content — editing it asks again. Context-only bundles need no approval because nothing runs.
Build one
tfcode extension new my-extension --template hello-tool
No build step: TypeScript is transpiled in-process, so a saved file runs on the next session.
Full documentation
The complete guide lives with the TF Code documentation:
- Extensions — what it is, and how it differs from a plugin or a skill
- Authoring — build one start to finish
- Reference — every field, hook, command and error
- Migrating — from Matilda, Claude or Gemini
- Installing and trusting — the user-facing side