Coding

TinkerClaw Subagent Overseer

Try it

You spawned 4 sub-agents. One died 20 minutes ago. You're still waiting. Overseer watches them so you don't have to — zero tokens, pure OS-level process checks. No polling loops, no wasted heartbeats.

What it does

Lightweight pull-based daemon that monitors sub-agent health. Writes a status file every N seconds. The heartbeat handler reads it — no push, no noise.

The skill document

Sub-Agent Overseer

Lightweight pull-based daemon that monitors sub-agent health. Writes a status file every N seconds. The heartbeat handler reads it — no push, no noise.

Architecture

overseer.sh (bash, runs in background)
    ├── /proc/  → gateway alive? CPU? threads?
    ├── openclaw sessions list  → sub-agent count + ages
    ├── find -newer marker  → filesystem activity
    └── writes /tmp/overseer/status.json  (atomic mv)

heartbeat (agent, every 3min)
    └── reads /tmp/overseer/status.json → summarize or HEARTBEAT_OK

Key principle: The overseer does all data collection. The heartbeat handler does zero tool calls if the status file is fresh and healthy.

Quick Start

1. Start the overseer when spawning sub-agents

setsid scripts/overseer.sh \
  --workdir /path/to/repo \
  --interval 180 \
  --max-stale 4 \
  --voice \
  &>/dev/null &

2. Heartbeat reads the status file

cat /tmp/overseer/status.json

3. Interpret the status

FieldMeaning
subagents.countActive sub-agent sessions
subagents.details[].staleConsecutive cycles with no filesystem changes
subagents.details[].statusactive / idle / warning / stuck
gateway.health.aliveIs openclaw-gateway running?
filesystem.changes_since_lastFiles modified since last check

4. Staleness thresholds (at 180s interval)

stale countTimeStatusAction
0-10-3 minactive/idleNormal
2-36-9 minwarningVoice alert (if --voice)
≥4≥12 minstuckAgent should investigate/kill

Heartbeat Handler Protocol

When HEARTBEAT.md fires:

  1. Read /tmp/overseer/status.json — if missing or stale (>10 min), restart overseer
  2. If subagents.count == 0 for 2+ cycles → overseer auto-exits → reply HEARTBEAT_OK
  3. If all agents active → brief one-line status → HEARTBEAT_OK
  4. If any stuck → report which labels are stuck → consider killing via subagents kill
  5. Never cache a previous heartbeat response. Always read the status file fresh.

Flags

FlagDefaultDescription
--interval180Seconds between checks
--workdircwdDirectory to watch for file changes
--labels(all)Comma-separated labels to filter
--max-stale4Cycles before marking stuck
--voiceoffLocal TTS alerts via jarvis command

How It Works (No AI Tokens)

  1. Gateway health: Reads /proc//status for CPU, memory, threads, FD count. Pure kernel data.
  2. Sub-agent list: Single openclaw sessions list call per cycle. Parses grep output.
  3. Filesystem diff: find -newer marker — detects any file writes in the workdir.
  4. Status file: JSON written atomically (write to temp, mv into place). Any reader sees a complete file.
  5. Self-exit: If no sub-agents for 2 consecutive cycles, the overseer stops itself.
  6. Dedup: flock ensures only one overseer instance runs at a time.

Cost

  • Overseer: $0.00 (bash + /proc + one CLI call per cycle)
  • Voice alerts: $0.00 (local sherpa-onnx via jarvis)
  • Heartbeat reads status file: $0.00 (one cat command)
  • Only cost is the heartbeat model itself (qwen3 local = free)

Pairs Well With

👉 https://github.com/globalcaos/tinkerclaw

Clone it. Fork it. Break it. Make it yours.

Related skills

Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.

by johnpatternai21 installs8 stars

Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.

by Iván555 installs18 stars

Query Twitter/X profiles, tweets, follower events, and KOL data through the 6551 REST API.

by infra403840 installs27 stars

Trade crypto, manage a multi-chain wallet, and query an AI analyst from one CLI.

by lowesyang162 installs109 stars

Query and manage Linear issues, projects, teams, cycles, labels, and comments through a managed OAuth GraphQL endpoint.

by byungkyu518 installs18 stars

Adaptive web scraping in Python that bypasses anti-bot systems and scales from single requests to concurrent crawls.

by d4vinci399 installs28 stars

More from globalcaos

Browse all skills

Give your OpenClaw agent a JARVIS-style British voice with matching dry humor, audio plus a purple chat bubble in one call.

by globalcaos190 installs4 stars

Native WhatsApp channel for OpenClaw with 22 messaging/group actions plus Protocol v2 multi-agent coordination.

by globalcaos116 installs3 stars

One dashboard tracking Anthropic, Gemini, OpenAI, and Manus token usage with budget alerts and a local REST API.

by globalcaos59 installs

Stop sending 'format this JSON' to Opus. Stop sending 'cron job' to GPT. Billing-aware routing guide for choosing among the models already configured in your OpenClaw setup when assigning an agent, sub-agent or cron task — flat-rate first, metered only when justified, budget pressure respected. Not for picking models outside your configuration, and not a runtime proxy.

by globalcaos16 installs

Your agent says 'done' — but did it check? Superpowers turns any OpenClaw agent into a disciplined engineer. Verification iron law (evidence before claims), three-agent code review (build → verify spec → verify quality), systematic debugging (4-phase root cause, three-strike rule), brainstorming gates (design before code), and anti-over-engineering rules. Use when: (1) coding tasks of any complexity, (2) debugging failures, (3) about to claim work is complete, (4) spawning sub-agents, (5) planning features, (6) reviewing code. Inspired by top coding agent methodologies, adapted for OpenClaw multi-agent architecture.

by globalcaos14 installs

Read and search Outlook, inspect attachments, and create or edit drafts without any send endpoint. Uses one short-lived Microsoft Graph access token supplied on stdin for one run; it never stores credentials. Bulk mailbox export is opt-in.

by globalcaos23 installs