Move retry logic out of the client
Same behaviour, its own module, so the agent can rewrite it without touching the request layer.
vibe
~/code/checkout-api/.vibe
Vibe is a desktop Kanban for "vibe coding" projects. Every column you see is a YAML file in a folder you picked. No database in the middle, no telemetry, no analytics, and readable by the coding agent you already use.
Here you're not the product: no ads, no selling your data, no free plan. You have 7 calendar days to ask for your money back, no questions asked.
Same behaviour, its own module, so the agent can rewrite it without touching the request layer.
the same card, on disk
title: Doing order: 3 cards: - title: Move retry logic out of the client tags: [refactor, api] milestone: 0.4.0 files: [] agentCommand: claude -p "implement this card" agentStatus: null
Not values from an about page. Read the columns before the cards: most of what we promise is held by the file format, two by a test that breaks the build, and exactly one by nothing but our own choice.
An automated test in the app's code breaks the build if anyone adds a network call outside the login screen.
No card, description or attachment leaves your machine. The only thing the app sends on its own is your account login, and we publish the whole table, item by item.
No analytics, no automatic crash reports, no version ping. Sending anything at all would have to get past the test first.
A folder of YAML on your disk, with no database in the middle. There's nothing on our side to leak, lose or charge you for.
Each column is a readable YAML file in your folder. Version it with git, open it in your editor, copy it to another machine. Uninstalling the app deletes nothing.
A coding agent creates, moves and updates cards by writing YAML. The board sees the change on disk and redraws itself, live.
We don't store your board, so we don't pay storage for you. The subscription is low and doesn't grow with the size of your project.
Nothing enforces this one. It's the promise we have to defend again at every release.
Two screens: the board and settings. Open it, pick a folder, use it. No workspace to configure, no six-step wizard.
The same claim as a board. Three columns, one card per kind of data, and the column that matters is the last one. Count its cards.
Stays in the folder you picked. No copy of it exists anywhere else.
Attachments and recorded audio too. One YAML file per column, in the folder you picked, readable without us.
Preferences your own system stores. Same for your coding agent's plan usage: read on your machine, shown only to you.
Off until you turn it on, with a notice that says what leaves, where to and when.
Vibe assembles the prompt on your machine and passes it to the CLI you chose. From there its provider's rules apply, not ours. And we'd rather say so than pretend otherwise.
What the app sends on its own, without asking you first.
At sign-in and when you change your password, to our authentication server. Never the board's content.
A second card in this column would mean naming a new exception in the app's principles document and allowlisting it in the test that would otherwise break the build.
One column, three cards: what's already in your hands, no roadmap slide attached.
The same app and the same folder on any machine you work from.
Columns and cards reorganize by dragging, with tags, milestones and file attachments per card.
An interface built to sit open all day next to your editor, in English or Portuguese.
Your data stays yours. That's why there's no free plan: there are 7 calendar days to ask for the full amount back, no lock-in and no cancellation fee.
This site counts visits with a self-hosted, cookie-less analytics script. No personal data, no IP stored. See our privacy page.