agents active

A self-hosted, always-on multi-agent setup built on OpenClaw and running on a Mac Studio. A primary orchestrator agent fields requests across messaging channels and delegates to specialized subagents (some cloud-hosted, one running fully on-device), backed by scheduled automations that report in on a cadence.

Architecture

                  ( messaging channels )
                            │
                            ▼
        ┌──────────────────────────────────────┐
        │ OpenClaw gateway                     │
        │ launch-on-login; brokers everything  │
        └───────────────────┬──────────────────┘
                            ▼
        ┌──────────────────────────────────────┐
        │ main  ·  orchestrator                │
        │ routes each task to a subagent       │
        └───────────────────┬──────────────────┘
                            │ delegates to
              ┌─────────────┼─────────────┐
              ▼             ▼             ▼
            cloud        lil-sis     askthelyrics
            subagent     on-device   content pipeline
            (other       local       sources -> answers
             provider)   model       via API -> publishes

        scheduled jobs (cron) ──▶ trigger agents on a cadence,
                                  results posted back to chat

The fleet

• main is the orchestrator. It handles general tasks and routes work to the right subagent. It carries its own identity, instructions, tool set, and a persistent memory store.
• cloud subagent is a second cloud agent the orchestrator delegates to for tasks suited to a different provider.
• lil-sis is a fully on-device agent running a local model on a Mac Studio with no cloud round-trip. It runs coding tasks, system monitoring, and the scheduled ops reports.
• ask-the-lyrics agent is a content-pipeline agent that turns ask the lyrics into a self-publishing feed: it sources questions, answers them, quality-gates, and posts the best.

Orchestration

The OpenClaw gateway runs as a launch-on-login service and brokers everything: agent definitions, channel bindings, and a set of scheduled jobs that trigger recurring work, with each agent reporting its results back into chat. Every agent is defined declaratively (identity, personality, tools, heartbeat instructions), and the whole configuration is versioned and backed up automatically.

Scheduled automations

Recurring jobs run mostly by lil-sis on cron, each summarized back to a chat channel:

• Water monitor pulls daily readings from a smart water meter, breaks down today/yesterday gallons and cost, flags anomalies (like sprinkler days), and projects the full billing-cycle bill as a point estimate with a range.
• Mining monitor watchdogs a fleet of ASIC miners (auto-restarting hung units), then reports total hashrate, per-miner status (hashrate + temperature), and pool balance (BCH and USD).
• System-health snapshots & service metrics covers periodic resource snapshots and app health/metrics checks.

Everything runs on a Mac Studio (M3 Ultra, 96 GB), including the on-device lil-sis model.

Draft. Deeper detail on the other agents coming.

Stack: OpenClaw gateway, scheduled cron jobs, a Mac Studio (M3 Ultra) host; a mix of cloud and on-device models.