✨ AI Models, Working as One Team

Stop tab-switching between AI models.

  • Copy-pasting responses between five different tabs
  • Re-explaining the project, the roles, and the goal to every model, every day
  • Pinging each AI one by one just to find out what's done
  • Getting polite, agreeable drafts instead of models that challenge each other
  • Playing telephone — asking one AI what it thinks of another's answer, by hand

The AI models you already use — Claude, GPT, Gemini, Kimi, local models — work as one team instead of five separate tabs. Ask the hard question once and watch them read each other's answers, challenge what doesn't hold up, and build on what does. Every reply labeled with its author, every conversation saved on your machine. Stop refereeing chatbots yourself.

🔒 Transcripts & keys stay on your Mac • 🔑 Encrypted OS Keychain • ⚡ Bring your own API keys
Gemini
The login bug is in auth.ts — the token expiry check uses the wrong timezone.
Claude
That would fail for every user, not just one. Checking…
[read_file: src/auth.ts]
Line 47 has no timezone — the real bug is two lines up: the token never refreshes on retry.
Gemini
You're right, I misread the comparison. Refresh-on-retry explains the idle failures too.

Five tabs → one room

Claude GPT Gemini Kimi Local One room every model talks

Why Kaldi Station

Not parallel answers in isolation — one team, reasoning together.

🧠 Deliberation

The models read each other's answers, challenge what doesn't hold up, and build on what does.

So what? You get the answer that survived scrutiny — not the first one a single model handed you.

🏷️ Attribution

Every reply has a name on it. You know exactly who said what.

So what? Judge each answer by who gave it, and route the next task to the right model. Trust the reasoning instead of guessing.

💾 Memory

The room remembers. Full conversation history, on your machine, across sessions.

So what? Pick up tomorrow exactly where you left off — no re-explaining the problem to a blank slate.

Built for the Workflow I Was Drowning In

Kaldi Station started as a personal itch — running a team of AIs across three apps.

I was switching between models all day — Claude in one window, Grok in another, Gemini in a third. Copy-pasting responses between tabs. Re-briefing every agent on context they'd already been given. Assigning roles by hand. Prompting each one to add code and keep building. Half my time went to herding chatbots instead of shipping.

Kaldi Station is the table I wished I had — I didn't want to give them an office tour every day: one room, every model, shared context, everyone knows their lane. Ask once — they read each other, challenge what doesn't hold up, and build on what does.

The fishbowl builds the fishbowl

Kaldi Station isn't just a demo of multi-model deliberation — it's built with it. Real rooms, real transcripts, real commits. A rolling sample:

Non-proprietary excerpts. Lightly trimmed for length.

This homepage

SeanDefine our mission in one paragraph.
KimiThree drafts describe parallel access — that's a commodity. The real product is deliberation: models reading, challenging, and building on each other.
ClaudeKimi's right — parallel access alone is not a moat. Converging on: "a Mac app where the AI models you already use work as one team instead of five separate tabs…"

✅ Shipped — you're reading it. Commit dc698f2.

The audit log spec

Two fishbowl threads designed our audit log — Gemini drafted the minimal schema, Claude added file hashes and redaction rules. The room merged them into one spec, ready for the build team.

✅ Shipped — spec handed to engineering.

The nine-minute stall

Sean watched one seat's approval card stall the whole room for nine minutes. That morning, parked seats stopped stalling the meeting — approvals stack, the room continues, the parked seat re-runs with fresh context.

✅ Shipped — commit 9256d24.

For Builders Who've Outgrown Single-Model Chat

🐛

Developers Debugging Together

One model spots the bug, another checks the file, a third catches the misread — with every claim labeled and evidence attached.

⚖️

Product Teams Weighing Tradeoffs

Put the hard question to the table once and watch the models argue it out — you keep the reasoning that survives.

🤝

Anyone Delegating to AI

When the work matters, you need to trust the result. See who said what and how it held up — then decide.

🔑

Bring Your Own Keys

Use the Claude, GPT, Gemini, and Kimi subscriptions you already pay for. Add keys once — they're encrypted in your system keychain.

Your Data Stays Yours

Your transcripts, memory, and API keys stay local. Prompts still travel to the model providers' APIs — that's how bring-your-own-keys works — but your conversation history never leaves your computer.

🔐 OS Keychain Encryption

Your API keys are stored in your system keychain—the same place macOS stores your passwords. Kaldi never sees them in plain text.

💾 Local Session Storage

All your work—transcripts, memory, context—lives in local files on your computer. No account, no cloud sync, no middleman servers.

🚀 You Own Your History

Export your memory, sessions, and reasoning at any time. No lock-in, no vendor dependency.

Ready to stop refereeing chatbots?

Download Kaldi Station now. No account. No servers. Just AI models working as one team — on your Mac.

Download for Mac

Get Started in 2 Minutes

1

Download & Install
Grab the .dmg and drag Kaldi Station to Applications.

2

Add Your AI Keys
Open Settings. Add your API keys once (stored in your system keychain). Done.

3

Start Thinking with AI
Open a room, ask once, and watch Claude, GPT, Gemini, Kimi, and local models deliberate — every reply labeled.

Download v0.1.0 for macOS

macOS 10.15+ • Universal Binary (Intel & Apple Silicon) • Free and Open Source