@glanger/glanger-cli
v0.1.9
Published
CLI for configuring local OpenClaw, Claude, and Codex settings
Readme
@glanger/glanger-cli
CLI scaffold for configuring local OpenClaw, Claude, and Codex settings.
Commands
npx @glanger/glanger-cli show
npx @glanger/glanger-cli show codex
npx @glanger/glanger-cli set codex --url http://127.0.0.1:8000 --key sk-xxx --model gpt-5.4
npx @glanger/glanger-cli set claude --url http://127.0.0.1:8000 --key sk-xxx
npx @glanger/glanger-cli set openclaw --url http://127.0.0.1:8000 --key sk-xxx --model gpt-5.4
npx @glanger/glanger-cli remove codex
npx @glanger/glanger-cli setup --codex-url http://127.0.0.1:8000 --codex-key sk-xxx --claude-url http://127.0.0.1:8000 --claude-key sk-xxx
npx @glanger/glanger-cli setup --codex-url http://127.0.0.1:8000 --codex-key sk-xxx --openclaw-url http://127.0.0.1:7000 --openclaw-key sk-yyyManaged files
- Codex:
~/.codex/config.toml - Claude:
~/.claude/settings.json - OpenClaw:
~/.openclaw/openclaw.json
Setup behavior
setup only updates the targets you configure explicitly. Passing --codex-url and --codex-key will not modify OpenClaw unless you also pass --openclaw-url and --openclaw-key.
Architecture
This repo mimics the yunyi-cli package shape:
- root package exposes the
bin - root
run.jsresolves the current platform package - platform packages contain the actual executable script
The platform package currently still runs Node.js code. That keeps the publish layout similar to yunyi-cli without adding native build complexity.
Local development
node scripts/build-platform-packages.mjs
node run.js showBefore publishing, change the package names to your own unique npm scope or package name.
