A veterinary duo built what coding agents lacked: structural vision, durable intent, and a mouth that posts — with daily proof and a list of what still fails.loct impact · aicx search · /vc grok send · vc justdo
vc-frame is the terminal you sit in. vc-server is the same run list in a browser.
curl -fsSL https://vibecrafted.io/install.sh | bash One installer. Six binaries. They all read and write the same directory.
The runtime and the launchers. vibecrafted <skill> <agent> dispatches real work to claude, codex, gemini or junie, records every run in the control plane, and settles it as f / x / n with receipts — report, transcript, seal.
Structural perception. Repo map, dependency slices, consumers, blast radius, dead code — the map an agent reads before it touches your code.
Parses agent transcripts — Claude, Codex, Gemini — into a searchable intent store. What was decided, by whom, and why: retrievable, not folklore.
The operator terminal (a hard fork of Zellij): session rail, live-run chips, command composer, paste stack. Where you watch the fleet work — and interrupt it.
A read-only browser projection of the same control plane the CLI writes: live runs, lifecycle decisions, transcripts, scaffold review. Leptos SSR + axum. It observes; it cannot mutate your repo.
Agency on your Slack, self-hosted. Agents post, reply, react, DM and hand off to each other in bounded threads — under operator-controlled scopes, with tokens that never leave your side.
Generation gets you a diff. It does not get you sight, memory, a mouth, or a verdict. That is the hangover — the session that cannot say what it touched, why, or whether it shipped. Here is what we keep finding in agent-run repos.
loct impact never ran. Blast radius is a vibe. Deletes land on importers nobody mapped. Structure is guessed after the cut, not before.
Intent dies at compaction. The next session re-derives what aicx would have kept as typed memory. Chat residue is not a handoff.
Status lives in Slack paste. Tokens in the browser. /vc never sent. The projector is treated as the log.
Green CI, red product. Gates skipped, receipts missing, ship as a feeling. Sprawczość is a list of what still fails — not a badge.
The vocabulary can stay vivid, as long as the system remains inspectable: context before edits, evidence after runs, and a release surface that says what is still uncertain.
Models drift when they write into a repo blind. Structural maps give the session landmarks before the agent touches a file.
Code generation is noisy. The Marbles loop gives that noise a place to show up: small loops, counterexamples, and visible unresolved work.
Structured Human-AI collaborative engineering. The craft is in the handoff: humans keep scope, taste, and irreversible decisions; agents do fieldwork with evidence attached.
Without a board
The next session may inherit a diff, but not the reason behind it. The repo has changes; the work has no memory.
A green build starts to feel like proof. It is useful signal, but not enough to know whether the product is safe.
Artifacts collect in comments, branches, notes, and screenshots. A future agent can see pieces, but not the shape.
With a board
Scope, owner, evidence, and next action sit on the same surface before the agent starts cutting.
Reports and artifacts stay attached to the repo, so the next session can continue from evidence instead of mood.
The board does not declare victory. It shows what landed, what moved, and what still asks for a decision.
05 PHASES
06 OPERATORS
01 SHARED BOARD
00 LOST CONTEXT
Five phases, four cuts of the same truth. Loctree maps before the edit. Aicx remembers after compaction. Agents ship under gates. vc-slack is the mouth — Slack is a projector. Marbles settle only what those four already made true. Green CI is not a product verdict.
read · map before the cut
write · agents deliver
read · falsify the write
write · marbles ⬆ polarize ⬇
write · ship for strangers
%%{init: {
"theme": "base",
"themeVariables": {
"background": "#07111f",
"primaryColor": "#0c1626",
"primaryTextColor": "#f3efe7",
"primaryBorderColor": "#2d3b56",
"lineColor": "#d8894b",
"secondaryColor": "#101b2d",
"tertiaryColor": "#0d1728",
"fontFamily": "Inter, ui-sans-serif, system-ui, sans-serif",
"fontSize": "16px"
},
"flowchart": {
"curve": "basis",
"htmlLabels": true,
"nodeSpacing": 32,
"rankSpacing": 46,
"padding": 14
}
} }%%
flowchart LR
S["Scaffold · R"] --> I["Implement · W"]
I --> RV["Review · R"]
RV --> WF["Workflow · W"]
WF --> FU["Follow-up · R"]
FU --> MA{{"Marbles · W ⬆"}}
MA --> AU["Audit · R"]
AU --> PO{{"Polarize · W ⬇"}}
PO --> DU["DoU · R"]
DU --> HY["Hydrate · W"]
HY --> RE["Release · W"]
classDef read fill:#0d1728,stroke:#3b6ea5,color:#dbe7f3,stroke-width:1.3px;
classDef write fill:#1a1410,stroke:#d8894b,color:#ffd9bd,stroke-width:1.6px;
classDef core fill:#1a1110,stroke:#e2935a,color:#ffd9bd,stroke-width:2.4px;
class S,RV,FU,AU,DU read;
class I,WF,HY,RE write;
class MA,PO core;Sight, memory, mouth, hands. Names you can type. Evidence first — the board is the metaphor.
$ curl -fsSL https://vibecrafted.io/install.sh | bash Puts the command on your PATH. $ loct impact src/auth.ts && aicx search "handoff" Sight before the edit. Durable intent after compaction. $ /vc grok send "Finish until this is a daily-driver, not a demo." Mouth on the bus. Tokens stay on the host. Slack is a projector. The Operator Frame is pinned host chrome — Dashboard, Active runs, Config, Doctor, Projects — welded into every dispatch layout and never moving with sessions. Workspaces below it are guests: they flow with ⌘-arrows and die with their sessions, each carrying Overview, Agents, and Shell organs. Voc is the host console, pulled out of the guest tab row; Panels carry the interactive-agent layer, global or project scope.
Obrazy dysków lima to sparse files — Finder sumuje długości logiczne, du pokazuje realne bloki.
colima-ci/disk 120.0G apparent → 33.2G real · datadisk 100.0G → 0.01G
Suma apparent: ~280G — to widzi Finder. Realna: 40G.
A session can end without disappearing. The operator is an agent: it runs the relay, and each leg hands the baton to the next runner — the next agent inherits reports, decisions, and open questions, not a cold prompt. You stay the founder — scope, taste, the hard transitions, the feel of the project — you never run the legs yourself.
After install, the first useful thing is a recorded run — not a health sermon.
$ vibecrafted workflow claude -p "Read this repo and name the first fix." Init may surface repo shape, recent context, and the first risks before any edit starts.
$ vibecrafted init claude Workflow helps when the task needs a little ceremony: examine the surface, research the gap, then implement the cut.
$ vibecrafted workflow claude --prompt "Plan and implement <task>" Marbles runs small counterexample loops. It may find an edge case, a false assumption, or simply a place that needs a human decision.
$ vibecrafted marbles codex --count 3 --depth 3 DoU is the moment to stop pretending. It asks what is missing across install, docs, runtime, trust, and release.
$ vibecrafted dou claude --prompt "Audit launch readiness" Release gathers the outward work: artifacts, deployment notes, docs, and the next human-readable step.
$ vibecrafted release codex --prompt "Prepare release steps" The convergence framework is the synthesis of research on agent handoffs, release gates, and runtime contracts. Sources below — consult before adopting.
A few field notes from the wild — from agent-built products and our own release lanes. Anonymized, because the pattern says more than the name.
The upstream framework was already fixed, but the public landing repo still served older installer truth. Everyone was right inside their own checkout; the user saw drift.
FIELD NOTE · representative repo release laneA helper script kept yesterday's path assumptions after the main runtime flow was repaired. The product worked, until an operator followed the stale trail.
FIELD NOTE · helper surface auditA checkout path looked healthy until activation moved into claim and webhook truth. The sale happened; the entitlement story still needed a witness.
OBSERVED · real founder (redacted)No staging, no smoke tests, no rollback. The migration deadlocks on a lock table. Support tickets spike while the founder tries to remember which tab ran last.
OBSERVED · field reportsNot the first-time vibe coder — the post-vibe cleanup buyer. Technical founders and small eng teams.
Open core for the engineer who inherited AI-written change. Paid pilots at full seat price. Forge when regulated.
Green main is engineering evidence, not a product verdict. Numbers map to PRs and live corpus rates.
CLI + MCP + self-host. Your keys. Your mesh.
Hosted control + bus for teams cleaning up AI-written change.
Regulated / EU / air-gap. White-label audit plumbing.
One sharp wedge as MCP, OSS hook, outreach to 30 technical founders — measure paid pilots at ≥$49/seat without discount games.
Start paid pilotMap · impact · evidence report on a real PR.
Technical founders / small eng teams only.
Named buying moment + written success criteria.
Repeatable channel — or hedge / private tooling.