What's new

What changed on vibe-coded.ai, newest first.

October 7, 2026 — A monthly call allowance per account

Every account now has a monthly allowance of API calls across all its vibes: at least 500,000 on Free, 900,000 on Pro and 2,000,000 on Pro+. A normal vibe uses a few hundred calls a month, so this only affects runaway or bot traffic. vibe status --plan shows where you stand, and if the allowance runs out your vibes pause with a clear message until the month resets or you upgrade. Details in Plans & Billing.

October 6, 2026 — Plans renamed

The $9 plan is now called Pro and the $20 plan is Pro+. Prices and limits are unchanged. Every plan builds with your own coding agent, so the old name, BYOV, no longer set the $9 plan apart; the plans differ in storage and limits.

October 5, 2026 — Fewer dead ends when you sign in

  • Adding a vibe as a connector in claude.ai or Claude Desktop now works from a signed-out browser: sign in when asked, and you return to the approval page. Before, you were left on your account page and had to start again.
  • vibe login works straight after you create an account. Approving the CLI could fail with a security error for about an hour after a new sign-in.
  • If a Google or GitHub sign-in fails, you land on the login page with the reason, not a page of raw data.
  • www.vibe-coded.ai now redirects to vibe-coded.ai.

October 4, 2026 — Templates updated

Added delete methods to the vibe example templates.

October 1, 2026 — Simplified plans

Simplified plans to focus on imported and freshly built vibes.

October 1, 2026 — Preview has its own data

Preview and production now keep separate storage: key-value data, the SQL database and files. A preview starts with empty storage, so test records you add there never reach production, and vibe publish deploys your code without copying any data. If your worker creates its own tables (CREATE TABLE IF NOT EXISTS, as the templates do), nothing changes for you. Webhooks and email sent from a preview are still real.

October 1, 2026 — Connect to vibes shared with you

If someone shares a vibe with you, run vibe connect <owner>/<slug> to add it to Claude Code. The connection acts with your role (viewers read, writers edit) and stops as soon as the owner removes your access. Your CLI login itself now works only on vibes you own. See Sharing & Access.

September 30, 2026 — Previews no longer touch production

Until today, every vibe preview also redeployed your production code. Now a preview builds and runs only on the preview address, and vibe publish deploys that exact tested build to production. If a publish can't finish, the message says whether production changed. Your data is still shared between preview and production for now, so test writes on the preview show up in production; separating the data is next. Update: since October 1, preview has its own data too (see above).

September 30, 2026 — Public vibes anyone can read, only you can edit

A new interaction policy, “Anyone can read; only invited people can edit”, lets you publish a reference server, catalogue or lookup that anyone can open and any AI can query, even without an account, while only you and people you invite as writers can change it. Writes from everyone else are refused, and they never see your secrets.

Choose it in the vibe's settings on your account page. If the vibe was built before today, run vibe preview and vibe publish once after switching. The existing “Anyone” policy is unchanged and still lets visitors write, for things like guestbooks. See Sharing & Access.

September 29, 2026 — Errors you can act on

  • A failed build now shows the bundler's error with file, line and column in vibe logs, and vibe publish refuses a failed preview straight away and tells you what to run.
  • When a tool fails, you see the error message (with credentials and paths redacted). Visitors see only a reference id.
  • Secrets created before a vibe's first build are kept and applied on the next preview. Rotations and deletes reach a running worker within seconds (allow up to about 30).
  • The CLI tells you once a day when a newer version is available. VIBE_NO_UPDATE_CHECK=1 turns that off.

Re-run the install line to update (this release adds the update notice, so it's the last time you'll need to check by hand).

September 29, 2026 — Check a private site from the CLI, and clearer failures

We ran blind agents through the whole CLI, from building to updating, sharing and breaking things on purpose, and fixed what tripped them up:

  • vibe fetch <path> fetches a page or asset from your vibe as the owner, so you can check a private site without a browser.
  • vibe status shows which build is live on preview and production.
  • vibe <command> --help prints that command's help instead of running it.
  • Changes that have to be made on the website (visibility, sharing) now exit with an error from the CLI, with the link to the right panel.
  • vibe preview uploads and prunes in one step, so a file you deleted stops being served right away. Having both worker.js and worker.ts is refused.
  • Secrets now reach your worker. Until this week, adding or rotating one never took effect.
  • A vibe without a build step no longer serves its worker source, config files or notes such as README.md.

Re-run the install line to update.

September 27, 2026 — Connect a vibe to Claude Code with one command

Run vibe connect in your vibe's folder. It creates a token that can only call that vibe's tools, and adds the vibe to Claude Code for all your projects. There's no browser step, so your coding agent can finish the whole job, from building the vibe to connecting it, while you're away. The tools load in your next Claude Code session.

vibe connect

Run it again to renew the token (it lasts until your CLI login expires, 30 days after vibe login), or use vibe connect --revoke to remove access. claude.ai and Claude Desktop still connect through Settings → Connectors. Re-run the install line to update.

September 27, 2026 — Start blank, and check your tools with one command

New templates: tools is a blank data vibe (notes your AI can add, list and update) to rename into whatever you track; tools-sql is the same on SQL for BYOV and Pro; site is a static page with no backend. vibe templates lists all six.

vibe call runs one tool on your live vibe as you, with no browser or connector, so you or your agent can check a published vibe works before connecting it:

vibe call add_note '{"text":"first note"}'
vibe call list_notes

Also: vibe init <slug> --adopt picks up a vibe you already own in a new folder, and vibe dev now serves at http://127.0.0.1:8787 and refuses to start if another program holds the port. Re-run the install line to update.

September 27, 2026 — New items show up in the list sooner

In vibes started from the tracker, log or journal template, an item your AI had just added could be missing from the list for up to half a minute. Add something, ask what's open, and it wasn't there yet. The templates now remember recent writes, so a new item normally shows up in the next list. In the rare case it doesn't, it appears within a minute, as before.

Vibes you created from a template before September 27 keep the old worker. To get the fix, ask your agent: “apply the skill's rememberWrite and loadAll pattern to this vibe,” then run vibe preview and vibe publish. Re-run the install line first so your agent has the updated skill.

September 23, 2026 — Sign in to the CLI with Google or GitHub

If you created your account with Google or GitHub, vibe login couldn't sign you in: it only asked for a password, and those accounts don't have one. Now it opens your browser instead. Sign in the way you signed up, check the code on the page matches the one in your terminal, and approve. Your coding agent can run it for you and hand you the link.

curl -fsSL https://vibe-coded.ai/install.sh | sh
vibe login

Already installed the skill? Run the install line again to get the new version. Email-and-password accounts can still use vibe login you@example.com.

Also fixed: vibe preview no longer uploads the local database that vibe dev keeps on your machine.

September 14, 2026 — Clear answers when a feature needs a paid plan

When something isn't included in your plan, the CLI now says what happened, which plan includes it and what it costs, and the exact sentence to give your agent — instead of a bare error. The signup form lists every password rule up front, and deleting an account no longer shows internal errors.

September 7–8, 2026 — claude.ai connectors that just work

Adding a vibe as a custom connector in claude.ai or Claude Desktop now signs in and lists your tools the first time. Conversations no longer drop the connection between turns, and people you share a vibe with as viewers can use its read-only tools.

September 5, 2026 — Sign up is open

No waitlist and no invite code. Create an account, install the skill, and build with the AI you already use — Claude Code, Cursor, Codex CLI, Gemini CLI and others. Start with the quickstart.