Skip to content

Navigation Menu

Sign in
Sign up

Repository files navigation

Command Code tooling

Cargo workspace. One shared logic crate (cmduse-core) powering two thin UIs; the opencode plugin is a separate TS package. The pre-workspace 0.1.x tree is archived read-only in legacy/v0.1/.

Component Crate/dir What
cmduse CLI cli/ (cmd-usage, bin cmduse) Terminal dashboard: plan/credits/windows, watch mode, reports, statusline. Published on crates.io / Homebrew.
Zed extension zed-ext/ (command-code-usage) /cmd-usage slash command in Zed assistant panel (markdown dashboard). WASM build.
Shared core core/ (cmduse-core) Plan table, dates/ISO helpers, window/pace math, money/compact/pct/rel_time formatting. Single source — edit here, both UIs pick it up.
opencode plugin opencode/ @jeffreyjyz/opencode-command-code — Command Code as an opencode provider (live model list, plan gating). No core dep (different language).

Build

cargo build # all Rust crates
cargo test # core + cli + zed-ext (host tests)
cargo clippy --all-targets -- -D warnings
cargo build -p command-code-usage --target wasm32-wasip1 --release # Zed ext
cd opencode && bun install && bun test

Why the split

0.1.x duplicated pure logic across two Rust crates (e.g. the burn-rate pace gate was patched in two files for one bug). The workspace moves all shared math into core/; cli/ and zed-ext/ keep only their presentation + I/O.

About

Zed extension and cmduse CLI for live Command Code usage: plan, credits, 5-hour and weekly windows, per-window elapsed, billing period stats. Rust, no bloat.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

AltStyle によって変換されたページ (->オリジナル) /