Agents & automations

An agent is a configuration - a model, instructions, a set of tools it's allowed to use, and (if you want) a budget and a schedule. Every built-in and installed app is available to an agent as a tool, so an agent can genuinely act on your files, your calendar, your notes, and anything else on your desktop, not just talk about them.

The assistant

The assistant is the easiest way to reach everything else in the system. Type a sentence into the strip and a conversation opens above it: ask a question, ask it to find or summarize something, or ask it to create an agent or an automation for you. It can surface apps, files, agents and automations as cards you can act on directly.

Agents

Set up an agent with a model, a system prompt, and the tools it needs. Give it a name and it becomes something you can talk to directly (in Messages) or hand a one-off task to from the strip with @. Every run is recorded with what it cost and what it did, and can be reverted if you don't like the result.

Automations

An automation is a rule: something happens (a schedule, an event on your desktop, opening an app, or a manual trigger), and something follows (a notification, opening something, or running an agent). Automations can chain into multi-step pipelines, where a later step uses an earlier step's output.

Tool permissions

Agents act through tools with your approval built in: anything that changes something asks first, unless you've told it not to for that kind of action. Your own provider keys never leave your browser unless you explicitly opt them into the encrypted vault used for runs that continue in the background.

What's next

• Let automations keep running without a tab open.
• Understand what "speculation" does to cost before you turn it up.