Skip to content

AI Tools

When the AI responds to your messages, it can call tools to gather information or make changes. You’ll see tool calls rendered in the chat as expandable blocks showing inputs and outputs.

ToolWhat it does
readFileRead the full contents of any file in Assets/
listDirectoryBrowse the directory tree (always scoped to Assets/)
searchCodeFull-text search across all C# and other source files
findSymbolsFind classes, methods, or fields by name
goToDefinitionJump to where a symbol is defined
getReferencesFind all usages of a symbol across the project
ToolWhat it does
writeFileCreate a new file
editFileEdit an existing file using find-and-replace patches
runCommandRun a shell command (dotnet build, git, Unity CLI, etc.)
ToolWhat it does
getDiagnosticsGet compiler errors, warnings, and info messages from the language server

These tools query the indexed knowledge graph built from your project’s files.

ToolWhat it does
projectOverviewHigh-level summary: script count, scene list, component usage stats
searchProjectSearch entities by name, semantic meaning, or auto (hybrid)
queryRelationshipsTraverse edges in the graph — inheritance chains, scene references, component usage
inspectEntityDeep dive into a single entity with all cross-references
resolveGuidConvert a GUID to an asset path or vice versa

The searchProject tool supports three modes:

  • name — exact or partial name match
  • semantic — uses vector embeddings to find conceptually similar code (e.g. “scripts that handle enemy damage” finds EnemyHealth.cs even if the words don’t match)
  • auto — the AI picks the best mode based on your query
  • Be specific about scope — “in PlayerController.cs” or “in the MainScene” helps the AI focus
  • Ask about errors with context — after a Unity console error, just ask “why is this happening?” — the AI already has the stack trace
  • Let the AI explore — for complex questions, let it call multiple tools rather than trying to paste in all context yourself