Documentation Navigation
Tools

Toolset

The core toolset behind every agent.

Tools are how an agent leaves the transcript and touches your machine. Codey ships the file, shell, search, and reasoning tools below on every client, and adds the Pro workspace tools where they apply.

#Core set

ToolDoesWrites
readRead files with offset and imagesNo
writeCreate or overwrite whole files, plus appendYes
editExact string replacementYes
apply_patchAtomic multi-file create and updateYes
bashRun shell commands in a sessionYes
globFind files by patternNo
grepSearch file contentsNo
webfetchFetch a URL as textNo
lspDefinitions, references, and symbolsNo
taskDelegate work to a subagentDelegated
todowriteTrack the session task listSession
skillLoad domain skillsNo
memoryRecall and store durable factsStore

#Workspace set

ToolDoesAvailability
browserDrives the Chromium in the Desktop side panelPro · Desktop
design_systemBrowse, read, and author the design-system catalogPro
blueprintWrite an approved plan onto the Blueprint boardPro
scheduled_taskCreate and run scheduled tasksAll tiers
open_sessionOpen or fork a session from inside a sessionAll tiers
open_fileOpen a file in the workbench for the userAll tiers
questionAsk the user a multiple-choice questionDesktop · app · CLI
  • Gated extras — websearch and codesearch load for the free model provider or with CODEY_ENABLE_EXA or CODEY_ENABLE_PARALLEL. Pin the provider with CODEY_WEBSEARCH_PROVIDER=exa|parallel (no API key required; EXA_API_KEY / PARALLEL_API_KEY only raise limits).
  • Apply patch — edits go through one multi-syntax patch engine with tiered context matching, so every model writes files the same way and shell heredocs stop corrupting them. Models with strict tool schemas get apply_patch in place of edit and write.
  • Experimental — the batch tool runs a set of edits as one step when experimental.batch_tool is enabled.

#Document tools

Five built-in servers give agents hands outside the codebase. They show up as Codey features rather than third-party tool names, and each one can be turned off individually in config.

Shown asServerDelivers
docscontext7Current library references, not remembered ones
sheetsexcelSpreadsheets and cleaned tabular data
pdfpdf-toolkitRead, extract, and package PDFs
writerwordDocuments, reports, and briefs
slidespptDecks built from rough notes
codey.json
{
  "builtin_mcp": {
    "excel": { "enabled": false }
  }
}
  • Pro gated — the built-in document servers need Pro; MCP servers you configure yourself do not.
  • Browser is not one of them — Playwright never launches a second, unrelated browser. On Desktop it is the browser tool; everywhere else it stays disabled.

#Permissions

Every tool sits under a permission tier — allow, ask, or deny — set globally, per project, or per agent. Deny survives pipes, flags, and rephrasing.

#See also