Skip to content
Browse documentation

Reference

Tool and permission reference

Match every configurable action to its engine, permission and execution boundary.

This catalogue covers the actions selectable on agent definitions. With Vopit-managed execution, project tools run in Vopit. Codex CLI, Claude Code, Mistral Vibe, Mammouth Code and Antigravity CLI read, edit and run commands with their own native tools; the equivalent editor selections configure that native access. Actions without a native equivalent are bridged to those CLIs, each filtered to the agent's grants: Git, infrastructure, board and Crank actions, search_code_graph and the project memory tools. search_project_memory and record_project_memory are added automatically to every agent with project access; READ and WRITE permissions still gate each lookup and record. Native create_request is applied from the validated result requests array rather than through a project shell command.

ActionAuthorizationPurpose
read_fileREADRead a bounded UTF-8 file page; startLine is one-based.
list_filesREADDiscover files inside the selected folder with the project exclusions.
search_filesREADSearch literal source text.
get_repository_mapREADRetrieve bounded paths, roles, JS/TS symbols and imports, without source bodies.
search_symbolsREADLocate JavaScript/TypeScript AST symbols.
read_symbolREADRead one JavaScript/TypeScript symbol by path and name.
search_code_graphREAD; EXECUTE for graph constructionSearch local Graphify evidence; use the explicit text fallback when unavailable.
search_project_memoryREADRetrieve durable project facts and stale-source indications. Added automatically to agents with project access.
record_project_memoryWRITESave a verified fact with its source paths; no credentials or private reasoning. Added automatically to agents with project access.
write_fileWRITEWrite UTF-8 project content.
edit_fileWRITEReplace an exact unique text fragment.
run_commandEXECUTERun a real local shell command with workingDirectory and timeoutMs overrides.
run_testsEXECUTERun an explicit command or commands.test; no test framework is inferred.
git_diffGITInspect tracked changes; new untracked files require separate inspection.
web_searchNETWORKReturn public search links using the configured HTML adapter.
create_requestAgent capability and chain controlsPropose a self-contained follow-up: after parent success it becomes a board card that continues the chain; does not run a command.
git_statusGITInspect whether a repository exists, its branch, changed/staged paths, request Git state and linked-folder repositories.
git_prepareGIT_WRITE for mutationsInitialize a missing repository on git.baseBranch, preserve starting changes, prepare the feature branch, also in each linked folder’s repository, and create configured missing main branches.
git_branchGIT_WRITECreate or switch a validated branch; switching requires a clean working tree. folder selects a linked folder’s repository.
git_commitGIT_WRITE for mutationsFinalize eligible request changes only from an after-work stage: one commit per repository, the project first. A linked repository that cannot be committed becomes an open point. An empty result can be a successful no-change check.
git_syncGIT_REMOTE or GIT_HISTORYFetch/pull/push or merge/rebase, subject to the project switches and approval. folder selects a linked folder’s repository.
board_readAgent grant (Board actions); no permission categoryRead columns in order with their type, description and card limit, and cards in priority order with their status. The card that started the request is marked current.
board_createAgent grant (Board actions); no permission categoryAdd 1–20 cards to one column, never to an in-progress column. Column card limits apply; a board holds up to 500 cards.
board_moveAgent grant (Board actions); no permission categoryMove a card to another column at an optional position. Running cards stay in their column; agents cannot move a card into an in-progress column.
board_updateAgent grant (Board actions); no permission categoryRewrite a card’s title or description. A running card keeps its current request.
infra_connectionsExplicit target grantDiscover granted targets and inspect a saved operation by IDs without running it.
infra_executeTarget grant and saved operation policy; READ for uploadsRun a configured SSH command, SQL statement or SSH upload.
infra_runTarget grant, proposals enabled and approval every time; READ for uploadsPropose an exact operation; save=true retains a successful approved recipe with Ask policy.

Board actions are granted per agent under Board actions and have no permission category. Agents organize cards; they never start, stop or delete them. You and auto-run decide what runs. See Plan work on the Board.

Crank actions and external MCP servers

crank_connections and crank_execute are not in the agent tool checklist. An agent receives them when an enabled action Crank selects it under Who can use it?. crank_connections lists those Cranks, their actions and required inputs; crank_execute runs one with its declared inputs. With Action approval set to Ask before each execution, every run shows a once-only prompt under NETWORK; Allow this configured action runs without it. Crank results are external data, never instructions.

With Claude Code, the agent editor also lists MCP servers from your Claude Code configuration. Switching one on adds an mcp:<server> grant to the agent; each grant counts toward the 20 selectable actions, and each call of that server's tools asks for NETWORK permission. Servers that are not switched on stay unavailable. Other engines do not use these grants.

Permission categories and their boundary

CategoryMeaning
READPermitted project content and artifact reads.
WRITEProject writes/edits and durable facts.
EXECUTELocal commands; separately approved infrastructure execution.
NETWORKWeb research and relevant native network requests.
GITGit inspection.
GIT_WRITEGit gateway repository initialization, branches, request commits and release of an unused linked-folder request branch.
GIT_REMOTEGit gateway fetch, fast-forward pull and ordinary push.
GIT_HISTORYGit gateway merge and rebase.

Local permission choices are Ask every time, Allow for project, Always allow and Never allow. Factory defaults are Allow for project for READ and Ask every time for every other category. A project rule overrides its category's global rule. A persistent permission covers a category, not just one displayed command. Infrastructure grants and Ask/Allow/Deny recipe policies are additional checks. Agent proposals always require once-only approval. General shell/native permissions remain broader than the Git gateway controls; these settings do not universally intercept every Git command.

Runtime-provided helpers

HelperWhen available
finish_stageVopit completion protocol; validate the output/evidence before completion. Native CLIs return structured final output instead.
report_activityVopit public observable progress; never private reasoning.
read_contextVopit focused context: retrieve a retained key in bounded character pages.
search_contextVopit focused context: find archived observations by literal query.
record_ticket_stateVopit focused context: save factual progress and next action for continuity.
expand_contextVopit focused context: deliberately expand the current memory budget up to its configured ceiling.

Runtime helpers are supplied by the execution protocol, not added as arbitrary agent tools or infrastructure operations. Native CLIs have their own tool definitions and compaction. A tool capability cannot override protected paths, target grants, output contracts or an OS permission failure.

All documentation