crouter for developers
Two packages, pointing opposite ways. The SDK is how an application drives a crouter daemon. The plugin framework is how a daemon reaches a service you wrote.
They are separate npm installs — install only the one you need. Both depend on @north-light/crouter-api, which declares the request and response types they share.
Start with the concepts
Both packages talk to the same runtime. These pages explain nodes and the canvas, lifecycle and wakes, memory, profiles, scopes, and why a daemon owns the state — so you can decide what to build before you pick a method or a manifest field.
Concepts@north-light/crouter-sdkDrive a daemon from your app
Your application calls a crouter daemon: create nodes, stream their events, wait for a typed result, and read or write memory.
@north-light/crouter-pluginGive agents a new command
A crouter daemon calls your service: one typed TypeScript command tree becomes the Fetch handler, the manifest, and the archive `crtr pkg plugin install` accepts.