ZTC Quickstart
Install the beta terminal agent, sign in, review your first plan, and keep work in a named session.
ZTC is the Zerg Terminal Client, an AI agent for working in an existing project. It reads code, makes a plan, edits files, runs commands, and checks results. ZTC is currently in beta.
1. Install
Use a supported Node.js release (Node 22 recommended) and npm. The native interactive terminal and desktop
payload in the published beta supports Apple Silicon macOS (darwin-arm64).
JavaScript and headless surfaces support macOS, Linux, and Windows; the beta
does not include interactive native binaries for Linux, Windows, or Intel Macs.
If you installed the legacy zerg-ztc package, remove it first
(npm uninstall -g zerg-ztc). It provides the same ztc and zerg commands.
npm view @zergai/ztc version
npm install -g @zergai/ztc
ztc --version
@zergai/ztc provides the ztc and zerg commands. Install only one ZTC
distribution globally because these command names overlap. For a pinned install,
replace the package name with @zergai/ztc@<version> using your selected version.
The installed release version can differ from its development source version.
ztc --version prints ztc v followed by the installed version. If it does not
show the version that npm view reported, or the version you pinned, run
which ztc to see which executable your shell found. If that is not the one npm
just installed, or the legacy zerg-ztc package is still present, remove the old
package and install again.
The CLI install does not automatically create a standalone desktop app. On supported
macOS hardware, ztc --desktop --cwd /path/to/project opens the desktop surface.
An optional application launcher can be created explicitly after installing:
node "$(npm root -g)/@zergai/ztc/scripts/install-macos-app.mjs"
The launcher installer uses /Applications when writable, otherwise
~/Applications. Set ZTC_DESKTOP_APP_DIR=/path to choose another directory.
Opening the launcher starts the desktop in your home folder.
Standalone desktop and installer
The ZTC download page enables the standalone download,
curl installer and Homebrew command only after the same signed, notarized
Apple Silicon release has been verified and published. The standalone app is
named ztc.app and includes its own Node runtime. It shares ~/.ztc profiles
and sessions with the terminal client. The first standalone releases use the
explicit preview channel; they are separate from a stable release.
Use the exact command shown on that page. Until those methods are available,
use npm or bun with Node installed. Avoid installing multiple distributions
onto the same command path; use which ztc to check the selected installation.
2. Choose one authentication route
Start ZTC in your project, then choose a route from the welcome message:
ztc --cwd /path/to/project --plan
Zerg Router browser login: run /auth login inside ZTC, or ztc auth login
in your shell. Complete the login at zergrouter.com. Both entry points share
credentials. Select a routed model with /model zergrouter <provider> [model].
Model usage follows your Router account's terms.
The browser flow uses your personal Zerg account. On Router's billing page, review payment status and your monthly spending cap before starting a task. Signing in and checking account status do not themselves send an inference request. If payment is pending or the cap is reached, resolve that in Router before starting the agent.
Your provider API key: configure the provider explicitly with
/config key <provider> <api-key>, then select it with /model <provider> [model].
For example, use the anthropic or openai provider ID with a key from that
provider. Provider usage is billed under your provider account.
Claude Code OAuth: obtain a token with claude setup-token, configure
CLAUDE_CODE_OAUTH_TOKEN in the environment that starts ZTC, then use
/model claude_code. This route requires your own eligible Claude Code account.
Use /accounts to inspect configured accounts. Authentication does not change
ZTC's software license.
3. Review your first plan
In the plan-mode session, ask for a small, concrete task:
Inspect this project. Explain its entry points and test command, then propose a small change and the checks that would prove it works.
Plan mode supports read-only exploration. Review the proposed changes and
validation, then run /execute when ready for ZTC to perform the work. Inspect
the resulting diff and actual test output. /permissions shows the current
permission profile and /help lists commands.
4. Keep work in a named session
Use a descriptive name for work that will span multiple runs:
ztc --cwd /path/to/project --name project-next-step --plan
Use /sessions inside ZTC to find and resume saved work. Keep the project path
consistent when reopening a session. A named session preserves conversation
context; verify any external files, running commands, or remote state again
before relying on an earlier result.
Models
Run /model inside ZTC to see the current provider and model, and /model list
to list the models that provider offers. Available models depend on your
authentication route and provider access. Check the selected model and its
pricing before starting work.
What it costs
ZTC is free to evaluate. The License section below describes the other permitted uses and when you need a signed commercial license. Model usage is separate from the software license and follows the account behind your authentication route: your Zerg Router account's terms, your provider's billing for an API key, or your own eligible Claude Code account.
Uninstall
If you signed in with Zerg Router, run ztc auth logout first to end the
Router session. Then remove the package:
npm uninstall -g @zergai/ztc
Uninstalling removes the package and its ztc and zerg commands. ZTC keeps
its local data outside the package, in ~/.ztc by default: config.json
(settings and any saved API keys), Router sign-in credentials, and saved
sessions. Delete that directory yourself if you no longer need it. If you
created the optional desktop launcher, delete it from /Applications,
~/Applications, or the directory you set in ZTC_DESKTOP_APP_DIR.
Get help
- Bugs and questions: support@zergai.com
- Commercial licensing and design partnerships: licensing@zergai.com
License
ZTC is source-available, not open source, under the Zerg Source Available
License 1.0. The package includes LICENSE.md, COMMERCIAL-LICENSING.md,
NOTICE, and third-party notices. Read the terms shipped with your selected
release. They permit purpose-limited evaluation and specified personal,
educational, research, and nonprofit use. Free company use is limited to
purpose-bound evaluation; ongoing commercial development, operations, customer
work, and other Commercial Use require a separate signed commercial license.
Contact licensing@zergai.com for commercial terms. Authentication and model usage charges are separate from software licensing.