Skip to main content
The model receives a fixed set of workspace tools, plus optional web research tools and any tools exposed by connected MCP servers. Every workspace tool call refreshes the workspace activity timestamp, which prevents an active session from being scaled to zero.

​
File tools

​
tool
Reads a text file, extracts text from a raster image with OCR, or converts a Word, PowerPoint, spreadsheet, OpenDocument, EPUB, RTF, or PDF file to Markdown. Paths default to /home/r5d.
​
tool
Creates or overwrites a file. Deliverables belong in /home/r5d/artifacts.
​
tool
Replaces one exact, unique block of text in an existing file. The match must be unique, which makes edits fail loudly rather than corrupting a file.
​
tool
Lists a directory in the workspace.

​
Search tools

​
tool
Exact regular-expression search through text and code files using ripgrep.
​
tool
Ranked full-text search across file contents, including Word, PowerPoint, Excel, PDF, and OpenDocument documents, powered by Recoll and Xapian.
grep finds exact strings; search finds relevant documents by meaning and reads inside binary document formats. Agents are instructed to use search when locating documents by topic.

​
Process tools

​
tool
Runs a shell command in the user’s isolated workspace. The default working directory is /home/r5d. Returns a process ID immediately, and takes an active lease so the workspace is not reaped while the command runs.
​
tool
Polls a shell process by ID for output and status. Releases the active lease once the process is no longer running.
​
tool
Cancels a running shell process and releases its lease.

​
Web research tools

These appear only when both AWR_BASE_URL and AWR_API_KEY are configured. See Web research.
​
tool
Searches the public web and returns concise result metadata.
​
tool
Renders one public URL and returns clean Markdown.
​
tool
Delegates a broad multi-source research task and returns cited progress and results. Requests may take up to 180 seconds.

​
MCP tools

Tools from connected MCP servers are merged into the same tool set. Their names and parameters are defined by the server. See MCP servers for trust and drift handling.

​
Agent conventions

The system prompt establishes a few rules that shape agent behavior:
  • Operate from /home/r5d by default.
  • Put user-facing deliverables in /home/r5d/artifacts.
  • Markdown links under ~/artifacts in user messages refer to real workspace files, so use readfile to inspect them before answering questions about their contents.
  • Use the bundled skills at /opt/r5dchat/skills when producing office documents.
  • When creating or editing a user-facing file, include a download link in the exact workspace form [filename](~/artifacts/filename). Paths such as file:, sandbox:, or /mnt/data are explicitly forbidden because the UI cannot resolve them.
The product name in the system prompt follows your branding, so the agent refers to itself by your product name.