Why VibeKit says the thing plainly: agents will act on chains; nobody in the
loop holds the key but the person's wallet, and the toolkit is shaped so that
stays true on every surface. How it works is the mental model with the
adapter table. Examples is one table over the runnable files. Run an action
walks examples/action.ts stage by stage; Compose a server is the reference
server's routing with its three decisions named. Index reorganised by who
you are; Explanation gets its own sidebar group.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

A Bun server (50 lines) mounts the agent handler, the action routes, and
REST over every tool, and serves the page. A React page (150 lines) streams
a turn, renders results with the vibekit add components by view id, and
walks a draft to approval — resting at approved, honestly, since no wallet
is wired. The component copies are drift-checked against the package.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

mcp: createMcpServer, createMcpServerFactory, createMcpHttpHandler,
serveMcpStdio. rest: createRestHandler, POST …/tools/<name> (it runs actions
too). The root exports the contract only; the compose engine is
@initlabs/vibekit/compose; agent exports the loop, the handler, and the
prompt — provider plumbing is agent/providers, the config file is
agent/config. The packed-consumer verifies catch up with phase 1's renames.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

createActionHost(deployment) and signDraftWith join actions; the deployment
read host and the block tail join views; createHost(network) — the stock
combined host the TUI and web server build on — and the Explorer agent
(tools, prompt, plugins, explain tool) are preset, where opinions live.
Five nouns again: query/action, agent, pay, views, preset; the rest are
adapters.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

views no longer re-exports the actions surface (every name had two import
paths); the fixtures and the sample host move to @initlabs/vibekit/views/sample;
ReadHost, classifyInput, routeInput, InputRoute, formatTime; record() is
createRecord; actionNextEventKinds is nextActionEvents. Imports in both apps
and the tests re-pointed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

draftDataSchema/DraftData, simulationDataSchema/SimulationData, stageEventSchema/
StageEvent, createStageEvent, <stage>StageEventSchema, actionIntentSchema/
ActionIntent, actionResultSchema. Rename only.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

createActionRoutes + createRemoteActionHost (actions/http): an ActionHost
over HTTP with server-side byte verification, lifted from the web agent's
explorer route and remote host. createReadHost + recordForToolCall (views):
the lookup surface over any callTool, shared by the live host and the
browser. The REST response carries the tool's view id, so a browser can wrap
any query into its record client-side. The web agent's 335-line explorer RPC
is now the action routes plus the query handler (house-billed), and the
enrichment/NFD side hosts it needed are gone.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Everything the two apps shared beyond the tool contract now ships in the
published package: views/ (browser-safe records, view models, the graph
builder, bridge, format, input, sample fixtures) and live/ (the deployment
host, block tail, enrichment, the Explorer agent). Tests and recorded
fixtures move with them; the block-tail record types move to views so views
never imports live. Apps import @initlabs/vibekit/views and /live; the
browser boundary test allows views beside actions.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

A generated tools reference (bun run docs:reference walks the tool contract:
29 queries, 16 actions, 5 plugins — never hand-edited), one tutorial (build
an agent: handler, components, signing), four short how-tos pointing at the
runnable examples (REST + x402, swap the model, swap the signer, components),
one explanation (queries and actions), the README reframed around the
surface, and a paragraph in the build-on-vibekit skill. Deliberately thin:
the API is moving; the reference is what stays current.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

packages/vibekit/components is the source: Companion, useAction (now free of
the explorer), ActionApproval, ToolResult, Transaction, Asset/AssetList,
Account, a digit-math format.ts, and one base stylesheet of class hooks.
Every component's props are a tool's output type, so the same data from an
agent event, a REST response, or an MCP result renders unchanged. The CLI
bundles them at build time (like skills); add --list/--dir/--force. The
agent app's copies are checked against the source in test.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

One POST per turn, NDJSON events back; a composed group leaves as a draft
record. Model, tools, prompt (a string or a function of the turn), per-turn
caps, billing, and limits are options; the package reads no env. Draft
decoding and the algod transaction formatter move from the explorer into
vibekit/actions so the handler emits drafts natively; activeSenderLine moves
to vibekit/agent. The web agent's route is now a mount (env → options); its
behaviour tests live with the handler. examples/agent-http.ts runs the same
under Bun with ZeroSignal as the model.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@initlabs/vibekit/pay: a PayStore interface (KV, Redis, memory), the credit
rules (paid turns per payer behind a bearer token, free turns per IP per
day, house caps), a web-standard x402 gate ported from @x402/next's withX402,
and createPaywall composing them: buy (402 → pay → credit), charge (a turn
or a 402), status. @initlabs/vibekit/rest: createQueryHandler — POST
…/query/<tool> runs any tool with the JSON body as arguments; actions return
the draft and never sign; a JSON Schema catalogue.

The agent app mounts these: credits/{config,ledger,route} shrink to env →
options plus the Vercel KV adapter; the agent route's inline gate is
paywall.charge; new /api/query/[name], /api/query (catalogue), and /api/mcp
(streamable HTTP, tools/call charged) sit behind the same paywall.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

The record envelope, stage events, reducer, host controller, and wallet
signing move from the explorer into the published package as a browser-safe
subpath (dependency direction forced the move: explorer builds on vibekit,
not the reverse). The explorer keeps the view models — the action view model
is views/action.ts — and re-exports the moved names so the apps' imports
hold. EXPLORER_PROTOCOL_VERSION → RECORD_PROTOCOL_VERSION.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

ActionHost.draft(toolName, args) replaces the payment-only draftPayment, and
the live host refuses queries at the boundary. The wallet-signing splice that
lived twice (explorer live + agent app) is one browser-safe actions/sign.ts;
the agent keeps only its record-signed transport. The agent's 12-param hook
becomes a headless useAction (components/action.ts, copy-paste tier) plus a
feed adapter. A swap with a pre-signed router leg runs the same machine in
test, and examples/action.ts does a payment end to end on LocalNet.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Rename only, no behavior change. *Tools → *Queries, *WriteTools → *Actions,
WriteFlow* → Action*, flows/ → actions/, feed block kind 'write' → 'action'.
Adds isAction/defineQuery/defineAction, defaultQueries/defaultActions, makes
tool output schemas required, and a signer example showing resolveSigner
takes any algosdk TransactionSigner.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>