Morning Brief · first AI employee

Turn the first hour of scanning into a 2-minute brief.

An AI employee that handles "look at everything before deciding anything": one prioritized brief, named decisions, named blockers, named next actions.

RuntimeHermesOpenClaw

Hire this AI employee See where it runs

Sample output

Today's brief, in product

Tue, May 21 · 09:02

3 decisions, 2 blockers, 5 next actions. Nothing urgent that has to leave your inbox today.

Priorities

Close the Morning Brief landing-page line.
Reply to Pixhost demo invite for next week.
Decide whether to extend the Cloud starter-month launch by a week.

Decisions waiting on you

Should legacy OpenClaw room-style Packs appear in the "coming soon" rail? (recommended: yes)
Should we send a Playbook seasonal note to legacy Pro owners?
Cloud starter-month extension → yes / no / hold one more week

Blockers

Studio trigger spec still in draft, waiting on design review.
Stripe webhook metadata migration green on staging, waiting on your go.

Next actions

Ship /usecases landing copy (owner: you)
Send Trust page FAQ for design review (owner: AI)
Reply to Pixhost demo invite (owner: you · waiting on your call)
Draft Cloud starter-month copy for ContactSubscribe (owner: AI · waiting on your approval)
Turn today's decisions into Instance Knowledge suggestions (owner: AI · waiting on your review)

Why you keep doing this by hand

Before you make a single decision you scan: inbox, calendar, docs, group chats, news, open decisions. Same routine every morning, eating the most valuable hour of the day.

It is 9:30 by the time you finish scanning, and the real decision time is already gone.
Important decisions get buried under repeated reminders.
Replies, commitments, and spend live in five different places with no single approval queue.

What it does every morning

Reads
Sweeps connected sources and collapses repeats your way.
Synthesizes
Turns the sweep into a 2-minute summary you can read.
Names decisions
Pulls out the items that need you to call it today.
Flags blockers
Marks anything stuck or waiting on someone.
Creates next actions
Generates a small queue with named owners.

What it needs to connect to

Read-only by default. You decide what to plug in; nothing fakes access to a system it never saw.

Inbox (IMAP / Gmail)

Needs setup

Reads the last 12 hours of unread and pending replies.

Calendar (ICS / Google Calendar)

Needs setup

Reads today and tomorrow.

Task source (GitHub Issues / Linear / Notion)

Needs setup

Reads the boards you point it at.

Doc folder

Ready

Reads only the Cloud-side folder you assign.

News source

Ready

Optional. Pulls from an allow-listed RSS set.

What it never does without approval

Outbound actions always land in the approval queue. If you do not tap confirm, nothing leaves.

Outbound replies

Email, DM, and community reply drafts stay as drafts.

Commitments

Any phrasing that promises a date, deliverable, or person is flagged for you.

Spending

Paid API calls, paid reports, ad spend all wait for your tap.

Public content changes

Site copy, tweets, public docs all need an explicit approval.

How it runs

Inside your voxyz Cloud workspace. Hermes handles the daily Agent surface and schedule. OpenClaw is there too when the job needs WebChat or a room-style Pack.

RuntimeHermesOpenClaw

Schedule and delivery

Default schedule: once every morning, in your timezone.
Rerun on demand — say, before a meeting.
Delivery: email, Telegram, Slack, or inside the Cloud workspace.

Why it gets sharper over time

Instance Knowledge keeps stable rules, taste, and decisions so the next brief does not re-ask the same question.

Remembers taste

If you said "do not relist completed items on Monday", it stops.

Remembers decisions

Items you already called stop reappearing as open decisions.

Remembers people

Roles and sensitivity for your team and external contacts only need to be set once.

Want it more your way?

Morning Brief's shape, sources, schedule, and taste are tunable. Start with the default, then customize once it is in your day.

See what Cloud picks up for you

Common questions

What if I do not connect any source?

You get an empty brief plus a list of the highest-value sources to connect first. The brief never pretends to read systems it does not have access to.

My team spans timezones — what happens?

The brief follows your account's timezone by default; team workspaces can set different timezones per AI employee in Cloud.

The brief is too noisy. How do I fix it?

Mark the noisy item with "do not relist." It becomes an Instance Knowledge suggestion; once you approve it, the next brief stops surfacing it.

Does it send emails on its own?

No. Outbound stays in the approval queue. Nothing leaves until you tap confirm.

Can multiple AI employees share the same brief?

Yes. Other employees in the same Cloud workspace (inbox, research, support) can reuse Instance Knowledge, while each keeps its own local memory.

Hire your first AI employee.

Start with Morning Brief. More employees can join the same Cloud workspace later.

Hire this AI employee See where Cloud control sits

Morning Brief · first AI employee

Turn the first hour of scanning into a 2-minute brief.

An AI employee that handles "look at everything before deciding anything": one prioritized brief, named decisions, named blockers, named next actions.

RuntimeHermesOpenClaw

Hire this AI employee See where it runs

Sample output

Today's brief, in product

Tue, May 21 · 09:02

3 decisions, 2 blockers, 5 next actions. Nothing urgent that has to leave your inbox today.

Priorities

Close the Morning Brief landing-page line.
Reply to Pixhost demo invite for next week.
Decide whether to extend the Cloud starter-month launch by a week.

Decisions waiting on you

Should legacy OpenClaw room-style Packs appear in the "coming soon" rail? (recommended: yes)
Should we send a Playbook seasonal note to legacy Pro owners?
Cloud starter-month extension → yes / no / hold one more week

Blockers

Studio trigger spec still in draft, waiting on design review.
Stripe webhook metadata migration green on staging, waiting on your go.

Next actions

Ship /usecases landing copy (owner: you)
Send Trust page FAQ for design review (owner: AI)
Reply to Pixhost demo invite (owner: you · waiting on your call)
Draft Cloud starter-month copy for ContactSubscribe (owner: AI · waiting on your approval)
Turn today's decisions into Instance Knowledge suggestions (owner: AI · waiting on your review)

Why you keep doing this by hand

Before you make a single decision you scan: inbox, calendar, docs, group chats, news, open decisions. Same routine every morning, eating the most valuable hour of the day.

It is 9:30 by the time you finish scanning, and the real decision time is already gone.
Important decisions get buried under repeated reminders.
Replies, commitments, and spend live in five different places with no single approval queue.

What it does every morning

Reads
Sweeps connected sources and collapses repeats your way.
Synthesizes
Turns the sweep into a 2-minute summary you can read.
Names decisions
Pulls out the items that need you to call it today.
Flags blockers
Marks anything stuck or waiting on someone.
Creates next actions
Generates a small queue with named owners.

What it needs to connect to

Read-only by default. You decide what to plug in; nothing fakes access to a system it never saw.

Inbox (IMAP / Gmail)

Needs setup

Reads the last 12 hours of unread and pending replies.

Calendar (ICS / Google Calendar)

Needs setup

Reads today and tomorrow.

Task source (GitHub Issues / Linear / Notion)

Needs setup

Reads the boards you point it at.

Doc folder

Ready

Reads only the Cloud-side folder you assign.

News source

Ready

Optional. Pulls from an allow-listed RSS set.

What it never does without approval

Outbound actions always land in the approval queue. If you do not tap confirm, nothing leaves.

Outbound replies

Email, DM, and community reply drafts stay as drafts.

Commitments

Any phrasing that promises a date, deliverable, or person is flagged for you.

Spending

Paid API calls, paid reports, ad spend all wait for your tap.

Public content changes

Site copy, tweets, public docs all need an explicit approval.

How it runs

Inside your voxyz Cloud workspace. Hermes handles the daily Agent surface and schedule. OpenClaw is there too when the job needs WebChat or a room-style Pack.

RuntimeHermesOpenClaw

Schedule and delivery

Default schedule: once every morning, in your timezone.
Rerun on demand — say, before a meeting.
Delivery: email, Telegram, Slack, or inside the Cloud workspace.

Why it gets sharper over time

Instance Knowledge keeps stable rules, taste, and decisions so the next brief does not re-ask the same question.

Remembers taste

If you said "do not relist completed items on Monday", it stops.

Remembers decisions

Items you already called stop reappearing as open decisions.

Remembers people

Roles and sensitivity for your team and external contacts only need to be set once.

Want it more your way?

Morning Brief's shape, sources, schedule, and taste are tunable. Start with the default, then customize once it is in your day.

See what Cloud picks up for you

Common questions

What if I do not connect any source?

You get an empty brief plus a list of the highest-value sources to connect first. The brief never pretends to read systems it does not have access to.

My team spans timezones — what happens?

The brief follows your account's timezone by default; team workspaces can set different timezones per AI employee in Cloud.

The brief is too noisy. How do I fix it?

Mark the noisy item with "do not relist." It becomes an Instance Knowledge suggestion; once you approve it, the next brief stops surfacing it.

Does it send emails on its own?

No. Outbound stays in the approval queue. Nothing leaves until you tap confirm.

Can multiple AI employees share the same brief?

Yes. Other employees in the same Cloud workspace (inbox, research, support) can reuse Instance Knowledge, while each keeps its own local memory.

Hire your first AI employee.

Start with Morning Brief. More employees can join the same Cloud workspace later.

Hire this AI employee See where Cloud control sits

Turn the first hour of scanning into a 2-minute brief.

Priorities

Decisions waiting on you

Blockers

Next actions

Why you keep doing this by hand

What it does every morning

Reads

Synthesizes

Names decisions

Flags blockers

Creates next actions

What it needs to connect to

Inbox (IMAP / Gmail)

Calendar (ICS / Google Calendar)

Task source (GitHub Issues / Linear / Notion)

Doc folder

News source

What it never does without approval

Outbound replies

Commitments

Spending

Public content changes

How it runs

Why it gets sharper over time

Remembers taste

Remembers decisions

Remembers people

Want it more your way?

Common questions

Hire your first AI employee.

Use Cases

Turn the first hour of scanning into a 2-minute brief.

Priorities

Decisions waiting on you

Blockers

Next actions

Why you keep doing this by hand

What it does every morning

Reads

Synthesizes

Names decisions

Flags blockers

Creates next actions

What it needs to connect to

Inbox (IMAP / Gmail)

Calendar (ICS / Google Calendar)

Task source (GitHub Issues / Linear / Notion)

Doc folder

News source

What it never does without approval

Outbound replies

Commitments

Spending

Public content changes

How it runs

Why it gets sharper over time

Remembers taste

Remembers decisions

Remembers people

Want it more your way?

Common questions

Hire your first AI employee.