Swih/ritoko

Solve a task once. Save the procedure. Run it again with new data.
Ritoko is an open-source browser automation and robotic process automation (RPA) tool for AI agents. Turn a solved task into a reusable browser, HTTP API or MCP workflow, run CSV or Excel batches, verify results and resume interrupted work with a local SQLite journal.
Use it as a Claude Code or Codex plugin, a local Model Context Protocol (MCP) server, or a standalone CLI. The direct replay engine runs saved workflows without calling an LLM; a connected MCP tool may itself use AI.
Try locally · Quick start · Use cases · How it works · Workflow example · FAQ · Advanced guide
Watch the 34-second demo — real-time execution against a local test application. Kill the process after the fifth submission, resume, then rerun the same CSV: 10 submissions received, 10 unique, one row still awaiting confirmation. Recorded results and environment.
## Why use Ritoko?
An agent can figure out how to enter a customer, download a report or call a business tool. A recurring batch also needs an input format, a rule for identifying each record, a success check and a way to recover after interruption.
Ritoko keeps those decisions in a reusable procedure:
Reuse the work. Save parameters, selectors, API calls and verification rules in a readable JSON workflow.
Process new data. Feed the procedure another CSV or Excel file instead of explaining the same steps for every row.
Recover with evidence. See which items finished, failed or have an uncertain outcome. Confirmed items are skipped on later runs; uncertain writes are held for review.
With a configured destination lookup, Ritoko can also check before creating a record (ensure) and settle an uncertain result by reading it back (reconcile). These 0.2.0 features require a direct HTTP GET or a trusted, explicitly read-only MCP tool, with separate rules proving presence and absence. A failed lookup blocks the row. Configuration and limits.
For example: teach your agent to create one customer, save customer-import, then ask it to process next week's spreadsheet and report each result.
## What can you automate?
| Task | Input | What the workflow does |
| Customer or supplier onboarding | CSV / Excel rows | Fill forms, submit each record and check its identifying details |
| Recurring report downloads | Account and period parameters | Open the report, wait for it and save the downloaded file |
| Back-office data exports | An HTML or ARIA table | Extract the rendered table to CSV for a later batch |
| HTTP API operations | Rows, parameters and environment-backed credentials | Send requests, check status and JSON results, save response files |
| Existing MCP tools | Rows and tool arguments | Call tools and check their returned data under the same journal rules |
| Mixed browser and API tasks | A spreadsheet plus workflow parameters | Pass saved values and files between supported browser, HTTP and MCP steps |
Ritoko fits repeated tasks with explicit rules and verifiable outcomes. A new task still needs an agent or a workflow author to understand the site and define the procedure.
## Quick start
### Try ten fake customers locally