jia-ethan/zcode-keysmith — explained in plain English
Analysis updated 2026-05-18
Install a persistent custom system prompt into the ZCode desktop app without modifying the app itself.
Preview exactly which files will be written before confirming an install with a dry-run step.
Verify that the custom system role was actually loaded the next time ZCode starts an agent session.
Cleanly uninstall the managed files and restore ZCode's default startup behavior.
| jia-ethan/zcode-keysmith | alibaba/omnidoc-tokenbench | arccalc/dwmfix | |
|---|---|---|---|
| Stars | 43 | 43 | 43 |
| Language | Python | Python | Python |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 3/5 | 3/5 | 2/5 |
| Audience | developer | researcher | general |
Figures from each repo's GitHub metadata at analysis time.
Requires the ZCode desktop app already installed on macOS and Python 3.10 or later.
zcode-keysmith is a small Python installer that patches how the desktop app ZCode starts its background agent process on macOS. Instead of changing the ZCode app itself, it points ZCode at a wrapper script that loads a cached copy of ZCode's own runtime, then swaps in a custom system prompt file before that runtime launches. The end result is that a Markdown file you control gets injected as the system message every time ZCode starts a new agent session, without modifying the original app bundle. The tool works by reading two environment variables that ZCode already checks when it starts its agent-server process, and redirecting one of them to a wrapper script installed under a hidden folder in your home directory. That wrapper reads ZCode's bundled runtime file, caches a modified copy that points to your custom system-role file, and then launches that cached copy using ZCode's own Electron process, preferring the internal Helper executable so the background process does not show up as a second ZCode icon in the Dock. Installation is done from the command line with a dry run step first, so you can see exactly which files will be written before confirming. Files land under a .zcode-keysmith folder in your home directory, plus a macOS LaunchAgent so the same environment variables persist across logins. The installer explicitly states it does not read, store, or print any API keys, tokens, or provider settings, all of which stay managed by ZCode itself. After installing, you quit and reopen ZCode, start a new task, and run a verify command that checks whether the wrapper was actually invoked. The README also documents a doctor command for checking installation status, an uninstall command that backs up and removes the managed files, and a logging file that records each wrapper start with a timestamp and process ID but no secrets. The project is part of a small family of similar keysmith tools the same author built for other AI coding tools like Codex CLI and Claude Code. It is written in Python 3.10 or later and released under the MIT license.
A macOS installer that redirects the ZCode desktop app to load a custom system prompt file every time it starts a new agent session.
Mainly Python. The stack also includes Python, macOS, LaunchAgent.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.