Repository navigation
Dev Companion 0.4.0 — developer presence and incident workflows
Pre-releaseA developer workflow that stays available after chat closes
This free Linux x86_64 preview adds:
- Opt-in login presence and a work desk for declared goals, unfinished work, incidents and reminders.
- An explicitly observed Bash session (
dot shell) with actual failure output and exit status. - An optional VS Code adapter for consented diagnostics with reported file/line/column and saved state.
- Incident follow-through: original evidence → optional local-model correction → review → explicit application → relevant current check.
- Durable reminders, snooze/done, quiet periods and optional focus/break timers.
- Explicit English voice turns using local Whisper.cpp and Piper after one-time setup; no continuous microphone or cloud fallback.
Evidence
67 Rust integration tests, six Node adapter tests, formatting and Clippy passed. The optional installed-audio test passed separately. A real local 4B model prepared a reviewed addition correction; the unchanged named check passed on current code. A returning generated-audio voice turn used that saved evidence. A desktop reminder was delivered with chat closed. These are scripted fixtures, not a general debugging benchmark; the v0.4 evaluations were not network-isolated.
Install and update
Download the CLI archive and SHA256SUMS; the optional editor adapter is a separate VSIX. Verify downloaded files with sha256sum --check --ignore-missing SHA256SUMS. Follow the setup/update guide for installation, explicit per-project enablement and service restart after an update. There is no built-in dot update command.
The static CLI archive has four files: binary, application license, dependency notices and quickstart. The VSIX includes the small JavaScript adapter; the Rust application source remains private. Model weights and private data are not included. Initial downloads need internet. Inference is local and optional for presence/reminders. Small models can make mistakes; inspect diffs and run relevant checks.
Physical microphone selection/playback comfort and real developer usefulness still need hands-on feedback. Voice is explicit and does not execute transcribed commands. Presence sees enabled adapters, not arbitrary terminals or screens.