Who it is forA developer who wants a browser-based AI coding workspace on a local repository.
The problemSetting up the web client and backend by hand is slow without the repo's dev command.
The outcomeA running web workspace at localhost:5173 that works on the chosen project folder.
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
- Install Git, Node.js 24.14.0 and pnpm 10.33.2 as listed in mise.toml.
- Clone the repository and run
pnpm bootstrapfrom the repository root. - Run
ZCODE_SERVER_WORKSPACE=/path/to/project pnpm dev:webon macOS or Linux. - Open
http://localhost:5173in a browser.
Prompt for your agent
In the zai-org/ZCode repo, run `pnpm bootstrap`, then `ZCODE_SERVER_WORKSPACE=<project-path> pnpm dev:web`. Report the web dev server URL and confirm that the backend at http://localhost:3030 responds.
Caveat. The README gives the ZCODE_SERVER_WORKSPACE example only for macOS and Linux, and the browser must use port 5173 while the backend uses 3030.
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