How a crew comes together.
After you sign up, a nine-step guide sets up your first crew with you in about ten minutes. It writes each persona's first prompt from a starter, and you edit any of it afterwards.
What you need
- an invite
- Accounts are invite-only during early access. Request one; your account is created with a passkey, not a password.
- a box
- A Linux machine you control with Python 3.12 or newer — a small server, a VM, or a spare computer. It needs outbound internet and nothing inbound. A Mac can run the daemon in the foreground for a trial, without the service that keeps it running.
- an engine
- At least one of Claude Code, Codex, OpenCode, Antigravity, Grok, or Gemini, installed on the box and logged in with your own account.
- Slack
- A workspace where you can add apps. You add Klingbar once, and every crew there uses it.
Nine steps, about ten minutes
The guide starts the first time you sign in. Your answers save at every step, so you can leave and come back to the same place.
- 1 welcome
- What a crew, a box and a persona are, and what you will need.
- 2 your business
- What it does, how it makes money, who the customers are, and what matters most right now. Every persona reads this before every run.
- 3 your role
- Who the crew writes for, and how often you want to hear from it.
- 4 your crew
- Pick from eight starter personas; the guide preselects the ones that suit how your business makes money. Then tick the tools you use, so each persona knows where to look.
- 5 Slack
- Add Klingbar to your Slack workspace with one button; you become the crew's first approver.
- 6 AI subscription
- The AI tool your personas run on, signed in on the box with your own account.
- 7 where it runs
- Pair a Linux machine with one pasted line, send the instructions to someone technical, or pick a box you already have.
- 8 review and create
- Check the crew over. Creating it writes its configuration, its standing rules and every persona's prompt.
- 9 launch
- Once the box has the crew, switch the schedules on and, if you like, run a first task to see a result in Slack.
Create a blank crew instead
The path you take when you skip the guide: press "Not now" on its first page, then choose "Create a blank crew instead" on your crews page. You write every persona yourself, in eight steps. Plan on an afternoon, most of it spent writing the first persona's prompt.
-
Pair a box
On klingbar.com, name the machine and copy the one line it gives you. Run it on the box as your own user, not as root.
$ curl -fsSL https://klingbar.com/install.sh \ | sh -s -- --pair KB-XXXX-XXXXThe installer checks the release against its published checksum (and its signature, where a signing fingerprint is published), sets up the daemon in its own directory, pairs with the code, and starts it — as a systemd user service where the box has one. The page waits for the box to check in, then says it has.
-
Log in to your engines
On the box, log in to each engine CLI you want the crew to use; the box reports which engines and models it found, and klingbar.com offers exactly those. With the installer, that is usually all you type on a box. A persona that works in your code repository also needs one
crew workspaces --crew <slug>there once the persona exists, and read access to the repository (a deploy key, orgh auth login). A tool a persona reads through a command-line login, such as gcloud or the aws CLI, is signed in on the box. -
Create the crew
Give it a name, a short identifier, a time zone for its schedules, and the box it runs on, then name the engine logins it may use as accounts. One box can serve many crews, so a second crew later is just this step again.
-
Connect Slack
Add Klingbar to your Slack workspace once, with Slack's own Add to Slack button; every crew in that workspace uses it.
-
Add a persona
Write its prompt, pick its seat and channel, and give it a task or two with a schedule. Add standing rules for the whole crew — how to speak, what never to touch — while you are there. What a persona is made of.
-
Name the approvers
Add teammates as members and choose who may decide cards. Each approver links their Slack account once, with a one-time code Klingbar's Slack app sends them in a direct message.
-
Run it once, by hand
Start a task from its page and watch the result arrive in Slack: a finding with its report in a thread, a quiet nothing, or a blocked that tells you what to fix — usually a missing credential or a channel the app has not joined yet.
-
Decide the first card
The first time the persona wants to change something, it proposes a card. Approve it in the channel, on your Home tab, or on the web, and read the report of what it did. From here the schedule takes over.
What running a crew looks like
Accept a few learnings
Runs propose one-line lessons as they meet your business's quirks. Approve the true ones and the persona stops repeating the same mistake.
Read the digest
Each persona's weekly digest says what it ran, what it found, and what it proposed, so you can tune a prompt from evidence rather than memory.
Adjust, and roll back
Every save is a version. If a change makes a persona worse, restore the version before it.
Moving, pausing, and retiring
Pause a persona or switch its schedule off from the web or from Slack; running work finishes. Move a crew to another box from its settings: the old box seals its secrets to the new one, and retires its copy once the move completes. Retire a crew and its box stops running it, while its history stays readable on klingbar.com.
Boxes upgrade themselves from signed releases, after a 30-minute wait in case a release is pulled. To choose when instead, pin the box with auto_upgrade = false in its box.toml and upgrade it from its page.
Configuration, prompts, secrets, upgrades, moves, and retirement all happen from the web. The crew's files on the box are rendered by klingbar.com and never edited by hand. What you usually type there is the installer, your engine logins, crew daemon where there is no systemd --user, one crew workspaces for a persona that works in a repository, a sign-in for any command-line tool a persona reads through, and, if you want it, the upgrade pin.
Ready when your invite is
Early access is free: you bring the box and the engine logins. What that means in practice.
Request early access