Files & Terminal
Anyy can read and search files, make targeted edits, apply structured patches, run shell commands, and manage background process sessions. These tools are most useful when the session has a clear Workspace and objective.
File Tools
| Capability | Behavior |
|---|---|
| Read | Reads text or supported JPEG/PNG/GIF/WebP/BMP images; large text is bounded |
| List | Lists a directory alphabetically, including dotfiles |
| Find | Finds paths by glob while respecting .gitignore |
| Grep | Searches file content with paths and line numbers while respecting .gitignore |
| Write | Creates or overwrites one file and creates parent directories |
| Edit | Replaces exact, unique, non-overlapping text regions in one file |
| Apply patch | Applies a structured patch across one or more files |
Search results and reads are intentionally bounded. Ask Anyy to continue from an offset or narrow the search instead of assuming truncated output is complete.
Terminal Tools
The terminal can run a foreground shell command or start a managed background process. Managed processes support lifecycle actions such as list, poll, log, wait, write/submit input, close input, and kill.
Example requests:
In this Workspace, find every reference to the old setting and show me the affected files. Do not edit anything.
Run the focused tests for this package. If they pass, propose the two-file change but wait for approval before writing.
Approval Behavior
Reads and searches are normally direct. File mutations and commands are classified by effect. In approval mode, sensitive changes can create a ChangePlan that you must review before execution.
The plan is bound to the proposed operation. If the command or mutation changes, Anyy must request authorization again.
Confirm the working directory, every affected path, the exact command, expected impact, validation, and rollback. Workspace is context and artifact storage—not a permission sandbox.
Safer Working Pattern
- Ask Anyy to inspect and explain the current state.
- Request a small, explicit change.
- Review the ChangePlan and diff.
- Run focused validation.
- Expand to broader checks only when needed.
Limits and Protected Reads
Anyy refuses unsafe virtual/device filesystem paths. Reads of protected or secret-bearing locations can require authorization. File mutations are constrained by the runtime's configured mutation scope and boundary checks, including path traversal and symlink handling.
Background Processes
Use a managed process for a server, watcher, or long-running test. Ask Anyy to report its process ID, poll or show logs, and stop it when the task ends. Starting or controlling a process can require approval because process input and signals may change external state.
One Profile can have at most four active managed process jobs. After a process finishes, its durable job status and summary remain, while raw diagnostic log files are retained for 24 hours and then released by an hourly cleanup pass. Copy a needed result into the Workspace or an Artifact before that diagnostic window ends.
See Approvals & ChangePlans for authorization details and Background Jobs for independent agent work.