Build with agents.
Keep your judgment.
Practical reference for building, reviewing and teaching with agents. Find the reasoning, the tradeoffs and the exact text.
Reference library
31 references
-
Automate lifecycle work with hooks
A hook is not a better prompt. It is a lifecycle checkpoint. Use it when the behavior should happen whether or not the model remembers.
-
Build hyper-specific workspace agents
The fastest useful agent is usually not the biggest one. Wrap the tools you already trust, preload only the context the job needs, and keep broad agents out of small repeated tasks.
-
Build narrow daemons and inspectable agent graphs
Run focused background daemons that update a human-readable HTML dashboard; Use low-reasoning iteration with a deliberately small-context strategy; Coordinate SDK multi-agent graphs with a multimodal verification loop.
-
CMUX Orchestration Field Guide
Use panes, browser tabs, and a manager agent without letting workers step on each other.
-
Codex Daemon Profile Field Guide
Turn repeated web-dev chores into narrow, cheap, low-context Codex workers.
-
Combine intent, implementation, and output for autonomous work
Bundle the context triad — intent, implementation, and live output — for diagnosis; Run specialized Codex daemons as overnight emulated crons; Coordinate agents through natural-language loose coupling.
-
Command a CMUX manager/worker layout playbook
Web developers already juggle dev servers, test runners, browser verification, and agent chats; this pattern turns that chaos into one visible Manager pane coordinating narrow worker panes. It matters most when a local app needs code changes plus runtime proof, because the Manager can inspect panes, send targeted tasks, read worker output, and keep the human focused on decisions instead of pane babysitting.
-
Control agent lifecycle with hooks and context hygiene
Manage context with compaction and conversation forking; Wire user-prompt, tool-use, and stop hooks into your workflow; Choose between skills and plugins and run a Ralph loop.
-
Coordinate agents with a manager and worker panes
Adopt an agent-first mindset and the manager-worker topology; Drive CMUX terminal layouts with natural language; Set up AFK automation loops that keep working while you don't.
-
Install and inspect dash-prefix Imp routing
Installation and trust-boundary guidance for foreground and forked Imp routing, including helper contracts, hook registration, verification prompts, cmux inspection commands, and troubleshooting.
-
Isolated Codex daemon profile playbook
Web developers constantly repeat narrow CLI work around local dev servers, deploy previews, browser QA, GitHub checks, and framework tooling. An isolated Codex daemon profile turns one repetitive tool workflow into a cheap, warm, low-context helper instead of dragging a full general agent through every small task.
-
Keep parallel agent work visible and bounded
A parallel workspace is not useful because it looks busy. It is useful when each lane has a job, a boundary, a check, and a visible trail. Start by planning the split. Then open the workspace that makes that split easy to supervise.
Browse 19 more references
-
Markdown flows as a repeatable control surface
Preload fresh evidence, declare capabilities, isolate ambient context, and improve prompts through explicit proposals.
-
Markdown flows as a repeatable control surface — discussion and evidence
Detailed companion accounts of concepts, questions, demonstrations, exercises, and unresolved observations.
-
Markdown flows as a repeatable control surface — prompts and exercises
Complete reusable prompts, setup recipes, success checks, and caveats for markdown flows as a repeatable control surface.
-
Markdown flows as a repeatable control surface — questions and tradeoffs
Detailed questions and tradeoffs with concrete prompts, observable outcomes, and the limits of the example.
-
Markdown flows as a repeatable control surface — reference patterns
Extended explanations, comparisons, experiments, and practical actions for the same operating pattern.
-
Markdown flows as a repeatable control surface — worked example
Detailed worked example with concrete prompts, observable outcomes, and the limits of the example.
-
Narrow Imp agents and routing: practical reference
Comprehensive Imp reference covering setup and verification, narrow-agent boundaries, command modes, router and compound routing, foreground/forked dash hooks, cmux inspection, fleet and warm-session management, runtime isolation, prompt templates, bounded…
-
Narrow Imp agents and routing: practice drills
Exercises covering Codex-versus-Imp selection, health checks, routing and execution modes, dash-prefix hooks, bounded marker packets, fleet management, evolution review, narrow Imp design, failure recovery, tests, and final handoff receipts.
-
Overnight emulated-cron loop playbook
Web developers often need long-running investigation without a real scheduler: flaky auth, broken localhost flows, intermittent console errors, or UI drift that only appears after repeated checks. This pattern gives an agent a bounded timestamp loop, runtime evidence, and a hard stop so overnight work produces receipts instead of vague claims.
-
Policy at the agent’s execution boundary
Project-specific shells, session-scoped guidance, Codex airlocks, and Claude hooks—with their bypass limits.
-
Policy at the agent’s execution boundary — discussion and evidence
Detailed companion accounts of concepts, questions, demonstrations, exercises, and unresolved observations.
-
Policy at the agent’s execution boundary — prompts and exercises
Complete reusable prompts, setup recipes, success checks, and caveats for policy at the agent’s execution boundary.
-
Policy at the agent’s execution boundary — questions and tradeoffs
Detailed questions and tradeoffs with concrete prompts, observable outcomes, and the limits of the example.
-
Policy at the agent’s execution boundary — reference patterns
Extended explanations, comparisons, experiments, and practical actions for the same operating pattern.
-
Policy at the agent’s execution boundary — worked example
Detailed worked example with concrete prompts, observable outcomes, and the limits of the example.
-
Ralph Loop stop-hook continuation playbook
Web developers already run agents against real repos, dev servers, browser panes, and local QA loops; the Ralph Loop helps those agents keep working toward a bounded goal instead of stopping after one polite assistant turn. It is especially useful for web tasks where success is observable only after code, tests, logs, and browser behavior line up.
-
Reusable flow and skill recipes
Complete small contracts for code review, onboarding, test repair, changelogs, PR descriptions, pane-aware standups, and preference capture.
-
Workspace and session routing: practical reference
Practical cmux/tmux orchestration reference with an agent setup prompt, workspace/pane/surface/session routing model, focused Codex fork and compact workflows, transcript exports, zsh helper integration, multi-agent layouts and gated chains, verification…
-
Workspace and session routing: practice drills
Nine exercises establish workspace-to-session routing and receipts using cmux identity, explicit handles, workspace focus, environment inspection, helper panes, focused Codex fork previews, transcript exports, layered debugging, and gated agent_chain phases.
No references match yet.
Try fewer words or choose another subject.