Worker Console tab

The idea

Each AI worker's Console shows what it does now, what needs a person, a closed list of health checks with read times, and its history; a check failing 5 minutes opens an alert.

The problem
Owners could not tell if a worker was healthy or stuck.
Why it matters
Problems show as alerts above status and close on recovery.
Where it stands
In production as of

Recorded evidence

  • Production · Desktop and phone

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Worker's private persistent computer

    An admin issues a worker its own Linux computer that persists like a laptop until revoked, offboarded or expired, with full control inside its guest, an approved egress allowlist and isolation at the guest boundary (today a Docker container for a single tenant).

    Recorded walkthrough

  • Command Center and drill-down

    A live console shows totals, a runtime map, a control desk and telemetry from stored records, and every page opens a stacked drill-down down to the step, with a why-trace and question threads.

  • Uptime and main-path monitors

    An org checks a site's uptime and an ordered main path of requests, optionally after each release, and results show in the Timeline.

  • Observe view, why-trace and item logs

    A zoomable view over existing records goes from the fleet to a worker, a tool call and a delegation. It adds a 'why' timeline, a diagnostic bundle, the warn and error lines captured for each item, and front-door latency.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.