Getting started
Create your organization, draft a routine, prove it with one manual run, and activate its schedule.
This walkthrough takes about fifteen minutes and ends with one routine running on a schedule you trust.
Create an account
Sign up at workonrepeat.com/sign-up. Work on Repeat creates a personal
organization containing one project named Default project. Nothing else is
created implicitly.
Routines, runs, connections, and API keys all belong to a project, and projects belong to an organization — the same shape LLMGateway uses. Read Organizations and projects if you plan to separate clients or environments now rather than later.
Draft the routine
Open Routines → New routine. Start from a template or begin blank. The setup flow asks for five things:
Prop
Type
Write instructions that describe what stays the same every week, and move the
values that change into variables such as
{{repository}} or {{reportingWindow}}.
The timezone picker lists every IANA zone your browser knows, grouped by region and labelled with its current UTC offset, and defaults to your own.
Schedules start paused
A new routine is created in draft. It is never eligible for scheduled
execution until you have proved it, which keeps an untested responsibility
from running unattended.
Add tools, if the work needs them
Skip this step if the routine only needs the model.
Otherwise open Connections and connect GitHub or PostHog with OAuth, paste a Zernio API key, or add your own MCP server. Then, from the routine, choose the connection and select Discover tools.
Every discovered tool arrives disabled. Enable only what the work requires, and grant automatic execution separately and deliberately — see Tool permissions.
Run it once, by hand
Select Run now. The run is queued, claimed by a worker, and executed against your configured limits.
Open the run and read the trace before you trust it:
- the final result;
- each model step and tool call, in sequence;
- inputs and outputs that are safe to retain, with secrets redacted;
- duration and token usage per step; and
- webhook delivery state, when a webhook URL is configured.
If it fails, Troubleshooting maps every error category to a cause.
Activate the schedule
Once a manual run of the current configuration has succeeded, Activate
schedule becomes available. Activating computes the next occurrence in the
routine's timezone and sets the status to active.
From then on the operations tick claims the routine when it is due, executes
it, and records the run exactly like a manual one — only the trigger differs.
What to do next
Understand the activation rule
Which edits send a routine back to draft, and why that is the point.
Get told when it finishes
Signed run.succeeded and run.failed events, delivered with retries.
Write better instructions
The difference between a prompt and a standing responsibility.
Drive it from code
Project-scoped API keys, least-privilege scopes, and the /v1 surface.