VT Code Companion

Use the connected server's search, fetch, start_task, get_task, and cancel_task tools. The service owns one workspace and permits one active task.

Before declaring tools unavailable, use the host's tool-search or tool-discovery capability, when provided, to find VT Code Companion and its start_task and get_task tools. Deferred tools may not appear in the initial tool list. Use the actual discovered names, including any server/namespace prefix. Loading this skill does not establish that its MCP tools are exposed to the conversation. Match the server identity, not just a tool named fetch or search: GitHub and other plugins can expose those names. A GitHub README is remote repository data, not evidence of access to the connected worktree or its uncommitted changes.

The local MCP process uses the binary and workspace selected by the user with vtcode --workspace <path> companion setup --binary <path>. If startup reports missing setup or an incompatible binary, ask the user to run that command with a compatible VT Code build and restart the plugin connection. Do not infer a workspace from this chat or pass a path through task tool arguments.