AI agents that do recurring work on time, on your computer
Tell The One's main assistant what should recur, such as “every morning at 9, check yesterday's orders”, and it sets up a trigger. Triggers fire on a time or a cron line, when a folder, a web page, a command or a Plugin (orders, refunds, mail) has something new, or when another service sends a webhook. Each fire goes to the matter's working group, which keeps what it learned. The One keeps running after you close the window, and finished work waits for you in one place.
What you can hand over
- “Every morning at 9, check yesterday's orders.”
- “Confirm each new order by email.”
- “When a new file lands in the Invoices folder, file it and add it to the spreadsheet.”
- “Every Friday, read this week's sign-ups and write a short summary.”
What can start the work
| Fires when | Example |
|---|---|
| A time comes: daily, weekly, every so often, a cron line, once | Every weekday at 08:30 |
| A Plugin has something new | A new order or refund (Payments), new mail (Mailbox) |
| Files in a folder change | A new invoice in a folder |
| A web page changes | A competitor's pricing page; only the lines that match a pattern |
| A command's output changes | A script that prints new log errors |
| A webhook comes in | A Stripe, Creem, GitHub or Shopify event; signatures checked, a resent event fires once |
| By hand | Fire now |
How it runs
- On a matter's board. A recurring piece of work gets a Cadence card: when it fires, where the work goes, the next and the last fire, Fire now, Pause.
- In the background. The One keeps running without a window, can open at login, and can keep the computer awake on mains power while triggers wait. A fire missed while the computer slept runs once on return, or is skipped, as you choose.
- What comes back. The finished work waits in Waiting for you; questions and failures always notify you. Ask for a notification when work is done, or leave it off for frequent work like each order.
- Outside text stays data. What a source brings, an email or a webhook body, reaches the Agent marked as outside data, so an email that says “ignore your instructions” is just part of an email.
Before mail and money go out
Everything a fire starts is recorded, and file changes can be undone. Emails sent and payments made cannot be taken back; the Mailbox and Payments Plugins rehearse locally first (sending reaches nobody, no money moves), and Payments runs in the provider's test mode before going live.
Where it stops
- Webhooks are not received while the app is closed, and triggers fire only in the active Space.
- There is no cloud runner: when your computer is off, the work waits.
- Mailbox does not support Outlook or Microsoft 365 yet.
Questions
- Do I have to write cron?
- No. Say it in words and the main assistant sets it up; the form takes “every day at 09:00” too. Cron is there if you want it.
- Can Agents make their own triggers?
- Yes. An Agent can set itself a time to come back and look; the settings page marks those Made by an Agent, and you can pause or delete them.
- Does it run while my Mac sleeps?
- No. With mains power it can keep the computer from sleeping on its own while triggers wait; closing a laptop's lid still puts it to sleep.
In the docs