AI assistants

Deckard gives AI assistants in VS Code eight tools through VS Code’s language model tool API. Any assistant using those tools can call them; in GitHub Copilot’s agent mode they appear in the tools picker. Assistants that connect only through MCP servers cannot see them; see Claude Code and other MCP clients.

In a workspace with types, deckard_query takes the type’s fields as conditions, and its answer, like deckard_list_tags’s, names the workspace’s types and their fields on its second line, Types in this workspace: Team (lead, owns, on-call, channel; reverses: members), …, so an assistant knows what it can ask.

Reading. The first time an assistant calls a tool in a session, VS Code asks you to allow it. Deckard sends nothing itself; the assistant may send what it gets to its model service. Set deckard.assistantTools to false to turn the tools off. Calls are timed in Deckard’s log.

Writing. The assistant asks before every write, and nothing is written until you approve the exact line in the refactor preview, even for one note. A change is refused if the line is no longer the task, or the question, the index knows. Deckard: Undo Last Change takes a write back.

Suggest steps

In Break into Steps…, Suggest steps asks a VS Code language model (GitHub Copilot’s or another extension’s) for a task’s steps. It appears only when a model is installed and names the model.

This is the only place Deckard itself sends anything to a model.

Claude Code and other MCP clients

Deckard can offer the same eight tools to Claude Code and other Model Context Protocol clients. Set deckard.mcpServer.enabled to true, or run Deckard: Copy MCP Server Setup, which offers to turn the server on and copies the command that adds Deckard to Claude Code:

claude mcp add --transport http deckard http://127.0.0.1:39217/mcp --header "Authorization: Bearer <token>"

← Themes and Display · All topics · Commands →