Examples
The generated agent and the folders on nylorun/agents that use the current API.
npm create @nylorun/agent@beta my-agent
cd my-agent
npx nylorun start
npm run devThe starter registry contains one Assistant with no tools, and a comment
in agents/assistant/agent.ts that shows how to add an http() tool.
npm run dev saves it as an agent manifest and makes the Agent its sessions
run on, again on every edit. Copy other agents from the
Agents repository
into your own agents/ tree; do not copy credentials.
npx nylorun init agents/hello --example writes an example
agent manifest instead: AGENT.md, an HTTP tool,
an MCP server, and a webhook trigger, with a README.md that explains each.
Release registry
The examples' own registry, which their npm run dev saves, and the two
agent manifests beside it:
| Folder | What it shows |
|---|---|
release | An order assistant with an HTTP tool, and a data analyst that works in its Agent's sandbox. Both are saved with the virtual runtime in runtime/scratch.runtime.json. |
repo-brief | Every piece in one flow agent: Switch, Map, Parallel, Loop, a skill run in the sandbox, a remote MCP server, and an HTTP tool as the last stage. |
repo-brief-folder | repo-brief as a flow manifest: 23 files, a flow.json with a switch, a nested flow.json with a map, a parallel stage, a loop, and an HTTP tool stage. npx nylorun check agents/repo-brief-folder compiles it offline. |
triage | An agent manifest: AGENT.md and mcp.json, whose Bearer ${GITHUB_TOKEN} header derives a GITHUB_TOKEN bearer slot for GitHub's MCP server. Saved with npx nylorun apply agents/triage, or with npm run triage, which saves it with saveFolder() and makes its Agent. |
Agent examples
| Folder | What it shows |
|---|---|
tool-use | HTTP tools served by an example service. |
instructions | Instructions only, no tools. |
skills | Agent Skills folders our harness serves. |
subagents | Delegation to a child agent. |
mcp | A remote MCP server declared by URL, with no key. |
ag-ui | Chat UI through an app server, createAgUiHandler({ agents: ["support"] }), on one Agent of kind none for everyone. A Tenant tool policy ask rule holds each lookup_order call for the person's approval. |
Flow agent examples
| Folder | What it shows |
|---|---|
chain | Flow stages in order. |
switch | Choose one case from the previous output's route. |
parallel | Named branches at once. |
map | One agent per list item. |
loop | Retry until a verifier passes. |
ship-feature | Combined flow stages. |
Each save moves the Agents that track the manifest to the new version, and each session's next turn runs it; a turn already running ends on its version. See Versions.
Harness example
harness-minimal
is a harness written only against @nylorun/core/harness-api: it runs the
turns of sessions on a pod Agent whose manifest's harness.id is minimal, as
the host of the Agent's pod. See Bring your own harness.