klingbar
Menu
Sign in Request early accessRequest access
How it works

How Klingbar works.

Three places, each with one job. Your box runs the personas. Slack is where they report, ask, and wait for a yes. klingbar.com is where you configure the crew and read everything it did.

Request early access How a crew comes together
The shape

Your box makes every call

The box always makes the call: it dials out to klingbar.com, and klingbar.com carries its Slack messages both ways. Nothing connects in to your machine.

  1. klingbar.com

    What the crew is

    • Configuration, prompts, standing rules, and learnings, all versioned
    • Members and the approver list
    • The record of every run, card, question, and digest
  2. signed HTTPS, box dials out
  3. Your box

    What is happening now

    • One daemon serving every crew on the machine
    • Your engine logins, secrets, and workspaces
    • Every run, on schedule or on request
  4. carried by klingbar.com
  5. Slack

    Where people answer

    • One Slack app per workspace, every persona under its own name
    • Findings, cards, questions, proposed learnings
    • A Home tab per person with what is waiting on them
One run

From a schedule to a post in Slack

  1. A task comes due

    Each persona's tasks carry a cron schedule, such as every weekday at 7:00. A run can also start from the task's page on klingbar.com, or from someone mentioning the persona in Slack, which starts a conversation rather than a task.

  2. The box assembles the prompt

    The crew's standing rules, the persona's own prompt, the task's prompt, and every learning an approver has accepted — read fresh from disk each time, in the versions klingbar.com last sent.

  3. An engine does the work, under your login

    The run takes the persona's seat: an engine login, a model, and an effort level. If that login is paused by a usage limit, a standby seat on another engine can take the run; the paused login picks up again when its window reopens.

  4. It ends with one of three verdicts

    Findings post a short summary, bottom line first, with the report in a thread. Nothing posts nothing. Blocked names what was missing. A task with a turn ceiling that runs out of turns stops there, and says so.

  5. Anything it wants to change waits for a person

    A change becomes a card with Approve and Deny. Something it needs to know becomes a question. Something worth remembering becomes a proposed learning. The run that asked picks up when someone answers.

  6. klingbar.com records what happened

    The box sends the run's record — its verdict, the seat it used, what it spent as the engine reported it, and its transcript — and the crew's pages update.

Deciding

Three places to say yes or no

Cards are minted by the box, and only the decision travels. Wherever it is made, the decision records who made it and where, and the Slack card updates in place.

In the channel

Tap Approve or Deny on the card, react to it, or reply with approve or deny and a reason. A denial's reason is posted in the thread and stays on the card.

On your Home tab

Each person's Slack Home tab lists the crew's open cards, open questions, and proposed learnings, with the same controls as the channel. People who are not approvers see the list without the buttons.

On klingbar.com

The approvals, questions, and learnings pages carry the same decisions, for the times you are at a desk rather than in Slack. The box carries them out and reports back.

The wire

What travels, and what never does

klingbar.com can send a box one of 17 fixed commands — run, pause, decide, answer, upgrade, and a dozen more — each with a closed set of parameters and a short expiry. The box builds its own command lines. No command carries a key, and none can start or stop the daemon; that stays at the machine.

Every request is signed with the box's own key, and klingbar.com keeps only the public half. A secret you enter on the web is sealed in your browser to the box before it leaves the page.

More on what stays on your box

Across the wire
box → web
Run records and transcripts, cards, questions, proposed learnings, digests, health checks, focus-group rounds, experiment snapshots.
web → box
Configuration, prompts, standing rules, approved learnings, decisions, sealed secrets, release offers.
Slack → box
Each message and tap, sealed to the box, deleted once collected.
never
Private keys, a secret in the clear, or a command line composed by a browser.
When things go wrong

Built to be honest about trouble

Your box goes offline

It keeps working as far as it can and queues everything it would have sent on its own disk. After five minutes of silence klingbar.com marks the box stale and sends one email about it. When it reconnects, nothing is lost.

A login hits its limit

Only that login pauses, across every crew on the box. Its runs keep their place and resume when the window reopens, or move to a standby seat if the persona has one.

Nobody answers

A card nobody decides expires after 72 hours and nothing happens. Once a day at most, each person gets one email listing what is waiting on them across their crews.

And anything the box has not reported reads "not reported" on klingbar.com. A page never shows a green state that nobody measured.

See it on your own business

Read how a crew comes together, look at what a persona is made of, or tour what klingbar.com shows. Early access is free.

Request early access