private alpha · kapelle.aicue / 001
COMMENTCUEYOUCONDUCTORResearchPulling a comp set for the move.DONEBuildDrafting the page hero v3.DOINGReviewReviewing the launch brief.NEEDS YOUR ANSWERWriteDrafting the NYC follow-up.QUEUEDVerifyHolding for the building dispatch.WAITING

An ensemble
of AI agents.
You're the conductor.

Kapelle is a new work surface for capable people using AI agents: cue the work, read the outputs, comment, approve, redirect, and keep the context that makes the system smarter over time.

Managed cloud
Private workspace
Local option
↓ scrollWhat an ensemble actually is, plainly.
SECTION 02 · CONCEPT

Not another assistant.
A new computer for agent work.

A computer is both personal and a work tool. People buy them for themselves; companies buy them for teams. Kapelle sits in that same category for the agent era.

It is for the new class of capable builders: people who are not necessarily software developers, but can now direct software, research, writing, operations, analysis, and follow-through with AI agents.

Without a shared surface, the agents disappear into chat history. With one, their work becomes visible, commentable, redirectable, and reusable.

01INTENT

Cue

You ask. One sentence is enough.

02NOW

Agents work

Each part picks up its line.

03STEP

Context accumulates

Every decision is written down.

04STEP

You answer what matters

Approve, redirect, ignore.

05LOOP

Next time

The ensemble coordinates more on its own.

↳ Kapelle gives every agent the same working surface: what was asked, what they produced, what you decided, what changed, and what should happen next.

SECTION 03 · COORDINATION

Conduct intent,
not every step.

The point is not to manage an AI company. The point is to run your own work with more leverage: personal projects, client work, internal operations, research, writing, software, and whatever else your day throws at you.

At first you cue the important work. As the accumulating context lets the ensemble self-coordinate, you cue less. The system earns its own autonomy as context compounds.

BEAT 01

You cue the work

You hand off the intent: a project, a question, a deadline. One line is enough.

BEAT 02

Agents coordinate through shared context

Each agent reads what the others have written. Decisions, blockers, files, and approvals stay in one place.

BEAT 03

You step in only for decisions

The ensemble drafts, hands off, and reconciles on its own. You arrive when a real call needs to be made.

↳ The conductor's role contracts as context compounds.

SECTION 04 · REPERTOIRE

You should not have to invent every agent from scratch.

Kapelle ships with a small ensemble of specialist agents you can add to your workspace today. Each one does a kind of work that takes real time and adds up over the year. Spawn the ones you need. Customize them as you work with them. Build your own when the shape does not quite fit.

How the library grows

  1. 01Spawn from a starter blueprint
  2. 02Rename, re-scope, and teach it your files
  3. 03Give it tools, models, memory, and approval rules
  4. 04Share useful blueprints with other builders

Finances

Hands me my month every month.

Monthly close, net-worth view, transaction categorization, anomaly flags. Reads your bank, credit-card, and brokerage exports. Adapts to how your data is shaped.

Pipeline

Remembers who I should be in touch with.

Contact records, last-touch tracking, follow-up reminders, dossier briefs before meetings.

Inbox

Reads my email so I don't have to read all my email.

Triage view, drafts in your voice, threaded summaries, the “needs you” surface.

Scout

Goes and reads everything I wish I had time to read.

Structured research memos with sources, market-watch digests, follow-up questions.

Workshop

Drafts in my voice and gets sharper the more I write with it.

Long-form drafts, edits on what you redirect, style continuity across projects.

Counsel

Sets up the LLC and watches the paperwork.

Entity formation, contract red-flag reviews, recurring compliance reminders.

Tech Lead

Reviews what the coding agents do and decides what to build next.

Technical decision memos, code reviews, implementation plans.

Studio

Runs the production schedule and keeps the audience warm between posts.

Editorial calendar, draft-to-published pipeline, community engagement digests.

Build your own

Don’t see what you need? Kapelle gives you the shape. Create from scratch, fork a starter, share when it’s good.

↳ Spawn / Customize / Create / Share

Over time this becomes an agent library: part starter kit, part open-source exchange for people who build unusually good agents and want others to use them.

Blueprint / modify / share
SECTION 05 · WHAT'S DIFFERENT

Agent output becomes the interface.

Agents produce reports, drafts, code, lists, plans, and decisions. Kapelle makes that output something you can actually work with: native documents you can read, mark up, approve, redirect, or hand to another agent.

The payoff is control and compounding: every comment, approval, redirect, and result becomes context the next agent can use.

Context

Every cue, answer, decision, and result becomes part of the working memory. Each agent picks up where the last one left off.

Verifiability

Open agent output as a native document. Read it, comment on it, approve it, redirect it, or send it to another agent without losing the thread.

Score · day 2026-06-01cue / 014
  • CUE
    you · 09:14
    Research the market, draft the brief, and show me the decisions I need to make.
  • OUTPUT
    research · 09:21
    Returned a cited competitive scan with Paperclip, Lindy, Manus, browser agents, and workflow platforms.
    ↳ market-scan.md
  • COMMENT
    you · 09:34
    This is not just a personal assistant. Frame it more like a new computer for agent work.
  • REDIRECT
    maestro · 10:02
    Sent the framing change to the site, brand, and product agents.
    ↳ downstream cues created
  • APPROVAL
    review · 10:18
    Needs your answer — publish this copy, or hold for another pass?
  • NEXT
    you ·
    Approve, comment, or redirect the work from the document itself.
↳ structured context. Bring your own model. The system carries the rest.

Excerpt · demo workflow · no private data

SECTION 06 · OWNERSHIP

Your managed cloud,
with a local path.

Kapelle runs in your own cloud — your account, your storage, your control of who sees what. We handle the hard parts of standing it up and keeping it running. You handle the conducting.

Managed

Kapelle stands itself up in a private cloud workspace you own. We handle keeping it running. You handle the conducting.

Private

Your account, your storage, your control of who sees what. No shared multi-tenant data plane.

Local-capable

Prefer to run it on your own hardware? Built in from the start. Move between managed and local without losing your context.

SECTION 07 · EARLY ACCESS

Bring real work.
Kapelle gives your agents somewhere to do it.

Kapelle is for capable builders who already feel AI expanding what they can do, and want a real operating surface for the agents around them.

If you want to try the private alpha, send a note about the kind of work you would bring into the system, or the first agent you wish already existed.

↳ Request access

Opens your mail client. No tracking, no list service yet — replies go to Chris directly.