Build · 8 min read
Terminal and coding tools
Understand file tools, patches, commands, interactive terminals, and background processes.
File and search tools
Gyroscape locates files, searches symbols and text, reads content, and applies precise patches. Independent read-only discovery can run in parallel. Mutating operations are coordinated to reduce stale writes.
If a patch no longer matches, the agent rereads and repairs it instead of silently replacing the whole file.
Command execution
Commands run from the active project unless a narrower directory is selected. Short commands return inline. Long commands can continue in a managed session for output, input, or interruption.
Interactive commands can use a real terminal. Background sessions stay with the task until they finish or are stopped.
Run the focused authentication tests. If still running, keep the command in a background terminal,
read new output until it finishes, and do not restart the development server.Describe intent in plain language; Gyroscape selects the tool flow.
Tool calls stay paired
Calls are tracked until return, interruption, or bounded cleanup. Late results reconcile with the original call. Incomplete streamed tool arguments are not executed.
Malformed or unknown calls retain their identity for correction. One tool error should not discard valid root work.
Sensitive commands
Commands outside the normal sandbox, broad filesystem access, or other sensitive boundaries require approval. Review the command and target. Auto-approve does not turn unrestricted execution into silent consent.
Related articles