“Why does the AI only work when someone types?”
Every run needs a person at a keyboard and a chat left open. When they log off, the work stops.
Unattended runs are ConvOps workflows that start on a schedule, without anyone typing. Every run is on the record. People keep the checkpoints they placed and the stop button.
schedules · one pod per run · tokens and cost per run · gates still hold
Give the workflow a schedule. Each run starts on its own, works in its own pod, and the work lands on a review branch, or any branch you choose.
ConvOps is the operations layer for AI agents. It holds your team's process as workflows with gates, a shared memory, scheduled and unattended runs, programs, a plan board, metrics and a full audit trail. It does not sell or host models.
key facts · october 2026
best for
not for
updated
AI that only runs while someone types is a tool, not a team. And what runs unwatched is rarely on any record.
“Why does the AI only work when someone types?”
Every run needs a person at a keyboard and a chat left open. When they log off, the work stops.
“What ran last night?”
A script fired on someone's machine. Whether it finished, failed or never started, nobody can say.
“What did it cost?”
Tokens disappear into one monthly bill. No run, no model and no task carries its own number.
Example: one nightly bug sweep, start to finish. Nobody typed a word until the review.
The bug sweep has a rule: every weekday at 01:00 in Europe/Berlin. Nobody is awake. The schedule creates the task and starts the run.
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
One pod for this run: the agent, its tools beside it, a volume for the task and a secret for this run only. It works the workflow step by step.
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
Halfway through the sweep, the machine under the run is lost. The run ends as a failure. Nothing is thrown away: the volume holds every file it touched.
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
ConvOps starts a new run on the same volume, on its own, and it carries on. The record links it to the run it continued, so the night reads as one story.
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
The fixes go to a branch named for the task, ready for review; the environment could name any branch you choose instead. Had the push been refused, the work would sit on a rescue branch.
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
Two runs, the tokens, the cost per model, the duration. The workflow waits at the review gate until an explicit approval is given. You read the branch and give it, recorded with your account.
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
weekdays at 01:00 · Europe/Berlin · next five runs shown before savingThe run ends as a failure. The task volume, and every file on it, stays. Three failures in a row and the task waits for you.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
None of them needs a person at a keyboard. All of them land on the same record.
A recurrence rule on the task, such as every weekday at 01:00 in Europe/Berlin, in its own time zone. You can also fire it by hand.
rule-based
A run can dispatch the next task it finds, within a per-run limit, so one night's work can lead to the next.
bounded
A run that fails starts again on its own, on the same volume, and carries on from where it stopped.
same volume
Your own product creates scheduled work through the SDK, when your customers or your data call for it.
through the SDK
Daily, weekdays, weekly, monthly or a custom rule, each schedule in its own time zone. See the next five runs before you save, and fire it by hand.
The Executions overview shows run status, runs per day, runs by executor and by backend, and spend. Every run keeps its tokens, cost per model and duration.
Finished, stopped by a person, resumed after a failure, or failed with the work kept. Each one is recorded.
where the work lands
A failed, stopped or timed-out run can be retried by hand. Resume carries on with the working copy it left; Start fresh begins clean.
Failed. The working copy stays.
Retried with Resume. Finished.
Give an environment full git access and the agent pushes as it goes, fast-forward only. Work lands on a review branch, or any branch you choose.
A run can dispatch follow-up tasks it finds, in its own workspace, when its environment allows it. Each run has a limit, so one night cannot run away.
Three invoice exceptions found. Dispatch one task for each.
A schedule starts the work, it does not approve it. A checkpoint you placed still holds: an approval, a required metric or a report. Any run can be stopped.
Bug sweep 2026-10-02
step 5 of 6 · review
convops/task/8c1e
example · the gate holds the step until an explicit approval is given, recorded with the account that gave it
checkpoints you choose
Add checkpoints where a person, a metric or a report should decide. Leave them out where the work can run by itself.
Attended or on its ownAn RFC 5545 rule, or a cadence in plain words, on a scheduled task. Hours are read in the schedule's own IANA time zone and stay local across daylight saving. Each fire creates a child task that inherits the title, project and executor, then runs it.
{
"tool": "schedule_create",
"arguments": {
"title": "Bug sweep {date}",
"vertical": "development",
"project": "checkout",
"rrule": "FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR;BYHOUR=1;BYMINUTE=0",
"timezone": "Europe/Berlin",
"executor": "claude-opus",
"description": "Pick open bugs, fix, test, push the task branch."
}
}Each run keeps its trigger, outcome, error class and stats: tokens in total and per model, turns, duration and cost, with where the cost came from.
{
"id": "run_4f2a",
"executor_name": "claude-opus",
"agent": "claude-code",
"trigger": "auto_resume",
"resume_of": "run_9b71",
"status": "ended",
"outcome": "succeeded",
"stats": {
"tokens": 71000,
"tokens_by_model": {
"opus": { "tokens": 64200, "cost_usd": 0.79 },
"haiku": { "tokens": 6800, "cost_usd": 0.03 }
},
"turns": 38,
"duration_ms": 1330000,
"cost_usd": 0.82,
"cost_source": "computed"
}
}The first run of the night ended when its node was lost. Its outcome and error class show it, and the resume above points back to it.
{
"id": "run_9b71",
"trigger": "dispatch",
"status": "ended",
"outcome": "infra_failure",
"error_class": "node_lost",
"stats": {
"tokens": 341000,
"tokens_by_model": { "opus": { "tokens": 341000, "cost_usd": 4.36 } },
"turns": 214,
"duration_ms": 7740000,
"cost_usd": 4.36,
"cost_source": "reported"
}
}The time limit is set per executor, four hours by default. A run that reaches it ends as time_limit and is retried by hand. A run may dispatch follow-up tasks, within a per-run limit, and any run can be stopped.
{
"name": "claude-opus",
"backend": "isolated",
"isolated": {
"agent": "claude-code",
"model": "opus",
"time_limit_s": 14400
}
}An unattended run is a ConvOps workflow run that starts with nobody typing: on a schedule, as a follow-up from another run, as an automatic resume or from your own app. Each run gets its own isolated pod, records its tokens and cost, and stops at the checkpoints you placed. Example: a supplier invoice match runs every weekday at 03:00 in Europe/Berlin.
Four things in ConvOps. A schedule, such as every weekday at 01:00 in Europe/Berlin or the 15th of every month. A run dispatching a follow-up task, within a per-run limit. An automatic resume after a failed run. And your own app, creating scheduled work through the SDK. You can also trigger any schedule by hand, which does not move its next fire.
In ConvOps a run that fails, say the model errors or the node under it is lost, resumes on its own on the same volume, and the record links the two runs. After three failed runs in a row the task stops and waits for a person. A run that reaches its time limit, four hours by default, stops and keeps its files: retry it with Resume and it carries on.
ConvOps pushes to a task branch for review by default, or to any branch you choose in the environment, where the work lands only when the run succeeded with a clean tree. When a push cannot land, the work goes to a rescue branch, so nothing the run did is lost. Reports, drafts and data files land the same way as code.
Only if your ConvOps workflow lets it. The checkpoints in the workflow hold whether a person or a schedule started the run: an approval gate holds the step until an explicit approval is given, recorded with the account that gave it. Add checkpoints where a person, a metric or a report should decide. Leave them out where the work can run by itself.
ConvOps records every run with its tokens, a per-model split, cost, turns, duration and, when it fails, an error class. Cost is either reported by the agent or computed from tokens, and the record says which. Example: a compliance team compares what each nightly sanctions check costs on two model tiers.
Yes. Any running ConvOps run can be stopped from the runs view or through the API. The record keeps it as stopped, with what it used up to that point, and a person can retry it later with Resume or Start fresh.
No laptop. ConvOps runs execute in isolated pods, one per run, on our cloud or on your own Kubernetes cluster. Enterprise customers can self-host from one Helm chart delivered with Enterprise, so nothing has to leave the cluster. Example: a hospital group keeps its nightly claims check inside its own cluster.