WZ

williamfzc/zcode-cli

Developer tools

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

0 stars 品質 55 トレンド 8Apache-2.0

Standalone Go CLI that drives the ZCode desktop app (Electron) over the Chrome DevTools Protocol — chat with your coding agent and inspect app status from the terminal. Built with cdp2cli.

概要

— target app ZCode 3.11.2 (Electron 41 / Chrome 146), CDP port 9227, live-verified 2026-09-10. zcodecli is a standalone Go command-line client for the local ZCode Electron app. It drives the app through Chrome DevTools Protocol on port 9227. Read commands call the frozen window.zcode contextBridge methods directly. Chat commands actually drive the agent (create sessions, send prompts, and collect the finished reply) through the renderer's workspace services, which zcodecli reaches by walking the in-page React fiber tree. No hooks are installed and the frozen bridge is never wrapped. The Makefile uses -ldflags="-linkmode=external" to avoid the macOS Go linker LC_UUID issue. Start the app with the local debug port first: Business commands do not restart the app silently. If the debug port is closed, run start first.

README

以下は原文 README の抜粋です。原文を見る。

zcodecli

Auto-generated with cdp2cli — target app ZCode 3.11.2 (Electron 41 / Chrome 146), CDP port 9227, live-verified 2026-09-10.

zcodecli is a standalone Go command-line client for the local ZCode Electron app. It drives the app through Chrome DevTools Protocol on port 9227.

Read commands call the frozen window.zcode contextBridge methods directly. Chat commands actually drive the agent (create sessions, send prompts, and collect the finished reply) through the renderer’s workspace services, which zcodecli reaches by walking the in-page React fiber tree. No hooks are installed and the frozen bridge is never wrapped.

Build

make build

The Makefile uses -ldflags="-linkmode=external" to avoid the macOS Go linker LC_UUID issue.

Development

make fmt
make vet
make test
make build

Use

Start the app with the local debug port first:

./zcodecli start

Business commands do not restart the app silently. If the debug port is closed, run start first.

Chat commands (these drive the agent in the currently open workspace):

./zcodecli chat list
./zcodecli chat show             # most recent messages
./zcodecli chat show  --all       # full history
./zcodecli chat new "reply with the word ok" # create a session, send a prompt, wait for the reply
./zcodecli chat send  "follow up" # continue a session, wait for the reply

chat new and chat send block until the agent finishes its turn and then print the final reply text (not just a submission acknowledgement). A turn that stops on a permission/approval prompt, reports an error, or does not finish within the timeout exits non-zero. Session ids always come from chat list or the chat new output.

Read commands:

./zcodecli status
./zcodecli ssh list
./zcodecli system locale
./zcodecli system device-id
./zcodecli editors list
./zcodecli docker status
./zcodecli docker containers
./zcodecli wsl list
./zcodecli updates status
./zcodecli window state
./zcodecli remote status
./zcodecli desktop activity
./zcodecli community status
./zcodecli explore methods

./zcodecli skill prints the built-in agent guide (compiled into the binary).

Every business command supports --json for single-line JSON. The default output is a human-readable table. Contract mismatches and connection errors exit non-zero.

Stop the debug-enabled app when finished:

./zcodecli stop

Safety

The debug port is a plaintext local control surface for a logged-in application. Keep it closed when not in use. The CLI serializes local CDP operations with a lock and closes its WebSocket after each command.

GitHub で README 全文を見る

推奨ツール

別のキーワードを試すか、フィルタを外してください。

インストール

npx skillfish add williamfzc/zcode-cli
MCP 初心者?mcpskill.org のガイドから始めましょう →