Skip to main content
Five things people actually build on Runtools, end to end — copy one, swap the names, deploy. Each is a real config: a sandbox, an agent, sometimes a tool, and the commands to ship it.

Code assistant agent

Create a sandbox, define an agent, deploy, and run it.
sandboxes/dev-env.ts
agents/code-assistant.ts

GitHub PR Review Bot

Install the GitHub tool, connect GitHub, and add the tool slug to your agent.
agents/pr-reviewer.ts

Email Assistant

OAuth-backed tools can resolve connected accounts during hosted tool execution.
agents/email-assistant.ts

Custom Tool + Agent

tools/customer-db.ts
agents/support-agent.ts
Deploy the tool and agent, then store the tool credential:

Programmatic Sandbox Management

Best Practices

New projects created by runtools init use exec_command, write_stdin, apply_patch, view_image, web_search, and get_dev_url.
Prefer Connected Apps for OAuth-backed marketplace tools.
Use runtools tool credentials for installed API-key tools. Use runtools secret or rt.secrets for named secrets that your own code or direct tool calls reference.
Keep long-lived environments only when you need their state.