An AI agent org chart is a configuration, not a diagram.
Here is what Klingbar has instead of a picture. A crew's structure — its personas, what each one watches, where they report, the seats they run on, who approves their changes, and the rules they all follow — is one configuration document on klingbar.com, rendered to your box as crew.toml. Every save is a new version, with a diff and a restore.
Personas, their lanes, and the people above them
A crew is a roster of personas. Each one has a lane: the thing it watches, written in its own prompt, along with its boundaries — what it leaves to another persona, so two of them do not report the same problem twice. Each has a channel it reports in, a seat it runs on (an engine login, a model, and an effort), an optional workspace, and a policy for what it may do without a card.
Above the personas sit the people: one approver list for the crew, whose members decide its cards, and the crew's standing rules, which every persona's prompt carries. That is the whole hierarchy. There are no units and no managers, and no persona directs another; each does its own job and answers to the same approvers. The one place several engines work on a single job is a panel, where several seats propose independently and one evaluator finishes.
- approvers
- Dana and Sam, by Slack user
- revenue
#revenue· renewals and failed charges- support
#support· the inbox; drafts, never sends- logs
#ops· errors after each deploy- standing rules
- Version 7, carried by every prompt
Edited through forms, rendered to your box
All of that is one document on klingbar.com, edited through forms — crew settings, each persona's page, each task's page, and members and approvers. You never write the file. klingbar.com checks the document's structure before saving it — types, references, an effort the engine cannot take — and renders it as crew.toml for the box.
On the box the file is never hand-edited. The daemon's own loader has the last word: it checks every version it receives and either applies it or rejects it and keeps running the last good one. Secrets appear in the document by name and by where to find them, never by value.
[crew] tz = "America/Chicago" approvers = ["U01AAAAAA", "U01BBBBBB"] approval_expiry_hours = 72 max_concurrent_runs = 2 [personas.support] display = "Support" channel = "#support" account = "claude-a" [personas.support.policy] send_ceiling = "draft_only"
An excerpt. The box receives the whole document as crew.toml, one version at a time.
Every save is a version, and the box says what it did with it
Saving any section writes a new version of the whole configuration. The box reports back on each one: applied, with the time, or rejected, with its error in its own words. A rejected version never replaces the one running, so a typo in a schedule costs you one line on a page, not a silent crew.
Each version has a line diff against the one before it, and a restore that saves an older version again as a new one, so history only grows. The crew's standing rules work the same way — versioned, with a diff and a restore, and reported applied by the box. Prompts are versioned on every save too.
- v14
- Applied by
studio-mini· Tue 9:02 AM - v15
- Rejected by
studio-mini: unknown panel "review" onlogs/error-review - v16
- A restore of v14 · applied · Tue 9:06 AM
Six parts, one document
The crew
Its time zone, approver list, card expiry, how many runs may go at once, how far back to catch up after downtime, and when the weekly digests post.
Personas
Display name and icon, channel, seat and standby seat, workspace, policy, and the secrets it may use, by name.
Tasks
A cron schedule or on demand, a timeout, an optional channel of its own, an optional turn ceiling, and an optional panel.
Accounts and engines
The engine logins the box has, each with a name, and where each engine is installed on the box.
Panels
Several seats that propose independently and the evaluator that finishes, for tasks worth a second opinion.
Prompts and rules
Kept beside the document rather than in it: each persona's prompt, each task's prompt, and the crew's standing rules.
When you don't need one
If you have one persona doing one job on a schedule, structure is overhead. Write it a good prompt — what it watches, how it decides, what counts as a finding, and when to stay quiet — give it a channel and a schedule, and stop there.
Structure starts paying for itself when several personas share a crew and their lanes could overlap, when more than one person approves changes, or when you run crews for more than one business from the same box. Below that line it is structure for its own sake, which is a cost with no matching benefit.
Related reading: the guide to an org chart as code, what a persona is made of, and adding a persona to a crew, step by step.
Frequently asked
What is an AI agent org chart?
It is the structure of a group of AI agents: which agents exist, what each one watches, where it reports, and who approves its changes. In Klingbar that structure is a crew's configuration — one versioned document on klingbar.com, rendered to your box as crew.toml — rather than a diagram.
What does a crew's configuration declare?
The crew's time zone, approver list, card expiry, and run limits; each persona's channel, seat, workspace, and policy; each task's schedule and timeout; the engine accounts on the box; and the names of the secrets personas use, with where to find them — never their values.
Do I write crew.toml by hand?
No. You fill in forms on klingbar.com, which check the document before saving it, and the box receives the rendered file. The copy on the box is never hand-edited; the next version would replace it.
What happens when I save a change?
Klingbar saves a new version of the whole document and sends it to your box, which checks it with its own loader. The version then reads applied, or rejected with the box's error, and a rejected version never replaces the last good one. Every version has a line diff against the one before it and a restore, which saves a new version.
Do I need this for a single agent?
No. One persona doing one job needs a good prompt and a schedule, not structure. The structure earns its place when several personas share a crew, when their lanes could overlap, or when more than one person approves changes.
Write the structure down once
Klingbar is free during early access. Start with one persona, and let the structure grow when the crew does.
Request early access