Concepts
When building with crtr, read this section because its pages explain which runtime parts solve each problem before you choose an SDK method or plugin field.
Use these pages to choose the shape of an agent application before you start wiring it. They explain the durable runtime model behind the SDK and plugin surfaces, then point to the detailed guides for each surface.
| Page | Decide |
|---|---|
| Nodes and the canvas | Whether work needs a durable node rather than one request and response |
| Lifecycle and wakes | Whether a node should finish, remain resident, delegate, or wait |
| Documents | What an agent should know or embody, who owns it, and where it belongs |
| Profiles, kinds, and modes | Which run-shaping dial matches an application concern |
| Scopes and trust | What an application or node may do and why only the daemon writes canvas state |
| Why a daemon | Why a broker survives a terminal and why viewers are clients rather than hosts |
Moving from @north-light/crouter
When you installed crouter or its SDK under the @north-light scope, read this page because the packages now publish as @crouter/*, and a plain swap fails on the first install under pnpm's minimumReleaseAge.
Nodes and the canvas
When deciding whether an agent task should outlive one request, read this because a node gives the task durable identity, context, reports, and a path for later messages.