Talo Guide
Automatic weekly report and reviewed
How to schedule a weekly summary of the project that generates on its own but never reaches your real folder without your approval.
You want to have a draft progress report every Monday without having to ask for it manually. Talo can do it, but with a rule it never breaks: what an automation writes stays in a copy until you decide to apply it.
Steps
- In a project conversation, ask the assistant something like "every Monday at 9 create
a progress report". The assistant creates the task with Talo's automations skill, but it's born paused: it's marked "Created by assistant · pending activation" and won't run on its own. The assistant itself can't activate it even if it tries.
- You'll see the "pending activation" notice in the sidebar (Automations), in Home, and on
the Settings main card. Go into the task detail and review what prompt it will use and how often.
- If everything looks good, tap "Activate". From then the task is active and leaves pending.
The schedule shows in plain text ("Every Monday at 09:00"), not as a cron expression.
- You can test it right now with "Run now" instead of waiting until Monday: you'll see a run
that finishes "Completed" with its cost in a few seconds (in Codex the cost might show "unknown", never 0).
- When the automation runs (scheduled, manual, or chained), its agent works on a copy of
the project, not on your real folder, and without auto-approve mode. If it tries to write outside that copy, it gets denied.
- If the run changed any files, the Executions panel marks it "Changes pending review", Home
warns you, and you get a notification. If nothing changed, the copy deletes itself and there's nothing to review.
- If you leave a review unresolved, it doesn't expire suddenly: Talo warns you when less
than 24 hours remain, and after 7 days with no decision, it marks it "Expired" and deletes the copy.
Review before applying is not optional
Changes from an automation never reach your real project on their own. You have to open "Review changes", look at the diff for each file (or the preview if it's a document) and tap "Apply" or "Apply all" yourself. If you edited that file by hand meanwhile, Talo marks it "Conflict" and won't overwrite it: only "Overwrite", with confirmation, replaces your version. If you'd rather not keep that result, tap "Discard" and the copy vanishes without touching anything.
Note
Only Claude Code and Codex can run automations in this beta. If you chain this task with another, the next one doesn't start until you apply or discard the pending changes from the previous one. All the detail on schedules, conditions, and triggers is in Automations.