vibemind.club
VibeMind
Join the VibeMind club.

A brain for your AI workflow that keeps getting smarter, and mission control to run it.

Plan in one place. Build in many. Lose sight of nothing.

VibeMind · the cockpit, first boot
The VibeMind cockpit on first boot: Thalamus in the chat pane waiting for sign-in, the heads-up to-do board, and the work tree panel

The cockpit, first boot: Thalamus, the work tree, the board. Real capture, no retouching.

∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
What is it, exactly?

Three things, plainly.

A brain: the curated memory and working rules your AI agents read the moment they start, so they boot already knowing your project. A machine: the coordination layer that runs several agents side by side and keeps them off each other's files. And an app that packages both, for people who do not want to live inside a code editor.

The free version

A public GitHub repository. Really.

Clone the repo, paste one block into your project's CLAUDE.md. That's the whole install: Thalamus greets you and runs the brain, an ASCII status board keeps score, and the working guidelines we compile from the sources we watch come baked in.

The full version

An app, and here is exactly what it is made of.

Built openly on VSCodium, running the genuine Claude Code extension, unmodified; you sign in directly with Anthropic, and VibeMind never sees, holds, or proxies your login. Around it sits the machine: the Board for every conversation and agent, lanes that keep parallel work from colliding, and a living brain kept current for you.

Team

Shared org memory.

One brain every seat inherits: the decisions, rules, and instincts your whole team works from. Coming later.

Before you join, the honest requirements
  • You bring your own Claude account. A paid Claude plan or an API key; the free Claude tier has no Claude Code access.
  • The app is Windows-first today.
  • It works on your existing projects, as they are. No restructuring, no migration.
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
The machine, made beautiful

Thalamus, the Board, the work tree, the Mind. One screen.

You talk to Thalamus like a person. Your builds run in isolated lanes, land on the Board, and nothing you started ever scrolls away.

VibeMind · Thalamus, mid-conversation
Real capture of a Thalamus conversation: the user asks for a motto to become a landing page, and Thalamus dispatches the build and points to the Board

A real Thalamus conversation: think it out loud, say go, watch the build land on the Board.

Dashboard captures
On their way.
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
Run more than one

Three agents. One repo. Today, it just works.

Once you stop repeating yourself, you can run several ideas at once instead of one at a time. Every agent works in its own lane, a claimed set of files, so lanes make collisions impossible by construction.

audited run · 2026-07-07 · three sessions on one repo, started within 2 seconds, 44 minutes side by side
0
file collisions
0
merge conflicts in code
33
new tests, all green after merge
0
times the shared repo went red
Before · without VibeMind
Real capture: an agent detects another process writing the file it is editing and stops to ask how to proceed

Real capture of life without lanes. This is not VibeMind. The agent notices something else writing the very file it is editing and stops dead to ask how to proceed.

After: lanes, same repo, three at once
“I pushed master only up to my green commit... Their window owns the fix.

During its own pre-push checks, one agent caught a failing test that a sibling agent had introduced, held that change back, and pushed only its own verified work. Nobody asked it to. The agents police each other.

raw transcript
Transcript capture: the agent explains it pushed master only up to its own green commit, leaving the sibling's failing change for that window to fix and push
Before merging, each agent first checks whether a sibling moved the code underneath it.

Same run, another agent. Its commit is clean and ready, and its first move is still to fetch and check what the other two did in the meantime. That reflex is the discipline, built in.

raw transcript
Transcript capture: an agent with a clean commit checks whether the sibling lane merged anything before merging to master
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
Measured, not marketed

Structure you barely pay for.
Disorganization is the expensive thing.

We ran 69 audited tests on real open-source codebases and spent $103.97 of real money to measure this. The short version: the organization layer adds almost nothing to your bill. The expensive thing is the disorganized default most people already run.

Your setup
// a feature, a fix, a refactor, real work, not one-line edits
6 / day
// in these tests a task was a real small feature, roughly three minutes of agent time; the large-feature test ran about sixteen
Your estimate
The machinery's own footprint about 1.2% of the clock · 408 ms of setup and merge steps, timed by an independent auditor · 92.6% of billed tokens are cache reads, the discounted kind · 0 blocking rate-limit hits in 41 runs
 
 
The bonus 
The money 
Weigh a price against the hours back
$ / mo
// pricing is not set yet. Type any number to weigh it against the time.
Enter a price to weigh it against the time.
What in your estimate is measured, and what is projected

Every number here comes from real timed runs of real coding tasks, reported as ranges rather than single points. The dollars come out about the same as doing your tasks one at a time; what changes is how fast and how orderly the day runs. Full methodology in the receipts.

One long chat doing everything, one task after another
the baseline: slowest, and the wall time swings wildly
Several chats on one folder (what most people try first)
about half again more money and the most errors of anything we measured
Isolated lanes (what VibeMind runs)
about twice as fast, the same tokens as one-at-a-time, and nothing can collide, by construction

Medium codebase, five runs each, middle result reported. Every number, every caveat, every blank: on the receipts page.

Even the smartest models do not organize work this way on their own.

We handed the whole job to top-tier models nine times and watched what they chose. Not one of them split the work into parallel lanes or hired cheaper workers for the simple parts. Every one reached for the slow, expensive shape by default. The best strategy has to be encoded. The machine is that encoding.

Before our final test ran, this engine predicted its result within 8 percent. Full methodology on the receipts page.

∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
The hostage conversation

The thread you are scared to close.

You know the one. Weeks of decisions live in a single chat: every architectural call, every dead end you already ruled out. It is the only record of how you got here, so you keep it open. And it degrades: the context fills, the answers wander, every turn costs more than the last.

● untitled-session-4
you · week 1auth redirects to /login on expiry. locked in.
you · week 4no, we ruled that layout out weeks ago. scroll up.
agentCould you restate that decision? I no longer have the earlier context.
context 187k / 200k41 days open

The brain livesoutside the transcript.

VibeMind keeps decisions, rules, and project facts in durable memory, outside any chat. Closing a conversation costs nothing. A fresh one reads the brain and boots fully caught up.

Your chat is not your memory.
Close the tab. The brain remembers.
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
It is your job either way

Who carries the weight?

Nobody else keeps your project honest. The difference is how many times you have to say it: every single time, or once.

Today: you, telling it every single time
  • Explain the project rules. Again. To every fresh session.
  • Re-state last week's decisions to an agent that was not there.
  • Repeat the deploy steps to every new agent you spawn.
  • Tell each one what is already in flight so they do not collide.
  • Ask what actually got done. Every time. Then go check.
  • Walk every session through the TODO, or watch it go stale.
  • Ask for a report, file it yourself, then do it all again tomorrow.
With VibeMind
  • 01Still your project.
  • 02Still your rules.
  • 03Still your call.
Say it once. The brain carries it to every session and every agent. Reports land on their own, lanes track themselves, questions queue up for you. You still run the show. You just stop repeating yourself.
Still your project. Still your call. The brain carries the bookkeeping.
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
The living changelog

The ground keeps moving.
The brain keeps up.

Anthropic ships new models, new features, new policies, new prices. You know you are not keeping up with all of it. You could. It is easier to let the club do it. The brain tracks the whole ecosystem, every claim linked back to its source, and hands you the new rule while it still matters.

v2026.27models · policy
They changedAn export-control directive suspended API access to two frontier Claude models in mid-June, days after their launch. Access was restored about three weeks later.
So the brain nownever assumes a top model is permanently available. Model routing carries a fallback chain: when the first choice disappears, work degrades to the next-best model instead of stopping.
v2026.27models · cost
They changedClaude Sonnet 5 launched June 30 as the new default model. Its tokenizer produces roughly 30 percent more tokens for the same text, and its introductory pricing ends August 31.
So the brain nowrecalculates how much conversation fits in one working session under the new tokenizer, and logs August 31 as a fixed date to revisit cost decisions before the price changes.
v2026.27features
They changedClaude Code made subagents run in the background by default, so Claude keeps working while they run. Parallel agent work went from an opt-in to the default behavior.
So the brain nowtreats collision protection as the baseline, not the edge case: every parallel task gets its own isolated copy of the project, so two agents writing the same file is impossible by construction.
Your brain stays current. That is the club.
Read the full changelog: 42 sourced entries, back to 2024
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
The club

Three ways in.

Start free, in bare Claude Code, and feel the difference. Step up to the whole machine when you are ready.

Free
The club, free forever.
  • A starter brain that works in bare Claude Code.
  • Thalamus, the front desk: it greets you and runs the brain.
  • A handful of commands to run with.
  • A simple ASCII status board.
  • Five-minute setup.
You also get the intelligence we run on: we parse Anthropic's releases, docs, and guidance, plus the best community sources, and turn them into working guidelines as things change. Members get the notes.
No card, no waitlist.
Clone it and go.
Founding Pro
The whole machine.
  • The app, for people who do not live in an editor.
  • The Board: every lane, report, and question in one view.
  • Parallel lanes that cannot collide on the same file, by construction.
  • Persisted reports that land and stay.
  • The needs-input queue, so nothing waits on a lost message.
  • The living brain, always current.
Founding pricing, locked for life, for the first 100 on the list.
You bring your own Claude access. We never see your login.
Team
Shared org memory.
  • One brain your whole team reads and writes.
  • Decisions, rules, and instincts shared across everyone.
  • The bookkeeping, handled at team scale.
Coming later
∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿∿
Not just us

The homework is sitting right in front of you.

None of this is a secret. Anthropic prints it on the usage dashboard and writes it in the docs, freely available to anyone. Reading it is easy. Doing something with it, every session, while also building your product, is the hard part.

Claude Code usage dashboard
“54% of your usage was at >150k context – Longer sessions are more expensive even when cached. /compact mid-task, /clear when switching to new tasks.”
Anthropic, your Claude Code usage dashboard
Claude Code usage dashboard
“33% of your usage came from subagent-heavy sessions – Each subagent runs its own requests. Be deliberate about spawning them – and consider configuring a cheaper model for simpler subagents.”
Anthropic, your Claude Code usage dashboard
Anthropic docs · Manage costs effectively
“Use /clear to start fresh when switching to unrelated work. Stale context wastes tokens on every subsequent message.”
Anthropic docs · Create custom subagents
“Control costs by routing tasks to faster, cheaper models like Haiku.”

The club is us doing something with it, rapidly, as it lands: the guidance becomes working defaults in the brain, and the machine runs them so you do not have to remember to.

Even their own dashboard tells you to work like this.
VibeMind just works like this.