Build from source when contributing or testing unreleased changes.
Build the CLI
Install mise, then clone the public repository:
git clone https://github.com/vibeke-ai/vibeke.git
cd vibeke
mise install
mise run build
Use the debug binary in this shell:
export PATH="$PWD/target/debug:$PATH"
vibeke --version
vibeke doctor
Run mise run test for tests and mise run ci for the full local checks.
mise run dist creates unsigned development artifacts and updates the local remote-install cache.
See releases and reproducible builds before using these artifacts remotely.
Measure terminal performance
Run the native terminal latency probe from a source build:
vibeke debug tui-latency --n 200 --json
The probe starts an isolated server and the native TUI in a pseudo-terminal.
It measures the time from a key to visible output through the full client path.
It reports latency percentiles and changes in render counters.
The host terminal is emulated, so physical display latency is excluded.
Ten warm-up samples and the 20 ms gap between keys are excluded.
The probe uses its own session and configuration.
Compare runs from the same build profile on the same machine.
Use --binary /path/to/another/vibeke to measure another build with the same probe.
vibeke server status --json includes render wakeups, timer wakeups, row projections,
and pane frame counts under render.
Row projections count full visible-row conversions made by render sessions.
Other readers can populate the shared row cache first.
Web and desktop development
See the web guide and desktop development guide.
The product website reads its documentation directly from docs/site/src/.
Register new chapters in SUMMARY.md and web/apps/site/content/manifest.ts.
CLI, configuration, and API references are generated from source. Use the regeneration instructions in releases.
Next steps
- CLI reference for the commands you can test.
- Release verification before you use development artifacts remotely.
- Troubleshooting for how to collect a debug bundle.