A LOCAL PLUGIN FOR CLAUDE CODE & CODEX
Teach it once.
Run every row.
Remember.
Stop copying a spreadsheet into the same forms.
Your agent learns one example. Ritoko repeats the saved steps for each new row, checks the result and remembers where to resume.
Free · Open source · MIT license
Have a workflow to automate? Tell us about itThree rows.
Three new customers.
customer
onboarding
Your agent finds the fields once.
Automatic illustration · CSV → customer records · sample data
0Model calls by the direct runner
to replay saved steps
100%RPA Challenge
70 of 70 fields
Resume.Keep completed work.
Hold uncertain submissions.
THE WORK IT TAKES OFF YOUR HANDS
Same clicks.
New data.
A useful routine.
Use Ritoko when you already know what a successful task looks like, and need to repeat it across a list.
Create customers from a CSV.
Teach one form. Fill the next records from your spreadsheet and check that each customer exists.
customers.csv → checked customer records 02 / REPORTINGCollect the monthly exports.
Save how to choose an account and a period. Run that routine again for the next month’s list.
accounts + month → named report files 03 / ADMINISTRATIVE WORKUpdate a list of records.
Combine a browser and a verified API. Check the changes; hold an uncertain write for review.
records + changes → checked results01 / THE PROCESS
One example taught.
A whole list handled.
Follow a customer onboarding task from the first example to an interrupted batch.
The demonstration starts by itself. Choose any step to look more closely.
One example customer shows your agent how the task works.
Interactive illustration. Sample data; no live submissions.
A new customer.
THE ENGINE, ON CAMERA
See a real run.
Even when it stops.
This is Ritoko running against a local test back office. The process is killed after the fifth submission, then resumed. It finishes the remaining customers without resubmitting the verified ones.
10 unique submissions. 9 verified, 1 held for review.
A deliberate 700 ms delay per submit makes the interruption visible.
02 / THE WORK, IN VIEW
Slow enough to follow.
Fast enough to matter.
01 / BROWSER · MEASURED RUN
Seventy fields.
One saved procedure.
The RPA Challenge shuffles its fields after every submission. Ritoko’s replay completed all ten rows at 100%.
03 / LASTING MEMORY
A crash stops the run.
Not its memory.
Every item has an outcome. On resume, the journal decides what can run and what needs a human check.
Watch the real crash & resumeThe journal covers actions executed through this Ritoko installation. Each workflow supplies checks that prove its business result.
Resume from the journal, not from zero.
SHORT ANSWERS TO REAL PROBLEMS
Problems we are
built for.
Did my browser submission succeed before the automation crashed?
A timeout or crash does not prove that the submission failed. Check the destination for that exact business record before retrying. Ritoko holds a write interrupted after its commit boundary for review and resumes other eligible rows from its journal.
How do I avoid duplicate records when I import the same CSV again?
Identify each operation with a stable business key and destination scope, adopt any row already submitted during recording, and verify each result. Ritoko normally skips confirmed keys and holds uncertain writes, but its local journal does not guarantee that duplicates are impossible.
Do I need an AI model to solve the same browser task on every run?
A stable task with explicit actions and checks can run as a saved procedure. Ritoko’s direct replay engine does not call an LLM. Recording, repair, host orchestration and external tools that use models can still consume model usage or incur charges.
How do I keep a recorded browser workflow useful when the page changes?
Record targets that identify the intended control by meaning and uniqueness, then verify the business result. Ritoko supports selector fallbacks and pauses eligible direct runs for deliberate repair. A changed submit target needs explicit confirmation before repair.
How can I process a CSV or Excel file and resume halfway through?
Define one verifiable operation per row, validate the input and keep a durable record of each outcome. Ritoko reads CSV and XLSX files, freezes the rows and workflow in its SQLite journal, and resumes the same run while keeping confirmed rows and holding uncertain writes.
Should a repeated task use the browser, an HTTP API or an MCP tool?
Use the supported interface whose business contract and permissions you can verify. Browser steps fit tasks exposed through a UI; HTTP steps fit documented endpoints; MCP steps reuse tools with known inputs and outputs. Ritoko can combine these paths under one workflow and journal.
READY WHEN YOU ARE
Your next task
could be the last first time.
Install the plugin. Ask your agent to record a task. Keep the procedure.
Read the setup guideclaude plugin marketplace add Swih/ritokoclaude plugin install ritoko@ritokocodex plugin marketplace add Swih/ritokocodex plugin add ritoko@ritokoRestart your client. Node 24+ required. Google Chrome for browser workflows.
“Record this task with Ritoko.”
FOR YOUR TEAM
Which routine
would you hand over?
Tell us what you repeat, which tools you use and what a successful result looks like. We can discuss whether the workflow is a fit for Ritoko.
Does every replay use AI?
The direct runner executes saved steps without calling a model. Recording, repair and host orchestration use your agent; connected MCP tools can also use AI. Reading each new document with an agent or OCR provider remains a separate step.
What happens if a submission is uncertain?
The item becomes review and is held across later runs. Check the result on the destination site, then resolve the item with an evidence note. Ritoko does not blindly submit it again.
Is this just a generated script?
A script can replay too. Ritoko adds a per-item journal, frozen input rows, business-key deduplication, result checks, interruption handling and a review state for uncertain commits.
Can I use browsers, APIs and tools together?
Yes. Workflows can combine browser, HTTP and MCP steps. Direct mode and host mode have different capabilities; the setup guide explains the supported paths and the host’s execution requirements.
Where does the data live?
The workflow, item journal and run files live locally. Destination sites and tools receive the actions you configure. Your agent’s provider receives what the agent sends while learning or repairing the procedure.
What if the page changes or asks me to log in?
A selector that stops matching pauses the run for repair. You complete login and MFA yourself in your authorized browser. Ritoko does not bypass CAPTCHAs or anti-bot protections.