Overview
RunTools is used to build AI-powered applications across many domains. Here are common patterns showing what you can build today.Code Assistant Agent
Build an agent that can write, debug, and refactor code inside a sandbox.agents/code-assistant.ts
GitHub PR Review Bot
An agent that reviews pull requests using the GitHub marketplace tool.agents/pr-reviewer.ts
github tool is installed from the marketplace and configured with your GitHub PAT via the Credentials page.
AI Email Assistant
Process emails using the Gmail marketplace tool.agents/email-assistant.ts
Custom Tool + Agent
Build a custom tool that queries your database, then use it in an agent.tools/customer-db.ts
agents/support-agent.ts
Desktop Environment for Computer Use
Create a desktop sandbox with full GUI for browser automation or computer-use agents.xdotool, scrot, and imagemagick for computer-use agents.
SDK: Programmatic Sandbox Management
Use the SDK to manage sandboxes from your application code.Secrets Management
Store API keys and credentials securely for your tools and agents.Best Practices
Use the right template for your use case
Use the right template for your use case
Use
base-ubuntu for CLI/headless tasks, desktop-ubuntu when you need a browser or GUI.Pause sandboxes when not in use
Pause sandboxes when not in use
Paused sandboxes have zero compute cost. Resume takes under a second. Auto-pause kicks in after 10 minutes of inactivity.
Store credentials as secrets, not in code
Store credentials as secrets, not in code
Use
runtools secret set or the Credentials page to store API keys. Never hardcode credentials in agent definitions.Use core tools for filesystem access
Use core tools for filesystem access
Every agent gets
bash, read_file, edit_file, etc. These are powerful — agents can install packages, run tests, and modify code.Build custom tools for external integrations
Build custom tools for external integrations
If the marketplace doesn’t have what you need, write a custom tool with
defineTool() and deploy it to your org.