Tasks

Most to-do apps are a list your software can't read. In Unyo, a task lives in your Neural Core — the shared memory all ten agents read — so "what's left?" is a question you can ask anyone on the team. And a task with a due date doesn't just sit there waiting to nag you: an agent can pick it up and start the work before the deadline.

What a task is

A task is a small, one-shot piece of work: a title, optional notes, a priority, and an optional due date and time. It is not a calendar event and not an automation — automations recur, tasks happen once and then they're done.

Every task has:

Your tasks are yours alone: the table is protected by row-level security on every read and write, so no other account can see or touch them, and they're purged with the rest of your data if you delete your account.

Three ways to add a task

1. From the sidebar

1. Open the Tasks section in the left sidebar (it's on every page except when you're inside an agent).
2. If your list is empty, click the add prompt; otherwise click the count badge to open the full list in the Neural Core.
3. Type a title, pick a priority, and turn on Date — and Time if the hour matters.
4. Save. It appears in the sidebar immediately.

2. From the Neural Core

1. Open your Neural Core from the sidebar.
2. Open Tasks.
3. Add, edit or delete anything from there — hover a row for the edit and delete controls.

3. By asking any agent

This is the fastest one. Any of the ten agents can drop a task into your Neural Core mid-conversation — you don't have to stop what you're doing and go find a form.

Priority and due dates

Priority does three things: it colours the dot in your sidebar (red for high, orange for medium, green for low), it sorts your list, and — if the task gets an agent — it decides how early the work starts. Your pending list is always sorted by priority first, then by due date, with dated tasks ahead of undated ones.

Due dates are handled in your timezone, not the server's. A task with a date but no time is treated as due at 09:00 your local time, not at UTC midnight — and the conversion from wall-clock to real time is DST-safe, so a task you set for 9am in March is still 9am in November.

If you don't need a deadline, don't set one. An undated task won't be scheduled against a clock — though if it's clearly work an agent can do, an agent may still pick it up shortly after you add it. To keep a task purely as a note, complete or delete it, or keep it a human task.

Ticking things off

Click the checkbox in the sidebar — that's it. The row fades out, you get a confirmation toast, and you never had to open anything.

• Ticking a completed task again reopens it.
• Everything you finished in the last 30 days stays available under the collapsible completed section, so you can go back and check what you actually shipped last month.
• Completing (or deleting) a task with a scheduled run cancels that run automatically, at the database level. There are no orphan runs — a task you finished early will never fire.

Your sidebar shows your top 10 pending tasks; the count badge caps at 10+. The full list lives in the Neural Core.

Every agent sees your pending tasks

This is the part that makes it worth putting your to-dos in Unyo at all. Up to 10 pending tasks — title, priority, due date, and who they're assigned to — are injected into every agent's context at the start of every session. Not Maya's. Not just the one you told. All of them.

Ask that of Ashley, Blake, Ema or anyone else and you get the same answer, because they're reading the same list. Agents can add tasks and tick them off when the work is genuinely done — so when an agent finishes a job you gave it, the task closes itself.

Tasks that run themselves

Give a task a due date and leave it unassigned, and Unyo will try to find the right agent for it. If it finds one, the agent starts ahead of the deadline so the result is ready by the due time, not after it:

When the work is ready, you get a red badge on that agent's avatar and a chime. The conversation is named after your task — not a truncated goal string — so you can find it later. Open it and you'll see the whole run: the steps, the tools, and whatever the agent produced.

The agent is told to do the work now, and to call it done only when it's actually done. If part of the job can't be finished without you, it prepares everything it can as drafts and tells you what's left.

What never gets handed to an agent

When you leave a task unassigned, a small router model reads the title and picks a specialist — in any language you wrote it in. "Write the newsletter for Friday" gets Lucy. "Call the dentist" gets nobody, on purpose: the router is explicitly forbidden from assigning physical or human tasks — calls, meetings, errands, appointments, chores — and from guessing on ambiguous personal reminders.

And it's fail-safe by construction. Every way the router can fail — no answer, an error, an unrecognised reply — resolves to no agent. The design rule behind it is blunt: never a wrong autonomous run. The worst case is that your task stays an ordinary task in your list.

Assigning a task to a specific agent

If you already know who should do it, say so:

Agents can also hand work to each other. When one agent delegates to a teammate, it writes a real assigned task into your Neural Core — a record you can see, edit and delete — and the teammate finds it flagged as theirs in their next session and offers to run it. Delegation is a row in your task list, not a promise in a chat bubble.

What it costs

Task management is free. Creating, listing, updating, completing and deleting tasks are all zero credits — that's a database value, not a promise. There's no charge for keeping your list in Unyo.

You only pay when an agent actually does the work: the run is billed on its real cost, at See credits and billing.

If you run out of credits, a scheduled task run is skipped cleanly — it doesn't count as a failure and nothing gets disabled.

Reliability details worth knowing

• Editing a task re-arms its run — it doesn't duplicate it. Each task has exactly one scheduled run, keyed uniquely to the task. Change the date five times and you still have one run.
• Stale tasks never stampede. A task whose due moment is already more than 24 hours in the past will never auto-fire. Come back after a week offline and nothing detonates.
• The run re-checks before firing. If you completed the task in the meantime, the run stops.
• Times are yours. Deadlines are computed and reported in your timezone, from your settings.

FAQ

Troubleshooting

My task didn't run. Check two things: is it still pending, and is it something software can do? "Call the plumber" is deliberately never assigned. If it's a legitimate work task with a deadline and nothing happened, reopen the task form and re-save the date — that re-arms the run.

It ran, but the result isn't what I wanted. Open the conversation named after your task. The full run is there — every step and every tool call. Reply in that conversation to correct it; you don't need to start over.

The task shows the wrong time. Deadlines follow the timezone in your settings. Check it there first — if it's wrong, every deadline shifts with it.

Some labels in the task panel appear in French. Cosmetic only, and being fixed. Your data and your agents are unaffected.

Next: Automations · The Neural Core · How agents work