CLI 0.16.1 — Long-running agent turns no longer drop
Long-running chat and delegated (A2A) agent turns are now resilient to brief network interruptions between your session and the agent’s sandbox.
Highlights
No more mid-turn drops. A transient connection blip no longer kills an in-progress agent turn — work that was running keeps running and reconnects instead of dying 10 seconds later.
Cancel still stays prompt. When you intentionally cancel a turn or it hits its timeout, it now stops immediately rather than lingering.
Clearer async guidance.mf agent help now documents that --async delegated turns are not unbounded — they still have a cap, just a longer one than blocking turns.
v0.31.0
Manyfold — Native sign-in, account connections, and chat file attachments
This release introduces a self-hosted sign-in experience, account-level connections your agents can use, and file attachments across chat — plus per-agent MCP tool configuration.
Highlights
A new way to sign in. Manyfold now runs sign-in itself: email and password (with email verification), Google, and single sign-on (OIDC), all configurable by your workspace admins. Sessions are issued and revoked by Manyfold directly.
Account connections. Link your GitHub, Cloudflare, and Composio accounts once, and Manyfold makes them available inside your agents — GitHub and Cloudflare as credentials, Composio as a set of ready-to-use tools.
File attachments in chat. Attach files in the chat composer, send file and image parts through the OpenAI-compatible API, and upload files to Dify chat agents.
Per-agent MCP tools. Choose which MCP tools an agent can use, per scope, right from the agent detail page.
Notes
You may need to sign in again. As part of moving to the new sign-in, existing sessions were reset. On the sign-in page, use Forgot password to set an email password, or sign in with Google/SSO once your admin has enabled it. If you run into trouble, reach out to your workspace admin.
v0.16.0
CLI 0.16.0 — Machine-readable —json across every command
Every mf data and mutation command now supports --json, so you can script Manyfold end to end and parse both success and failure reliably.
Highlights
--json everywhere. All data and mutation commands accept --json for machine-readable output; deletes emit { "ok": true, "id": ... }.
Parseable errors. In --json mode, failures print { "error": { "message": ... } } on stderr with a non-zero exit, so scripts can branch on both outcomes.
Secrets stay redacted. Channel output remains secret-redacted in JSON mode, and login --json reports the result without ever printing your token.
Notes
Raw-stream and interactive commands (files read, daemon logs, daemon start/register/stop, update) keep their existing behavior.
v0.15.0
CLI 0.15.0 — Pick a specific mf CLI version for hosts and sandboxes
The runtime host and sandbox detail pages gain an mf CLI version picker, so you can update a host to a specific build instead of only jumping to the latest. Stable and staging builds are surfaced where available, and daemons can pull a cross-channel build in non-production environments.
Highlights
Install a specific mf CLI version. The runtime host and sandbox detail pages now include a version picker — update a host or sandbox to a chosen mf CLI version, not just the latest.
Stable and staging builds, min-version filtered. In local and staging environments, both stable and staging builds are listed, filtered to the admin-configured minimum CLI version.
Cross-channel daemon updates. In local and staging, a daemon can install a build from another channel (for example, a staging build on a stable daemon) when it runs a CLI that supports the daemon.update channel override. Production daemons stay on their own channel.
Notes
The version picker lives on the runtime host and sandbox detail pages in the web app.
Update with mf update --force --yes; existing daemons keep working.
v0.14.0
CLI 0.14.0 — Agent health & diagnostics commands removed
The low-value agent diagnostics surface is retired across the platform. The CLI drops the mf agent diagnose and mf agent health-check commands; agent storage reporting stays exactly as it was.
Highlights
Removed mf agent diagnose. The agent diagnostics probe — and the API endpoint behind it — is gone.
Removed mf agent health-check. The agent health-check command — and the API endpoint behind it — is gone.
mf agent storage-usage is unchanged. Storage reporting (and the web Storage tab) works exactly as before.
Notes
These commands backed the Health, Diagnostics, and Extras tabs in the web agent settings, which are removed in the same release.
Update with mf update --force --yes; existing daemons keep working.
v0.12.0
CLI 0.12.0 — The CLI is now mf
The command-line tool is renamed from nca to mf, with an agent-facing help guide built in, more resilient logins, and safer channel output. Existing installs keep working — the legacy nca binary still self-updates onto the renamed CLI, and your config is read from the old location as a fallback.
Highlights
Renamed to mf. The binary, commands, and docs now use mf (was nca). Config moves to ~/.manyfold (with read-only fallback to ~/.config/nca), and the local daemon migrates to ~/.manyfold/daemon on first run. Your API tokens and existing agents are unaffected.
mf help --agent. A built-in agent operations guide that works offline and without login. mf help <topic> --agent covers 13 focused topics — auth, safety, channels, automations, files, model-config, skills, runtime, agent, backups, usage — with exact scopes and copy-pasteable commands; --json returns a stable envelope.
Resilient poll-mode login.mf login --poll now persists the pending request, so an approval is no longer lost if the polling process exits before you approve (the common case in chat). The next mf command redeems the approved session automatically, and mf login --resume checks or completes it. Consent links now stay valid for 15 minutes.
Channel secrets masked everywhere.mf channels get/create/update/list redact secrets at every nesting level, including Lark webhook verificationToken / encryptKey. Note: mf channels list --json now returns [redacted] for secret fields — read secrets from your own records, not CLI output.
Notes
A new staging release channel lets you install pre-release builds: install.sh gains an MF_CHANNEL switch (staging builds point at the staging API and self-update independently of stable). Production install/update behavior is unchanged.
Update with mf update --force --yes (or nca update from an older install); existing daemons keep working.
Chat runs backed by your local nca daemon now survive transient
daemon↔cloud connection loss — laptop sleep, network blips, or a server
restart no longer kill an in-progress assistant turn with a
claude_exec_failed error.
Highlights
The daemon buffers exec output to disk and replays it after reconnecting, so a brief disconnect no longer loses work.
When the daemon comes back, the cloud transparently resumes the in-flight assistant turn instead of failing the message.
Messages whose daemon is temporarily offline are now held in a suspended state and resume automatically, rather than ending in an error.
Notes
To get the new behaviour, update the daemon: nca update --force --yes, then restart any long-running daemons.
Fully backward compatible — older nca versions keep working against the updated cloud API; the disconnect-survival path engages once you are on 0.11.0.
v0.10.0
CLI 0.10.0 — Cloud Agents is now Manyfold
The product has been renamed from Cloud Agents to Manyfold, with new primary domains across the web app, API, admin, docs, and CDN. Existing CLIs, daemons, scripts, and bookmarks keep working during a grace period — old hostnames continue to respond, and the nca binary name is unchanged.
Highlights
Product name in CLI help text, prompts, and output is now Manyfold everywhere it used to say “Cloud Agents” or “Netmind Cloud Agents”.
All old domains continue to serve during the grace period — web/docs apex 301-redirect to the new domain, API/admin/CDN respond on both hostnames — so existing CLI installs and integrations don’t need to change immediately.
Notes
The CLI binary name remains nca for backwards compatibility. Existing shell aliases, scripts, daemon init units, and CI configs keep working unchanged.
Sign-in: Clerk’s primary domain switched to manyfold.ai, so you may be asked to sign in again the first time you visit the new web app.
To pick up the new binary, run nca update --force --yes. Existing daemons continue to run against the old API hostname until restarted.
The GitHub repository moved from protagolabs/netmind-cloud-agents to protagolabs/manyfold. Old URLs are forwarded automatically by GitHub.
v0.9.0
CLI 0.9.0 — Channel session switching
nca channels gains a sessions subcommand group for inspecting and managing the per-scope chat sessions that channel bridges create. Same primitives the in-channel slash commands and the web sidebar use, now scriptable from the terminal.
Highlights
nca channels sessions scopes <channelId> — list scopes in a channel with their active session, total session count, and last activity timestamp.
nca channels sessions list <channelId> [--scope-key <key>] [--include-archived] — list sessions, with active marker, channel session id, scope, and display name (🏷️ when user-set).
nca channels sessions new <channelId> --scope-key <key> [--name <name>] — create a new active session in a scope; the previous active becomes inactive.
nca channels sessions switch <channelId> <sessionId> — make a session active in its scope.
nca channels sessions rename <channelId> <sessionId> <name> — set the channel display name (the 🏷️ label that shows in /list inside the channel and in the web sidebar).
nca channels sessions delete <channelId> <sessionId> [--activate-fallback] — archive a session; with --activate-fallback, auto-activate the newest remaining if you delete the active one.
Every command supports --json to emit raw JSON for piping into other tools.
Notes
Slash commands inside each connected channel — /new, /list, /switch, /current, /rename, /delete, /help — are now always on and mirror the CLI semantics.
Display name and chat-session title are independent: rename in the CLI / web “Rename channel display” updates display_name; rename in web “Rename session title” updates the chat-session title. Either appears in the web sidebar; the 🏷️ marker indicates a user-set channel display name.
nca update --force --yes pulls the new binary; existing daemons keep working unchanged.
v0.8.0
CLI 0.8.0 — Daemon autostart on login and boot
nca daemon start now installs an OS init unit so the daemon auto-starts at login and is automatically restarted by the operating system if it crashes. The web app’s Settings → Local daemons also shows each connected machine’s CLI version and how its daemon was launched.
Highlights
nca daemon start installs a per-user init unit by default — macOS launchd LaunchAgent (~/Library/LaunchAgents) or Linux systemd user unit (~/.config/systemd/user). The daemon now auto-starts on login and is restarted on crash by the OS.
nca daemon start --system installs a boot-time unit (requires sudo): /Library/LaunchDaemons on macOS or /etc/systemd/system on Linux. Use this on always-on machines that should run the daemon before any user logs in.
nca daemon start --foreground runs the daemon inline without touching any init unit, useful for debugging and CI. nca daemon stop cleanly removes the init unit it installed, and nca daemon status / nca daemon doctor now report both user- and system-scope unit state.
Each row in Settings → Local daemons → Connected machines now shows the daemon’s CLI version and how it was started, e.g. cli 0.8.0 · autostart · login (launchd) or cli 0.8.0 · manual.
Notes
Existing daemons keep running unchanged; the new init unit is only installed the next time you run nca daemon start. Run nca daemon stop && nca daemon start to opt in.
Use nca update --force --yes to reinstall the latest standalone binary, then nca daemon doctor to confirm the init unit was installed correctly.
v0.7.0
CLI 0.7.0 — One-step daemon onboarding
nca daemon register now offers to start the daemon immediately after registration, so connecting a new local machine takes one extra keystroke instead of a second manual command.
Highlights
After nca daemon register --token <TOKEN> succeeds in an interactive shell, the CLI prompts Start the daemon now? [Y/n]. Pressing Enter or y starts the daemon detached; pressing n keeps the existing register-only behaviour.
Added -y / --yes flag for non-interactive setups (CI, unattended provisioning): nca daemon register --token <TOKEN> -y registers and starts the daemon in one shot, no prompt.
Behaviour in non-TTY shells without -y is unchanged: the command only registers and prints the existing Next: run nca daemon start hint.
Notes
The web app’s Settings → Local daemons now renders the full nca daemon register --token <TOKEN> command in a copy-ready block so it can be pasted straight into a terminal — see the new Register a local machine doc for the end-to-end flow.
Use nca update --force --yes to reinstall the latest standalone binary.
v0.6.0
CLI 0.6.0 — Command surface expansion
This minor release significantly expands the CLI surface, adding new top-level command groups for managing Cloud Agents resources, plus per-agent token binding support for the OAuth grant flow.
Expanded nca agent (alias agents) with get, update, delete, diagnose, health-check, storage-usage, model-config, and credentials.
Expanded nca runtime (alias agent-runtimes) with control-ui, dashboard, and agents {add,list,remove}.
nca login --poll accepts --limit-to-agent to bind the new token to a specific agent (full API support lands in a follow-up).
Notes
Runtime helper markdown emitted by agents now lists every CLI subtree; the legacy raw-curl Path-B section is removed.
Use nca update --force --yes to reinstall the latest standalone binary.
v0.5.0
CLI 0.5.0 — Channel management
This minor release adds CLI support for managing Cloud Agents channels.
Highlights
Added the nca channels command group.
Added commands to list, create, inspect, update, delete, test, and register channels.
Added global agent context support with --agent-id and NCA_AGENT_ID for channel workflows.
Notes
Use nca update --force --yes to reinstall the latest standalone binary after the release workflow publishes it.
v0.4.0
CLI 0.4.0 — External runner daemon support
This minor release updates the CLI and local daemon protocol for the current Cloud Agents runtime contracts.
Highlights
Added external runner daemon protocol support.
Updated the standalone CLI binary against the latest shared SDK contracts.
Kept local daemon integrations aligned with current API, chat, and runtime metadata shapes.
Notes
Users running local daemon-backed agents should update their CLI binary before using external runner workflows.
v0.3.1
CLI 0.3.1 — Model configuration compatibility
This patch release keeps local daemon runtimes compatible with per-agent model configuration.
Highlights
Added daemon protocol support required by per-agent model configuration.
Added model-aware chat session support across API, SDK, web, and local daemon integrations.
Repaired managed Sub2API credential handling used by managed model providers.
Notes
Users should update local CLI binaries when using agent-specific model settings with local daemon runtimes.
v0.3.0
CLI 0.3.0 — Workspace and terminal runtime updates
This minor release updates the CLI and daemon runtime protocol for newer Cloud Agents workspace behavior.
Highlights
Added support for custom workspace directories across hosted and local agent runtimes.
Repaired local terminal session handling for daemon-backed agents.
Improved runtime diagnostics by using the runtime kind when checking agents.
Added support for Unicode agent display names.
Updated object-id-compatible runtime naming used by hosted sprite-backed agents.
Notes
This release includes protocol and runtime compatibility updates for the broader Cloud Agents product, not only command-line UX changes.
v0.2.1
CLI 0.2.1 — Daemon lifecycle hardening
This patch release hardens local daemon process management and CLI authentication session handling.
Highlights
Hardened nca daemon start and stop behavior with shared pidfile handling.
Added stale-pid recovery when a previous daemon process exited unexpectedly.
Added a start lock to avoid overlapping daemon launches.
Propagated daemon-stopped state back to agents more reliably.
Bounded CLI login sessions and consumed login state atomically.
Notes
This release focuses on reliability for local machine runtimes and browser-based CLI login.
v0.2.0
CLI 0.2.0 — Browser login and production defaults
This release improves the first-run CLI experience and makes the standalone binary point at the production Cloud Agents API by default.
Highlights
Added browser-based nca login with a loopback callback for local machines.
Added a headless auth-code login path for environments where opening a browser is not practical.
Switched the default API URL to the production Cloud Agents endpoint.
Renamed daemon login flows around machine registration language.
Added the nca update self-update command.
Fixed daemon spawn arguments in Bun-compiled binaries.
Notes
This version is the first CLI release backed by Changesets-generated package release notes.
v0.1.0
CLI 0.1.0 — Initial public release
First public build of the nca CLI, distributed as a standalone binary.
Highlights
One-line install on macOS and Linux: curl -fsSL https://cdn1.netmind.xyz/cli/install.sh | sh
Five platform binaries: linux-x64, linux-arm64, darwin-x64, darwin-arm64, windows-x64
Browser-based login from the terminal
Commands for listing agents and runtimes
Local machine registration through nca daemon
Built-in CLI update checks
SHA256 sidecars for every asset
Notes
The first CLI release focuses on sign-in, listing, runtime inspection, updates, and local machine registration. Rich chat and terminal workflows are available in the web workspace.