Context References
Context references let you point Anyy at source material without copying it into the message by hand. Put a supported @ reference in normal prompt text; the resident runtime expands it before the model turn and records citation metadata with the run.
Supported references
| Syntax | Adds |
|---|---|
@file:PATH | A text file from the Profile Home, or an explicit absolute path that passes safety checks |
@file:PATH:START-END | A bounded line range from a text file |
@url:https://example.com/page | Readable text from a public HTTP(S) page |
@result:RESULT_ID | Stored evidence from a tool result in the current session |
@folder:PATH | A sorted listing of one folder in the active Workspace root |
@diff | Current unstaged Git diff |
@staged | Current staged Git diff |
@git:N | Patches for the latest N Git commits |
You can combine ordinary instructions and references:
Compare @file:workspace/proposal.md:10-80 with @url:https://example.com/policy and list conflicts.
Refer to files
Relative @file paths resolve from the selected Profile Home. The default Workspace is therefore normally referenced with a workspace/ prefix:
Summarize @file:workspace/notes/meeting.md
Use a line range when only one section matters:
Review the assumptions in @file:workspace/plan.md:24-67
Text files larger than the per-reference limit are refused unless a bounded line range fits. Binary files are not inserted as text; attach supported media through the chat surface instead.
Refer to a folder or Git state
@folder lists the immediate entries in a directory; it does not recursively insert every file. Folder and Git references are constrained to the active Workspace root supplied by the session.
Use @folder:reports to identify the newest report.
Review @diff for correctness and missing tests.
Compare the last three commits with @git:3.
@diff, @staged, and @git:N require a Git working tree. Anyy runs a bounded read-only Git command and refuses a reference when its changed-path preflight includes a protected sensitive path.
Refer to public pages and tool results
@url accepts public HTTP(S) destinations. Private/internal targets and unsupported schemes are blocked.
Extract the decision criteria from @url:https://example.com/guide
Use @result when a previous tool returned a logical result ID and you need its stored evidence again:
Re-check the failures in @result:tr_123 and propose the smallest fix.
Tool-result references are restricted to the current session. An ID from another session is treated as not found.
Limits and warnings
One prompt expands at most eight references. Defaults are 64 KiB per reference and 192 KiB total attached reference text; public page extraction is also bounded, and Git capture has its own finite limit.
When a reference is malformed, blocked, missing, too large, or beyond the count/total budget, Anyy attaches a warning instead of silently inventing its content. Fix the reference and send a new turn.
Referenced text may be untrusted. It does not override Anyy's system rules, your current request, approvals, or tool policy.
Security behavior
- Protected credential paths are refused and recognized secret material is sanitized.
- Path traversal and escaping the active Workspace root are blocked for folder and Git references.
- Symlinks are validated instead of being followed across a protected boundary.
- Binary file content is refused.
- URL fetching blocks private/internal destinations and non-HTTP(S) schemes.
These checks reduce accidental exposure but do not make arbitrary public content trustworthy. Read the cited source before authorizing actions derived from it.
Troubleshooting
| Warning | Fix |
|---|---|
malformed context reference | Check the colon syntax, line range, or positive Git count |
reference not found | Verify the path, result ID, Git repository, or URL |
reference blocked | Keep the reference inside the allowed root and away from credentials/private network targets |
reference too large | Select a file line range or fewer/smaller sources |
reference limit exceeded | Split the request into multiple turns with at most eight references each |
See Files & Terminal for tool-based file work and Session Search for finding earlier conversations.