Skip to main content
Scaffold an agent, run it locally, deploy it, and see it under governance. Nasiko has two surfaces. Neither requires the other. Steps 1–4 use the CLI. Step 5 uses the dashboard. To govern agents someone else deployed, skip to step 5.

​
Prerequisites

  • Docker
  • An account with deploy permission — see ACL
  • A model provider API key (OPENAI_API_KEY or similar)
This one key actually needs to go in three separate places, and each is independent of the others — having it in one doesn’t mean it’s set for the rest:
  1. Your project’s own .env — read by nasiko run . for local testing (step 3 below).
  2. A per-agent secret — nasiko secrets set OPENAI_API_KEY <key> --agent <name>, read by nasiko deploy ./nasiko upload . (step 4). Deploy does not read your project’s .env — skip this and the deployed agent chats with a 502/empty error and no explanation. See managing agent secrets.
  3. The control plane’s own environment — needed for the routing engine and orchestrator chat (nasiko chat "..." with no agent name). If you’re running nasiko up locally, answer its setup wizard prompt for OPENAI_API_KEY rather than pressing Enter past it — see Setup Your CLI for the wizard and what happens if you skip it.

​
Get started

1

Install and authenticate the CLI

nasiko up starts a local control plane and connects the CLI to it as cluster local. auth login stores your token in ~/.nasiko/config.json. Options: Setup Your CLI.
2

Scaffold an agent

Writes an AgentCard.json, a Dockerfile, and starter source. Run nasiko new with no arguments for a wizard. Templates: Sample Agents.
3

Run it locally

Local runs use the same router and access checks as production. More: Build, Run, and Test Locally.
4

Deploy to the control plane

Builds the image, pushes it to the embedded registry, then registers and starts the agent. Writes .nasiko/agent.json bound to the deployed agent’s ID.No local Docker? Use nasiko upload . and the control plane builds it. See Deploy and Manage.
The deployed container does not inherit your project’s local .env — it starts with no model credentials unless you set them as a secret first:
Skip this and nasiko chat my-first-agent "..." fails with an unhelpful agent task failed or HTTP 502 — check nasiko logs my-first-agent if you see either. See managing agent secrets.
5

See it under governance

Sign in to the dashboard. Your agent is already:

​
Next steps

Manage secrets

Move that provider key out of your shell.

Set access policy

Control who can invoke, edit, and promote this agent.

Connect tools over MCP

Give the agent systems to act on.

Compose multiple agents

Wire agents together across frameworks.
Stuck? Ask in Discord or email support@nasiko.com.