Guide
Give your agent
a camera.
Toru is recording infrastructure for your AI agent. Connect it once, pair the Chrome or Mac it records in, and ask for a demo in your own words. This page is the whole of it.
1. Connect your agent
In Claude Code, Claude, Cursor, Codex or any client that supports remote MCP servers, add a connector with the address https://mcp.toru.tools/mcp, then sign in to Toru and approve the connection. In Claude Code you can also install the Toru skill from alifoo/toru-skills. This connects your agent to Toru; it does not sign in to your product.
2. Choose where Toru records
Toru records in two places, both already signed in as you. It never asks for a password or a code, and a sign-in page stops the run instead of being recorded.
Web apps: your own Chrome
Install Toru for Chrome and pair it once from a link your agent gives you. Each recording opens your product in a window of its own, signed in with your session, with no click from you. Your cookies and storage never leave Chrome.
Mac apps: Toru for Mac
Install Toru for Mac with one line in Terminal, curl -fsSL https://toru.tools/install.sh | bash (or brew install --cask alifoo/toru/toru), pair it from a link your agent gives you, and choose the window or display to share. You approve what is shared, and you can stop sharing at any time.
3. Ask for a demo
Record a demo of creating an invoice in https://app.acme.com: open Invoices, click New invoice, choose Acme Inc. as the customer, save, and end on the invoice page.
Before recording, your agent writes a short plan of the flow: the screens, the exact buttons and fields, the values to use and what the last screen should show. If it can read your product’s code it uses that; otherwise it looks at the live product. The more specific your request, the better the demo. Ask for one flow per demo.
Then your agent records the flow itself, one click at a time, in a window Toru opens for it. When the last screen is on show it tells Toru it is done; Toru holds on that screen, stops, renders the video with your brand and checks it. Your agent spends a few tokens per step; Toru adds no model of its own.
Your brand
In the console, open Settings, add your product’s address and choose the background, padding, intro and outro cards, the camera’s zoom, the cursor, the GIF and the output size, then save. Every demo of that product uses them automatically.
Delivery check and credits
Every video is checked before delivery. Blank, frozen or too-short videos are held back as needing review and never charged; you can record again or accept the video anyway. One credit is used when a video is delivered. See pricing.
Your demos
Your agent hands you links to the MP4 and GIF. Every demo also stays in Demos for your plan’s storage period, with each step of the plan on the video’s timeline. Changed your brand? Render a demo again from there while its capture is kept; it uses no credit.
If something goes wrong
- Needs review: the video did not pass the check and no credit was used. Ask your agent to record again with a clearer flow.
- Stopped at a sign-in page: sign in to your product in that Chrome or app, then ask again.
- Chrome or Mac offline: open Chrome or the Toru app; a paired device reconnects by itself.
- Waiting for capacity: the beta records one demo at a time across all accounts. A run that finds Toru busy waits its turn, up to ten minutes, before recording; your agent can keep polling its status.
- Anything else: email support@toru.tools.
Run it yourself
Toru is open source under the MIT license: the recorder, Toru for Chrome, Toru for Mac and the console are at github.com/alifoo/toru. Run it on your own machines, with no model key to bring: your agent drives. The hosted service is the same code, run for you.
More
Pricing · Terms of Service · Privacy Policy · Plain-text summary for agents