Who it is forA developer who wants the terminal coding agent without the desktop app or a packaged release.
The problemThe packaged zcode command may point at an older install, so source runs are needed to test changes.
The outcomeAn interactive TUI session started from the current source, with the CLI help output confirmed first.
What you need first
- Git
- Node.js 24.14.0 and pnpm 10.33.2, as pinned in mise.toml
- Clone of the zai-org/ZCode repository
- A local project folder to point the agent at
Steps
- Complete the setup in the repository root with
pnpm bootstrap. - Check the entry point with
pnpm --filter @zcode/cli dev --help. - Start the interactive terminal agent with
pnpm --filter @zcode/cli dev. - Read the CLI usage guide at apps/zcode-cli/docs/usage/README.md for model setup, non-interactive calls and trajectory recording.
Prompt for your agent
In the zai-org/ZCode repo, run `pnpm bootstrap` and then `pnpm --filter @zcode/cli dev --help`. Report the available options and state whether the help text lists a non-interactive mode.
Caveat. This entry point runs the Agent CLI directly and skips the --web routing that the packaged zcode command provides.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page