Add MCP servers, hooks and commands

Why each extension waits for your trust is explained in Extensions.

Prepare and trust the project

talos init              # creates .talos-cli/ with commands/, extensions/ and an empty config.json
talos project status    # what is trusted, why, and the project files that can run code
talos project trust     # trusts the project and the current snapshot of its executable files

talos project revoke removes the trust: the project’s hooks, MCP servers, plugins and commands stop loading.

An MCP server

talos mcp list          # the servers, with their source, trust and state
talos mcp test <id>     # starts it and checks protocol, tools, trust, permissions and recent logs
talos mcp trust <id>

Its tools then go through your permissions like any other — as Mcp(server:operation).

A hook

talos hook list
talos hook dry-run <id> <event>   # runs it with a synthetic event, the way a real one would
talos hook trust <id>
talos hook history <id>           # its last runs

talos hook quarantine <id> denies a hook until you release it; releasing does not restore its trust.

A plugin

talos plugin install <source>
talos plugin list
talos plugin trust <id>

Installing does not make a plugin run: the project’s trust must cover the new package first.

A command of your own

A custom command is a Markdown file, for example in .talos-cli/commands/ of the project; its text becomes the prompt, with {{arg1}}, {{arg2}}… for its arguments. In the interactive screen it is a slash command.

talos command list                 # commands, skills and workflows, with where they come from and whether they are valid
talos command run <name> <arg>     # prints the prompt it expands to