Skip to main content
Day-2 operations use the same commands whether the agent was deployed with deploy, upload, or import. Every command runs against the active cluster.

Status and logs

-f live-tails via SSE.

Start, stop, restart, scale

restart tears down and recreates the container — this is what picks up changed secrets or environment variables. stop / start pause and resume without touching configuration. On Nasiko Cloud, agents run on the Kubernetes runtime on every plan. On a self-hosted server under Docker, any scale above 1 is clamped to 1. Horizontal scaling there needs the Kubernetes runtime, which needs an Enterprise license. See Agent hosting.

Deployments

A deployment is one running instance of an agent, with crash reason and restart count.
deployments restart restarts by deployment ID (from ls), not by agent name. Container-level nasiko restart <agent> is the usual choice.

Writable storage

Plans: Individual, Pro, and Enterprise. Self-hosted: Included in the open-source server.
By default an agent’s filesystem is ephemeral. To keep a directory across restarts, redeploys, and code updates:
--writable mounts a private-per-agent volume at /workspace. --writable-path mounts at that absolute path instead (and implies --writable). Pick a dedicated state directory — the mount hides whatever the image ships at that path.

Import from a registry

The cluster pulls the image itself. No local Docker needed. The registry host must be one the server allows: registry.nasiko.com, the registry URL set in the dashboard settings, or a host listed in REGISTRY_IMPORT_ALLOWED_HOSTS.

Remove

Terminates the container and deregisters the catalog entry. -f skips confirmation.

Secrets and env

Precedence, highest first: nasiko deploy -e → agent-specific secret → vault secret. Full model: agent secrets.

Next

Versions and rollback

Version history, reupload, rollback.

CLI operate reference

Every flag.