All Docs
Read https://nanocode.xyz/llms.txt and help me build an agent with nanocode.
Paste a prompt into a coding agent that can fetch URLs, such as Claude Code, Codex, or nc. The agent reads the guide's Markdown and writes the code. Open a prompt in the playground to run it against the docs in this browser.
Read https://nanocode.xyz/llms.txt and help me build an agent with nanocode.
Read https://nanocode.xyz/docs/guides/agents.md, then add a nanocode agent to this Rust project: build one Nanocode runtime with Claude and Codex enabled and the default tools off, spawn a Claude Haiku agent, stream its reply to stdout, and shut the runtime down cleanly.
Read https://nanocode.xyz/docs/guides/tools.md, then expose this project's core operations to a nanocode agent: wrap each as an async #[nanocode::tool] function with a clear description, register them with Tools::builder().without_defaults(), and add a FunctionTool for any tool whose schema is only known at run time.
Read https://nanocode.xyz/docs/guides/code-mode.md, then add a Code Mode harness to this Rust project that registers our tools and runs JavaScript cells against them without a model, so we can test parallel calls and how tool errors surface.
Read https://nanocode.xyz/docs/guides/subagents.md, then add a nanocode coordinator to this Rust project that splits a task across parallel subagents, gives each a typed output_contract, waits for their accepted results, merges them, and logs every subagent update to stderr.
Read https://nanocode.xyz/docs/guides/durability.md, then make this project's nanocode agent durable: store sessions in a JsonlStore, give every prompt a stable request ID, reopen the session by ID after a restart, and flush the agent before exiting.
Read https://nanocode.xyz/docs/guides/workers.md, then embed a nanocode agent in this JavaScript project with gakonst/nanocode-wasm: back its SqlHost with our SQLite database, inject the API key in dispatch, expose one host tool, and drive a turn to completion.
Read https://nanocode.xyz/docs/guides/remote-hands.md, then split this project's nanocode agent into a brain and a hand: the brain listens for hands with a shared token and keeps inference and durability, and a hand binary connects from the build machine and runs tools in its checkout. Read the token from NANOCODE_RUNNER_TOKEN on both sides.
Read https://nanocode.xyz/docs/guides/gateways.md, then route this project's Codex agents through a Responses gateway selected by an environment variable, either OpenRouter or Cloudflare AI Gateway, reading keys only from the environment and leaving the agent code unchanged.
Read https://nanocode.xyz/docs/guides/cli.md, then install the nanocode CLI on this machine, add the nc alias, and tell me how to sign in with /login and start a session in this repository.
Read https://nanocode.xyz/docs/guides/exec.md, then add a CI job to this repository that installs the nanocode CLI and runs nc exec through a Responses gateway with its key from a repository secret, reviewing the current branch's diff and printing the reply to the job log.
Read https://nanocode.xyz/docs/guides/xframes.md, then build a Cloudflare Worker in this repository that works like xframes: one Durable Object per user runs a nanocode-wasm agent whose publish_frame host tool stores an HTML app, the Worker serves each app at /f/<id> with player card tags, and a second Durable Object polls the bot's X mentions and replies with the app's link.
Read https://nanocode.xyz/docs/guides/mpp-payments.md, then build a nanocode CLI for this project that pays for its models per request the way gakonst/nanocode-machines does: implement a nanocode::http::Layer that runs mpp-rs's send_with_exchange over the layer's Next, register it with ModelClients::openai_endpoint and claude_endpoint, and start the CLI with nanocode_cli::run_with.
Read https://nanocode.xyz/docs/guides/nanocode-ts.md, then run a nanocode agent from this TypeScript project with gakonst/nanocode-ts: add it as a git dependency pinned to a commit, back its SqlHost with node:sqlite, add the API key in dispatch, expose one host tool, and drive a turn to completion.