> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noclick.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Your coordinator
> One assistant that sees your whole NoClick account, keeps an eye on failed runs, and remembers how you like to work.
An [AI agent](/agents/overview) lives inside one workflow. The coordinator sees the account: every workflow, every run, every connected account. You talk to it about your work rather than about a canvas, and it does what it can on your behalf.
It is on for every account. You reach it by message rather than on a canvas: see [Reaching you](#reaching-you) for the channels it works on. What it has learned lives in the **Memories** card on your [Dashboard](/getting-started/dashboard).
## What it can do
| It can | How |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tell you what is in the account | It reads your workflows, their runs, and what needs you, the same picture the [Dashboard](/getting-started/dashboard) shows. |
| Build and change workflows | It hands the request to the [AI builder](/builder/overview) and follows it up. Where the builder needs an answer or a connection, you get a link. |
| Give work to an agent you already have | It finds a suitable agent, sends it the task, and brings the reply back. A queued task is not a finished one, so it tells you the reply will follow. |
| Connect an account | It sends you a link to connect the service, without building a workflow first. |
| Trash and restore a workflow | It asks first. A trashed workflow can be restored for 30 days. |
| Search the web | Through [Exa](/integrations/exa), returning the sources it used. |
| Make images and video | Video generation is available on the Plus and Pro plans. |
Everything it does is billed to your account in credits, like any other AI usage. See [What costs credits](/billing/costs).
## Failed runs
When a workflow fails, the coordinator looks into it rather than waiting for you to notice.
Usually by asking the builder to diagnose the workflow, sometimes by reading the run itself.
A workflow that is clearly finished with, such as an abandoned test or a duplicate, is paused with the reason recorded. A broken one that can be fixed goes back to the builder.
A failure that keeps repeating, or one only you can fix because it needs a credential or a decision, reaches you. Everything else stays a note in the conversation.
A workflow the coordinator paused is resumed by the coordinator too, and only the triggers it switched off are switched back on. Triggers you disabled yourself stay that way.
| Limit | Value |
| ------------------------ | ------------------------------------------------------- |
| Failures folded into one | One workflow's failures inside 6 hours |
| Failure wake-ups per day | 6 per account. The rest are recorded without waking it. |
| Messages from one agent | 3 per agent a day, 10 across the account |
A run that failed for want of credits never wakes the coordinator. The [credits alert](/billing/notifications) covers that on its own.
To stop this, tell the coordinator, either for one workflow or altogether. It keeps that as a memory and honors it. There is no switch to find.
## Memories
**Memories** is a card on the Dashboard. It holds what the coordinator has learned about you and your work, and you can read, edit, and delete every entry, or write your own.
Each memory has a name, a line under **When this is useful** saying when the coordinator should recall it, and the memory itself. Entries are filed under **About you**, **Preferences**, **Project context**, or **Reference**, and each says whether it came **From a conversation** or was **Added by you**.
Preferences belong here rather than in a settings page. How you like to be reached, which workflows to leave alone, what your project is for: tell the coordinator once and it writes it down.
Memories are private to your account and survive resetting the conversation.
A memory is context, not a rule. Telling the coordinator to check with you before it sends anything does not stop it from sending. To stop an action, lock it on the connection's [tool permissions](/credentials/permissions) page.
## Reaching you
The coordinator reaches you on the channel you last wrote to it on, unless a memory says otherwise.
* **WhatsApp**, on a number [linked to your account](/getting-started/phone). A message from that number starts a conversation with the coordinator, and it can reply there.
* **Email.** The coordinator has its own inbound address on `noclick.app`. Ask it for the address, or ask it to take a readable name, then write to it and it answers on the same thread. Mail is acted on only when it comes from the email address you sign in with and passes the sending checks.
Where neither can reach you, the message is left in the conversation rather than sent somewhere you did not ask for. A channel that cannot deliver says so rather than silently trying another.
## Next steps
What needs you, what ran, and what is coming up.
Link the numbers you reach NoClick from.