Saved setup
Saved once, replayed every run
A task keeps its own brief, project, files, model, effort, and machine size. Every run starts from the same setup, so the sixth result is comparable to the first instead of a fresh interpretation.
Marketing work that keeps running.
Put research, reporting, and content batches on a repeating cadence. A scheduled task runs on time without a nudge — hourly, daily, weekly, or monthly — and every result lands back in your project, ready to review and publish.
The things you always mean to do, actually done.
Every team has work that should happen regularly and quietly doesn't. Hand it to Ampere once, and it just keeps happening — finished work waiting for you, not another reminder to do it yourself.
Saved taskActive
Monday competitor sweep
What your competitors changed in the last seven days across their sites, pricing, content, and public ads — with before-and-after evidence bound to every claim and a suggested response you can accept or ignore.
- Cadence
- Weekly · Mondays 09:00 · America/Los_Angeles
- Project
- Competitive watch
Scope
- Up to 8 competitors
- Up to 5 dimensions
- 7-day window
Deliverable
- Scope and window
- Material changes
- Unchanged or unresolved
- Evidence
- Implications
- Suggested responses
It also tells you what didn't move, which is why you can trust the quiet weeks.
The same sections every run — which is what makes the fifth run comparable to the first.
Watch one chat become a standing job.
A competitor brief, asked for once in plain English. One follow-up turns it into a scheduled task. The next Monday it runs on its own — and the report opens with what changed since the last one.
A scripted replay of a real Joule run. Playback is compressed; the first brief took about nine minutes and the unattended run about six.
A schedule you can actually trust.
Unattended work is only worth having if you can tell what happened. Every run leaves a record, lands where you'll find it, and stops itself when something's wrong.
Where it lands
Results land in the project
Each run opens its own chat inside the project you bound the task to, and files its outputs there. Nothing to go hunting for, and the recurring work sits next to the rest of that project's work.
Run history
Run history in plain language
Every run has a record: when it ran, whether it succeeded, partly succeeded, or failed, what it produced, and what it cost.
Team updates
The team gets the result, not the chore
Add workspace members to a task and they can be emailed when a run finishes, with a link straight to the run. They see the run, not your private chat or project.
Safety
It stops itself when something's wrong
Runs check and reserve credits before they start, so an empty balance pauses the task instead of failing on repeat. Keep failing and it pauses itself and tells you — after five failures in a row by default, and you choose that number.
Unattended runs
It never waits on you
Joule asks what it needs while you're setting the task up. After that it stops asking — a run does the work with what it has, notes anything it couldn't reach, and finishes. You'll never find it stalled halfway, waiting on an answer.
Questions, answered
What a scheduled task is, what it will and won't do on its own, and where it stops to ask.
A saved brief with a cadence. You describe the work once and saves it with a name, the project it belongs to, a timezone, its run settings, and any files it needs. From then on it runs on the schedule you set. You can run it now, pause it, edit it, duplicate it, or delete it whenever you like, from the dashboard or by asking Joule in chat.
Put the first one on a schedule.
Start with the job you keep meaning to do every week. Brief it once, accept the cadence, and let it run.
- Research
- Content
- Creative
- Monitoring
- Reports