vibey-chat-driverlisted
Install: claude install-skill the-vibey-project/vibey
# Driving vibey from Chat
`vibey` is a queue-based, six-phase conductor for autonomous software delivery (`INTAKE → DESIGN → [VISUAL_DESIGN] → BUILD ⇄ REVIEW → optional DEPLOY`). You do not leave your chat client (Claude Code, Codex, Claude Desktop, Cursor, VS Code, or the krypton desktop chat) to use it: `vibey mcp` exposes the hub's operator surface as Model Context Protocol (MCP) tools, and `vibey connect` registers that server across your installed clients in one step.
---
## 1. One-Command Setup (`vibey connect`)
Register `vibey mcp` with your host clients:
```bash
vibey connect # shows the plan (create / update / unchanged), backs up existing files, merges idempotently
vibey connect --yes # non-interactive approval
vibey connect --list # list supported client IDs (claude_code, claude_desktop, codex, cursor, vscode, gemini_cli)
```
Or install via the Claude Code plugin marketplace:
```text
/plugin marketplace add the-vibey-project/vibey
/plugin install vibey@the-vibey-project
```
When the first MCP tool call runs, `vibey mcp` connects to the local hub (`<state_dir>/serving.json`) and automatically runs `vibey hub start` if no hub is serving yet.
---
## 2. Security Boundary: The Scoped Agent Principal
When a host LLM calls `vibey mcp`, it authenticates with `<state_dir>/agent.token`, **never** the host's owner token. The hub assigns `HubPrincipal(name="agent")` bounded by `[hub] agent_scopes` in `vibey.toml`:
- **Default ceiling:** `["view", "an