Henry’s agent use cases

These are plain examples of how Henry and the Enterprise Crew use agents in daily work. Not a prompt library. Not a raw catalog. Just the recurring jobs, what each one connects to, what comes back, and where the human approval line sits.

Readable by a normal operator

Each example explains the work in human terms. “Meeting prep” is easier to understand than “calendar-aware contextual synthesis loop,” which sounds like a SaaS landing page got trapped in a blender.

Built around approval

The useful part is not just that an agent can act. It is knowing what it can do alone, what it should draft, and where it must stop for Henry.

Examples

How the system gets used

Operations

Heartbeat

Ada checks the agent fleet every hour and posts a short status card when something changed or needs attention.

When it runs
Hourly, into the private #heartbeat channel.
What it connects to
Hermes cron state, gateway health, storage headroom, dropped-session watchdogs, error clusters, Entity docs, and recent agent receipts.
What Henry gets back
A compact readiness score, the main blocker, any safe recovery Ada already performed, and a deep-dive link with the evidence.
Where the human stays in charge
Ada can inspect, recover dropped internal threads, update receipts, and perform safe local fixes. Anything destructive, customer-facing, credential-related, or broader than the approved maintenance window stops for Henry.
Daily briefing

Morning brief

Ada turns calendar, inbox, task, vault, and fleet signals into a short morning brief Henry can act on.

When it runs
Every morning at 7am, delivered to the internal ops channel.
What it connects to
Google Calendar, Gmail, Obsidian notes, recent sessions, Mission Control-style task surfaces, crew health checks, and Henry’s current location/timezone file.
What Henry gets back
Three concrete actions for the day, what finished overnight, what is blocked, and anything that needs Henry rather than another agent pretending to be useful.
Where the human stays in charge
The agent can read, summarize, archive low-risk inbox noise under standing rules, and draft. It cannot send as Henry, make commitments, change external calendars, or publish without approval.
Research

AI news watch

Spock and the WeeklyClaw research jobs scan AI news, remove duplicates, and turn useful developments into briefs or draft posts.

When it runs
Daily and twice-daily, depending on the lane. Some runs stay silent when there is nothing worth sending.
What it connects to
Hacker News, TechCrunch AI, The Verge AI, Ars Technica, credible X sources, Polymarket AI-market state, saved research memory, and prior draft history.
What Henry gets back
Ranked AI items with source links, why they matter, draft social posts when useful, and a clear marker when the evidence is weak or already covered.
Where the human stays in charge
Research and draft staging can run alone. Public posts, market-facing claims, customer references, or anything with shaky sourcing wait for review.
Meetings

Meeting prep

Before a call, Ada builds the context Henry would otherwise hunt through manually. After the call, it turns the transcript into next steps.

When it runs
On demand or as part of a meeting-actions workflow.
What it connects to
Calendar events, attendee names, company context, prior notes, CRM-style relationship memory, docs, email threads, and meeting transcripts from tools like Fireflies or Google Meet captions when available.
What Henry gets back
A prep note with who is joining, what has happened before, likely agenda, useful questions, open risks, and after the call, owner-backed action items plus follow-up drafts.
Where the human stays in charge
Prep, summaries, and draft follow-ups are safe. Sending messages, changing calendar invites, or making commercial promises requires approval unless a standing workflow already covers that exact action.
Relationships

Personal CRM

A daily sync keeps Henry’s relationship memory fresh without turning it into a creepy outreach cannon. We are civilized villains here.

When it runs
Daily at 5:45am, local-only.
What it connects to
Gmail, Google Calendar, Slack, Fireflies, Apollo contact data, local CRM tables, embeddings, duplicate checks, and relationship-health scoring.
What Henry gets back
Updated contacts, interaction history, relationship health, duplicate suggestions, and a searchable base for meeting prep or follow-up.
Where the human stays in charge
The sync is read-only against providers and writes only to the local CRM database. It does not send messages, launch outreach, enrich contacts externally, or mutate provider records.
Inbox

Urgent message triage

Ada watches for messages that are easy to miss but expensive to ignore, then stages the response path.

When it runs
As a recurring check or on demand when Henry asks for an inbox audit.
What it connects to
Gmail, Slack or Discord mentions, WhatsApp/Beeper queues, sender history, current priorities, and thread context.
What Henry gets back
A short list of what needs attention, why it matters, suggested next action, and draft replies when useful.
Where the human stays in charge
Reading and drafting can be automatic. Sending as Henry, contacting a new person, making promises, or escalating externally needs approval.
Product

Runner builds a scoped task

A coding runner takes a bounded ticket, changes the repo, runs the gate, and returns proof instead of “looks good” fog machine nonsense.

When it runs
On approved tickets or durable project loops.
What it connects to
GitHub or local repo state, task brief, acceptance criteria, tests, build commands, review tools, and deployment rules.
What Henry gets back
A branch or patch, the exact diff, test/build output, blockers, and the next merge or review step.
Where the human stays in charge
Local reversible edits and tests can run. Merge, production deploy, destructive migration, customer release, or expanded scope waits for Henry or the project owner.
Publishing

Public-safe resource page

Ada turns a private evidence pack into a page strangers can read without exposing private proof or internal mess.

When it runs
When a resource, use-case page, article, or public artifact needs to ship.
What it connects to
Private receipts, source notes, repo content, screenshots, diagrams, QA scripts, build output, deployment status, and production route checks.
What Henry gets back
A readable page, a privacy-safe version of the useful pattern, build receipts, route checks, and a clear list of anything blocked by approval or missing credentials.
Where the human stays in charge
Drafting, local build, and QA can run. Public release needs privacy review and approval for sensitive claims, private evidence, customer references, or external announcements.

Setup pattern

The recipe is boring on purpose

Good agent workflows are not magic. They are clear inputs, a narrow job, a delivery route, and a gate. The boring version works. The cinematic version sends you a 19-page report no one asked for and calls it strategy.

  1. Pick one repeated job Henry already has to do.
  2. Connect the safe sources the agent is allowed to read.
  3. Define what the agent returns and where it delivers it.
  4. Write the approval boundary before the automation runs.
  5. Keep receipts, so the output can be checked instead of trusted.
See moreThe full workflow atlas, with every mapped use case and filters by agent and category.