clawd (“Caleb”) — the standby assistant — Fleet Playbook

The Fleet › clawd (“Caleb”) — the standby assistant
👤 Orchestration

clawd (“Caleb”) — the standby assistant

A persistent personal-assistant agent with its own soul, memory, and judgment about when to speak. Wakes on a heartbeat to do quiet background work — right now its heartbeat checklist is empty, so it’s parked.

Caleb is what a personal chief-of-staff looks like when it’s an agent. It has a
SOUL.md (how it behaves), a USER.md (who it works for), and dated memory files it reads
at the start of every session — because it wakes up fresh each time and those files are its continuity.

What it does

On a heartbeat poll, it reads its HEARTBEAT.md checklist and does small, safe, proactive work:
skim the inbox for anything urgent, glance at the calendar, tidy and update memory. It is deliberately conservative —
bold with internal actions (reading, organizing), careful with external ones (never sends on your behalf without a nod).

Current status: its HEARTBEAT.md is empty, which by design
skips the heartbeat entirely. Caleb is parked — zero token burn — until you give it a checklist. That’s a
feature: an idle agent shouldn’t cost anything.

How it fits

Where clawdbot is the switchboard, Caleb is a single, trusted aide. In the recursive system it’s the layer that
turns “things I keep meaning to check” into background work — the connective tissue between the big scheduled jobs.

← Back to the full fleet

Job facts

Systemclawd/
TriggerHeartbeat-driven
ScheduleOn heartbeat · currently idle
StatusStandby
TimingNo shared-quota use
Wired toMemory files, Heartbeat, Skills