vibe-workbench

Vibe

Vibe is Vibecade's concrete tool for vibe-coded systems: a hybrid specification language and future runtime for declaring agentic infrastructure as code.

This repository, C:\vibe, is the new active Vibe home. The older C:\Hive\vibe repository was used as a reference and transfer source, but it is no longer the active workstream.

The spec is intentionally fluid. Naming, syntax, backend choice, and the split between parser, runtime, providers, generated artifacts, and long-horizon agents should change as the repo learns.

Status

C:\vibe has been inflated from the old reference repo into a working monorepo:

• packages/language contains the current TypeScript/Langium parser, dispatcher, resolver, provider shims, self-plan extractor, and tests.
• packages/vscode-extension contains the thin VS Code extension scaffold.
• examples/vibe-self.vibe is the current self-describing source for Vibe's near-term work.
• docs/superpowers/ contains the transferred specs, plans, and research notes.
• go/ contains a provisional Go runtime spike. It is source-only until a Go toolchain is available.

Commands

pnpm install
pnpm run self:plan
pnpm test
pnpm run build
pnpm run check
pnpm run vibe:continue
pnpm run vibe:doctor
pnpm run vibe:lanes
pnpm run vibe:graph
pnpm run vibe:serve

pnpm run self:plan extracts a JSON self-plan from examples/vibe-self.vibe into docs/examples/vibe-self-plan.json. pnpm run vibe:graph derives docs/examples/vibe-lanes.mmd from that JSON. pnpm run vibe:serve hosts a local admin dashboard at http://127.0.0.1:8787. pnpm run vibe:continue prints the compact resume protocol for future Codex, Claude Code, or human sessions.

The cross-session resume protocol is tracked in docs/continue.md. Bootstrap setup work is tracked in docs/bootstrap-todos.md. The local CLI and hosting shape is tracked in docs/local-toolkit.md. VS Code agent workflow notes are tracked in docs/vscode-agent-workflow.md.

VS Code Agent Loop

The workspace now includes first-pass integration points for OpenAI Codex and Anthropic Claude Code in VS Code:

• AGENTS.md gives Codex repo-local operating guidance.
• CLAUDE.md gives Claude Code repo-local operating guidance.
• .vscode/extensions.json recommends the Codex and Claude Code extensions.
• .vscode/launch.json starts the local Vibe VS Code extension in an Extension Development Host.
• .vscode/tasks.json exposes Vibe snapshot, lane, self-plan, and full-check tasks.
• packages/vscode-extension contributes Vibe: Admin Workspace, a command palette picker that runs the same Vibe Workbench checks from a terminal.
• The extension also contributes a Vibe tree in Explorer, sourced from .vibe/state.json when present and falling back to docs/examples/vibe-self-plan.json.
• Vibe Now commands can create .vibe/project.vibe, parse the active .vibe file into .vibe/state.json, show a project summary, generate .vibe/generated/AGENTS.preview.md, and create an opinionated GameSpree/Pawfall contract.

Bootstrap Loop

examples/vibe-self.vibe
  -> packages/language self-plan extractor
  -> docs/examples/vibe-self-plan.json
  -> human/agent execution
  -> updated .vibe source

This is the first dogfood loop. It is not final self-hosting. Long-horizon agents are an eventual execution target for Vibe lanes, not a dependency of the initial setup.

Vibe also needs to know where a lane is being managed from. A lane may be started or supervised from a local desktop, phone, web session, IDE, GitHub, or cloud agent, but the contract should stay repo-grounded: source, branch, handoff, write scope, validation gate, and human approval.

Repo Layout

vibe/
├── docs/
│   ├── examples/
│   ├── fresh-start.md
│   └── superpowers/{plans,research,specs}/
├── examples/
├── go/
├── packages/
│   ├── language/
│   └── vscode-extension/
├── package.json
├── pnpm-workspace.yaml
└── tsconfig.base.json