Daemons
Team up with your daemon

Meet Daemons, agents for work.

Work today means switching apps, rebuilding context, and turning what you want into the steps each tool expects. Stop being the human proxy. Your daemon does the steps and asks before any real change.

Team up with your daemonSee how it works
Touch the ribbon to meet your daemon

One task, end to end.

Follow a task from the request to the exact changes waiting for review.

Daemons
Clean up Q4 pipeline

Find the stale deals and prepare the changes.

I compared the call notes with the pipeline. Here is the update for Acme

⌄ Ready for review

  1. Searched
    Salesforce — AcmeGmail — pricing threadCall notes — October 28
  2. Reading the sources
  3. Comparing the pipeline stages
  4. Preparing the exact changes
  5. ✓ Changes are ready for your review
Waiting for youProposed change

Update the opportunity

Salesforce · Acme · Q4 expansion

FieldCurrentProposed
StageDiscoveryProposal
Close dateNov 6, 2026Nov 20, 2026
Next stepFollow upSend revised scope
Approve EditDecline

Nothing changes until you approve.

Applied to Salesforce · Approved by you

Ask Vigil about this task

Most work isn't hard. It's stuck.
Waiting on an app, a colleague, or one missing fact.

From ask to done.

Follow one task through the town. Every stage is built to keep the decision with you.

YouYour colleague

Update Acme's Q4 opportunity in Salesforce Done

Read the call notes Vigil Ready to read Gathering context
Confirm scope with your colleague CBuyer needs a revised scope by Nov 20Source: your colleague’s call notes, Oct 28 Review requestedYour colleague allowed sharingFact attachedSigned off by your colleague
Draft the change Y Edited by you
Your exact approval YouWaiting for youApproved by you

Next task handed to Vigil

How it works

  1. Hand over the task in plain words. Your daemon turns it into a plan and a small team of agents.

    Plain-words tasksEditable plan

  2. Helper agents take each step in the apps the task needs: your email, your calendar, your drive, and Salesforce.

    Helper agentsYour connected apps

  3. You and your colleague shape the same plan. Send a step to a colleague for review. Their daemon shares a fact from their device, with their permission and its source.

    Shared plansReview requestsCited facts

  4. Reading and drafting run on their own. A colleague signs off on their step inside the run. Anything that changes the outside world waits for exact approval.

    Colleague sign-offExact approval

  5. The work is prepared end to end. You review the Salesforce update and the Slack post together, approve both, and your daemon picks up the next task. Your time goes to the work that needs you.

    Signed recordSave as a routine

A day full of everything but the work.

Theo, Vigil, Tock, and Arca are agents your daemon hands work to.

25% of their time just searching for answers.

Leaders and teams in Atlassian’s survey.

Atlassian, State of Teams 2025

Theo finds the answer.

Research

Search the source documents and bring back a brief with citations.

275 times a day

Interruptions for the top 20% of Microsoft 365 users by ping volume, across a 24-hour day.

Microsoft, Work Trend Index 2025

Vigil gathers what needs you.

Your inbox

Prepare replies together so you can review them in one place.

55% of the workday is busywork

Share of the workday, according to Asana’s research.

Asana, State of AI at Work 2025

Tock prepares the repeat work.

Routines

Run the saved routine and bring the proposed updates back for approval.

Only 12% of workers say new information flows quickly between departments

Asana surveyed over 13,000 knowledge workers across six countries.

Asana, State of Work Innovation 2024

Arca asks your colleague.

Team requests

Request the missing fact. Your colleague chooses what to share.

Context that evolves with your business.

Your people, projects, and preferences carry into every task, and they update as the work changes.

Your daemon learns from the systems of record your business runs on: who owns each account, where each project stands, and how your team likes work done. As deals move and plans change, it keeps that picture current. Each fact links to its source. Correct it once, and every later task uses the correction.

Vigil keeps your context close.

Memory · Your preferences
Writing

Prefers short replies to customers.

Your sent mail
People

Your colleague leads the Acme account.

Account notes
Projects

Q4 expansion needs a revised scope.

October 28 call notes
You can read and correct what it knows.
Waiting for youProposed change

Update the opportunity

Salesforce · Acme · Q4 expansion

FieldCurrentProposed
StageDiscoveryProposal
Close dateNov 6, 2026Nov 20, 2026
Next stepFollow upSend revised scope

Why this change
The buyer asked to review a revised scope before a decision on November 20.

Evidence: Q4 expansion call notes, October 28

Approve once EditDecline

Nothing changes until you approve.

Plumb compares the call notes with your CRM and prepares these field changes for review.

It asks before it acts.

The exact email. The fields that will change. The entry going into your books. You see the work before it leaves your hands.

Review what will change, why it is being proposed, and the evidence behind it. Approve once, edit it, or decline.

Every run is recorded: what it read, what it proposed, what you approved, and what happened.

Read about approvals and records

One daemon. A team of agents.

Ask for an outcome. Your daemon turns it into a plan you can edit, gives helpers the steps, and brings the decisions back to you.

Under the hood, Daemons runs your agents in the cloud through connected accounts, and on your Mac inside apps you already use. Every external change needs your exact approval.

Your apps. Finally on the same page.

Connected accounts for cloud work. Apps you are already signed into on your Mac for local work. The same exact approval either way.

Gmail Google Calendar Slack Salesforce NetSuite QuickBooks Google Drive Google Docs Google Sheets Outlook Notion HubSpot

In the cloud.Nox works through the accounts you connect, so the work keeps going when your laptop is closed. Changes still wait for your approval.

On your Mac.Vigil works in the apps you are already signed into on your Mac, while it is on. Changes wait for the same approval.

Explore integrations

Good work is a team sport.

Work on the same task or routine with colleagues and their daemons. Edit the plan together and share the context you allow.

Shared routine

Q4 expansion

YCVigilArcaLive
Draft v3Everyone sees the same plan
VelaAccount context

Read account context

Acme call notes and open questions

YYouVigil
TaviPreparing draft

Revise scope

YYouVigil
Vigil is editing the scope
PlumbShared fact

Confirm approved scope

CYour colleagueArca

Your colleague permits this fact to be shared.

Revised scope approved on October 27.

Finance review · Scope decision
AurelWaiting for approval

Review customer update

After revised scope and approved scope

YCustomer messageWaiting

Exact recipient and message need approval before sending.

Arca shared approved scope with permissionVigil is using the fact to revise the scope.

Activity

Arca, your colleague’s daemon, shares only the context your colleague allows.

Memory2 agents7 tools4 calls/min$0.00
  • You (you).
  • Your daemon (agent, working): Linking this task to its sources. Calls in the last minute: Gmail 1, Memory 1.
  • Memory (agent, working): Linking facts to their source. Calls in the last minute: People 1, Your daemon 1.
  • People (tool).
  • Projects (tool).
  • Preferences (tool).
  • Gmail (tool).
  • Salesforce (tool).
  • Calendar (tool).
  • Docs (tool).

Memory that grows with your work.

Your people, accounts, projects, and decisions belong in the same picture.

Your daemon links what it learns to the work it came from. Each task adds context for the next. You can read what it knows and trace a fact back to its source.

A context graph: a connected map of your work.

Do it once. Save the routine.

When work repeats, your weekly review proposes a routine. You choose what to save and when it runs. Every send still asks you.

  1. Run a task
  2. Spot the repeat
  3. Review the suggestion
  4. Save and schedule
  5. Approve each change

Review the deals that need fixing

See stale opportunities and proposed corrections before you approve changes to the pipeline.

Weekly, for example Monday morning before forecast review; adjustable forecast cadence

Restart the deals worth pursuing

Review quiet opportunities with the last conversation and a useful reason to reconnect.

Weekly, for example every Monday

Find what is holding up close

Review missing close evidence, responsible owners, and messages asking for what is still needed.

Daily during the close window, starting several business days before close; also on demand

Remember what you agreed to deliver

Review your call commitments and prepared replies with exact figures and uncertain dates flagged.

When each meeting transcript is ready

Find the replies people are waiting for

See only conversations where you owe the next response, each linked to its source.

Each morning, looking back one week

Give each teammate their next step

Review assigned actions and recipient specific notes before anything goes to the team.

When a meeting recording or transcript is ready
Find your next routine

Yours to keep.

Your apps stay the system of record. Choose your model providers. Your daemon helps your team move faster while your work stays in the tools you chose.

Your records. Your choice of models. Your permission.

Built around your permission.

Reading and drafting run on their own. Every external change waits for your exact approval.

How Daemons is built
Your daemonWhat it may do without asking you
Safe actions run, risky ones wait for you

Runs on its own2

  • Read your email and docsGmail
  • Search Salesforce recordsSalesforce

Asks you first5

  • Draft replies and updatesRiskyGmail
  • Send emailsRiskyGmail
  • Update CRM recordsRiskySalesforce
  • Post in SlackRiskySlack
  • Change financial recordsDestructiveQuickBooks
If risky: 2 on its own, 5 ask first

Frequently asked questions

What is a daemon?

Your personal agent for work. It gathers context across your apps, coordinates a team of agents, and brings every external change back for your approval.

Do I need to write code?

No. Describe what you need in plain words. Your daemon prepares a plan you can read and edit before work begins.

Will it send anything without me?

Every external change needs your exact approval, including emails, messages, account updates, and remote drafts. You see the recipient, content, or field changes before you decide.

Which apps does it work with?

Workflows cover pipeline work and finance close, using tools such as Salesforce, Slack, Gmail, Google Calendar, NetSuite, and QuickBooks. Explore the integrations directory to find your tools.

Does it work when my laptop is closed?

Eligible cloud steps use the connected accounts you grant access to. Steps that depend on an app or signed in session on your Mac need your Mac available. A prepared external change still waits for approval.

What does it remember, and can I see it?

The memory design connects people, projects, accounts, preferences, and decisions to their sources. You can inspect and correct what it remembers.

Can my team use it together?

In Preview, you can share tasks, routines, and your screen, and ask questions between daemons with permission. Your colleague chooses which facts to share.

How is this different from a chatbot?

Your daemon coordinates work across apps through a visible plan. It prepares specific changes, asks for approval, and keeps a signed record of the run.

What does it cost?

Daemons is in early access, and pricing is not public yet. Tell us about your team and the first task you would hand over, and we will talk it through.

How do I start?

Choose “Team up with your daemon” and tell us about the first task you would hand over. The early access page opens a draft in your email app so you can send it to us.

Meet your daemon.

What holds up your workday?

Plumb, on pipeline cleanup.

A pipeline you can trust.

  1. Compare call notes with your CRM.
  2. Flag stale stages and missing next steps.
  3. Prepare the exact field changes.

Every CRM update waits for your approval.

Aurel, on month-end close.

Find what is holding up close.

  1. Compare the ledger with source records.
  2. Gather evidence for each exception.
  3. Prepare corrections for your review.

Every accounting entry and shared update waits for your approval.

Vigil, on inbox triage.

Give the replies a head start.

  1. Gather the threads that need a reply.
  2. Look up the context behind each request.
  3. Prepare replies with the sources attached.

Every send and remote draft waits for your approval.

Arca, on meeting prep.

Walk in with the context.

  1. Find the last notes and open commitments.
  2. Ask your colleague’s daemon for missing facts.
  3. Prepare a brief for your next conversation.

Your colleague chooses what to share. Publishing or sending the brief needs your approval.

Theo, on reporting.

A report you can trace.

  1. Gather the figures from connected sources.
  2. Check the differences and link the evidence.
  3. Prepare a report with the open questions.

Publishing the report or changing a shared document waits for your approval.