vibeos

VibeOS — Autonomous Development Engine

v2.2.0 — Evidence Recall Upgrade (2026-04-24)

This update adds a local, source-cited evidence recall utility. VibeOS can now build a compact index of work orders, audits, gate manifests, skills, session state, baselines, and checkpoints, then return bounded excerpts with citations instead of rereading large context bundles. It uses a generated .vibeos/cache/ file, has no network dependency, and does not add any external memory service.

v2.1.0 — Advanced Governance Upgrade (2026-04-03)

This update makes VibeOS smarter about how it reviews its own work. It can now check code quality while it's still building (instead of waiting until everything is saved), ask a second AI (Codex) to independently verify what it built, and automatically prevent work orders from growing too large or messy. It also blocks attempts to skip safety checks and protects test files from being weakened during implementation. If you're running multiple builds in parallel, VibeOS now enforces clear boundaries so they don't step on each other. Say "Upgrade VibeOS" inside any active session to get these improvements.

v2.0.0 — Verification Integrity Upgrade (2026-03-16)

This update came after VibeOS ran a fully autonomous 8-hour build session — 156 work orders, 6,175 passing tests, zero human intervention. Running at that scale revealed places where the system needed to be more careful about verifying its own work: catching stale code reviews, validating that the front-end and back-end agree with each other, remembering issues between sessions, and making sure old problems don't get quietly ignored forever. The system now verifies its own verification.

VibeOS turns Claude Code, Cursor, and Codex into a hands-on development partner. You do not need to learn a complicated workflow to get started. Open your project in the runtime you prefer, describe what you want in plain English, and VibeOS figures out whether to discover, plan, audit, explain, or keep building.

Think of it like this:

• You say what you want
• VibeOS asks follow-up questions only when it truly needs them
• VibeOS creates the plan, writes the code, runs checks, and keeps you updated
• When VibeOS needs your input, it explains the options in simple terms, gives pros and cons, and recommends what to do

You can learn a few commands later if you want, but the normal way to use VibeOS is to talk to it naturally.

Start Here

If you are not technical, this is the only part you really need:

1. Install VibeOS.
2. Open Claude Code, Cursor, or Codex inside your project.
3. Say what you want, like:
   • "I want to build a task management app"
   • "Help me understand this codebase"
   • "Continue building"
   • "What's the status?"
   • "Give me a project status"

That is enough to get started.

How It Feels To Use

VibeOS is voice-driven and conversation-first. In practice, that means:

• You do not need to remember slash commands to use it
• You do not need to know GitHub pull requests, branching, or formal project management
• You do not need to tell it which internal mode to use
• You can just type what you want as if you were talking to a strong technical teammate

Examples:

You say	VibeOS does
"I want to build a booking app for dog groomers"	Starts discovery and helps shape the product
"Build this as a competition-grade enterprise MVP"	Creates a compact VibOS Comp mission brief
"Make a plan for this"	Creates a phased development plan
"Keep going"	Continues the build loop
"What's the status?"	Gives a tactical update on the current or most recent session
"Give me a project status"	Gives an executive big-picture briefing on the whole project
"Go autonomous"	Puts VibeOS back into full autonomous session mode
"Audit this session"	Reviews everything completed in the current or last build session
"Check the code quality"	Runs quality gates and explains the result
"What is ratcheting?"	Explains the concept in plain English
"Help me understand this codebase"	Audits the project and maps what exists

What It Does