Your to-do list, but it does the to-dos

Every task app is a better-looking place to feel bad. You write "draft the Friday newsletter", you set a reminder, and on Friday your phone buzzes to tell you the thing you already knew: it isn't done.

Unyo tasks work differently. Give a task a due date and Unyo picks the right agent for it and starts the work before the deadline — 60 minutes early for high priority, 30 for medium, 15 for low — so that when the deadline arrives, the draft is already waiting.

And when the task is something only a human can do? Unyo doesn't touch it. That's not a limitation we're apologising for. It's the reason you can trust the rest.

How a task runs itself

Four things happen, and only the first one is your job.

1. You write it down. In plain language, in the sidebar or in the Neural Core: title, notes, priority, an optional date and time. That's the whole form. (You can also dictate one to an agent — "note that I need to redo the pricing page by Friday" — and it lands in the same list, though a task created that way gets its agent when its moment arrives rather than ahead of time.)

2. Unyo picks the agent. A small routing model reads the title and notes and chooses the one agent that could genuinely do this with software — or chooses nobody. It works whatever language you wrote the task in. You can also name the agent yourself in conversation — "assign that one to Lucy" — and the routing steps aside.

3. The clock arms itself. A task with a due date and an agent schedules a real job in the background. Not a reminder — a run. The lead time is set by priority:

Set a date with no time and Unyo aims for 9:00 in your local morning, not midnight UTC — because "Friday" means Friday where you are.

4. The agent works, then tells you. It opens its own conversation — named after your task, so you can find it — does the work, ticks the task off when it's genuinely done, and puts a red badge on its avatar. You open it and find the draft.

The tasks Unyo refuses

Type "call the dentist" and Unyo assigns nobody.

Not because it failed. Because the router is explicitly instructed to refuse: physical and human tasks — call someone, attend a meeting, buy something, go somewhere, appointments, chores — get no agent. Ambiguous personal reminders get no agent. These tasks stay yours: they sit in your list with their priority dot and their date, and any agent can tell you they're pending when you ask what's left.

This is the part we'd like you to press on, because it's where the engineering is.

Every failure mode of the router lands in the same place: nobody. No API key, a network error, an exception, an answer it doesn't recognise — all of them return "no agent", and no agent means the task quietly stays a plain to-do. The comment in the source is the design goal in five words: never a wrong autonomous run.

Think about the alternative for a second. A router that fails open would guess. It would decide "call the dentist" is close enough to an email task and hand it to Maya, who would draft a message to a dentist you never named. The failure mode of over-eagerness isn't a missing feature — it's an agent doing something stupid on your behalf while you're asleep. So Unyo's routing is built to fail into inaction, every time.

Every agent knows what's on your plate

Your pending tasks aren't locked in a tasks app. They're part of your Neural Core — the memory all ten agents share — so up to ten of them, with priority, due date and who they're assigned to, are in front of every agent, in every conversation, automatically.

Which means you can ask anyone:

Ashley knows. Blake knows. Maya knows. Nobody has to be told twice, and you never have to remember which agent you told.

They can also act on it. Any of the nine non-Steve agents can create a task, list them, update one, tick one off, or delete one — in conversation, in your language, without a command syntax. (Steve reads your memory; he doesn't write to it.)

All of that is free. Every task tool in Unyo costs zero credits — create, list, update, complete, delete. Managing your work isn't a metered upsell. You pay only for the model tokens when an agent actually does the work, at real cost. See Pricing.

Where tasks live

Tasks are a section of your sidebar and a panel in your Neural Core — deliberately close at hand rather than a destination you have to visit.

• Your top 10 pending tasks, always visible, sorted by priority then by deadline, each with a coloured priority dot and a count badge.
• Tick one off without opening anything — the row fades out where it stands.
• Changed your mind? Tick it again to reopen it. Everything you finished in the last 30 days stays browsable.

The boring guarantees

This is the unglamorous half, and it's the half that decides whether you can leave the thing switched on.

Editing a task doesn't clone its run. Each task's scheduled run is keyed to that task and only that task. Reschedule it five times and you re-arm the same single run — you never end up with five agents doing the same job at once.

Completing or deleting a task cancels its run. Not "eventually", and not by a cleanup script that might miss one — a database trigger cancels the scheduled job the moment the task changes. There are no orphan runs waiting to fire for work you already did.

A stale deadline never stampedes. If a task's moment passed more than 24 hours ago, it never auto-fires. Come back from a week off and Unyo doesn't greet you by launching every missed task at once.

Your timezone is respected end to end. The form converts what you typed on the clock into real UTC — correctly, across daylight-saving boundaries. The dispatcher does no timezone maths at all; it just checks whether the moment has arrived. Every time an agent reports back, it reports in your local time.

Running low on credits pauses nothing. If a task run can't proceed because your balance is empty, Unyo skips it and moves on. It is not counted as a failure and it never auto-disables anything. You top up, and the next one runs.

Tasks vs. automations

Two different tools, and people mix them up.

A task is a deadline. An automation is a habit. Both end up doing the same honest thing: preparing the work and handing it to you.

What tasks are not

We'd rather you learn this here than after you've moved your life into it.

• This isn't a project manager. No boards, no subtasks, no dependencies, no assignees other than you and your agents. It's a list that can do its own work.
• The agent doesn't always finish. If parts of a task need you, it prepares everything it can as drafts and tells you plainly what's left.
• Personal tasks don't get a push notification. They stay in your list where you'll see them, with their date and priority — but Unyo will not buzz your phone about the dentist. If that's the job you need doing, keep your reminders app.
• An undated task waits. Autopilot arms on a deadline. No date, no clock, no run.
• Autopilot is young. It ships, it works, it has fired in production. It has not yet run ten thousand times. We'd rather tell you that than let you find out.

FAQ

Stop writing down work you'll do later

Give a task a deadline. Let it start without you.

Get started free — 2 500 credits, no card. Task management itself never costs a credit.