#Examples

The repository ships seven examples, and they are products rather than fixtures. Each one uses only public agent-bundle exports and workspace:* dependencies, each one builds and validates through the same public CLI you would use, and none of them needs an API key or a signed-in host to reach a useful state. Four have a walkthrough here:

Three more are advanced composition references, documented by their own READMEs rather than walked through here:

#Running them

Run the pnpm example:* scripts from the repository root. Each one builds the workspace first, then starts that example's foreground agent-bundle dev server and prints the loopback Workbench URL. Pass --open (for example pnpm example:<name> -- --open) to open a browser:

pnpm install
pnpm example:skills

For the noninteractive path, pnpm examples:check runs every example package's own check script, validate and build, plus typecheck and tests where the example has them, with no dev server and no browser:

pnpm examples:check

Each example package also exposes the same public commands directly, once the repository-level pnpm build has built the local agent-bundle workspace dependency. Every example has validate, build, and check; the four walkthrough examples, Worktree Proximity, and Host Test also have dev, while the RSC Agent Runtime demo is driven through its tests and eval:hosts instead:

cd examples/skills-starter
pnpm validate   # agent-bundle validate
pnpm build      # agent-bundle build
pnpm check      # validate and build, without opening the Workbench
pnpm dev        # agent-bundle dev

#Reading an example

Every example page below records the same four things: what the example proves, the public packages it depends on, its root run command, and a link to its source. Read the source next to the page, the configuration files are short on purpose, because the src/ conventions carry most of the structure.

Two habits make the Workbench trustworthy while you explore:

• Wait for a completed state. A rebuild is finished when it reports Idle or Failed. A Building state is still in progress, and judging one is how a healthy project comes to look broken.
• Treat a failed rebuild as last-good behavior. A failed build publishes no epoch, so the Workbench keeps serving the previously published artifact alongside the new diagnostic. Restore the checked-in source and rebuild; the new active epoch is the repair evidence.

Hooks and Scripts ships a scripted, reversible diagnostic walkthrough for exactly that reason, break a handler, watch the failed rebuild keep the last-good artifact, restore, and read the new epoch as the repair. Skills Starter practices the same rebuild-and-restore loop against stale eval evidence; the other walkthroughs only ask you to wait for a completed state before judging a rebuild.

#Where the concepts live