VTK://FIRST-RUN//LOCAL-COMMAND-DECK

Build your first usage runbook

Choose how VibeTRACKER starts, declare the source rails you use, and inspect every command before it reaches your terminal.

READY / LOCALnothing runs on this page

COMMANDS08manual pasteSOURCE RAILS043 usage / 1 localEVIDENCEARMEDlocal receiptRELAYDRY RUN0 page writes

01 Choose the start mode

02 Select source rails

Selections prepare discovery commands. They do not connect an account.

Hosted APIsUsage and spend from authenticated AI providers.USAGECreator toolsImage, video, music, audio, and 3D workflows.USAGECoding CLIsDeveloper tools with source-labelled local evidence.USAGELocal stackDiscover Ollama, LM Studio, ComfyUI, and loopback tools.LOCAL

03 Arm proof gates

Secret boundaryPrompts, outputs, and credentials never enter the runbook.LOCKEDLocal sync receiptWrite an inspectable receipt beside the local ledger.ARMEDC0VIBE dry runPreview the aggregate bundle without publishing it.DRY RUN

FIRST MINUTE / VERIFIED ORDER

What the runbook will ask you to review

VIBERS UNITE / AFTER REVIEW

00
Terminal opens the GUI
The ASCII CLI remains visible inside the local wizard so users never lose command-line confidence.
LOCAL
01
Connect only what you trust
OAuth, MCP, API keys, local logs, and manual ledgers are labelled by source before any scan runs.
CONSENT
02
Watch the scan prove itself
Provider cards fill with branded feedback while audit rails separate usage, estimates, and trust signals.
AUDIT
03
Review before C0VIBE
Vibers Unite at c0vibe.app only after the dry-run confirms what leaves the machine.
PREVIEW