Everything a crew runs on,
and a record of all of it.

A calendar that keeps itself

Every task has a cron schedule in the crew's time zone. A run missed while the box was down fires once when it comes back, if it is recent enough to still matter. You can pause a persona, switch its schedule off, start a task by hand, or cancel a run in flight — from the web, or by talking to it in Slack.

Each run records its verdict, its transcript, the seat it used, and what it spent as the engine reported it: tokens, turns, and the engine's own cost estimate. On Claude Code and Grok, a task can carry a turn ceiling, and a run that spends it stops and says so rather than retrying.

Standing rules, learnings, and digests

Standing rules are the crew's house rules — how to speak, what never to touch, where the source of truth lives — and every prompt carries them. Learnings are one-line lessons a run proposes and an approver accepts, or that you write yourself; they join every future prompt for that persona or task until someone retires them. The digest is each persona's weekly summary of what it ran, found, and proposed, with notes you can add on the web.

It tells you when it cannot tell you

The box checks itself — engines and their versions, each login, every channel the crew posts in, its Slack connection, its workspaces, its own home directory — and klingbar.com shows the checks with how old they are. A box that stops syncing reads stale within five minutes. A box that cannot prove its own home directory refuses to write and says why. And anything the box never sent reads "not reported", because a green nobody measured is worse than no answer.