0.9.8.44 is a user-experience release: the binary drops its trailing d,
the dashboard gains a Settings tab and per-chain storage visibility, and
mentisdb now loads configuration from .env files so you can keep
project-local settings out of your shell profile.
Breaking change: the installed binary is now mentisdb,
not mentisdbd. All documentation, CI artifacts, install scripts,
and TUI references have been updated. If you have scripts or aliases that
call mentisdbd, update them to mentisdb.
mentisdbd → mentisdb. Every reference in docs, tests, CI, install scripts, and the TUI has been updated. cargo install mentisdb produces mentisdb.MENTISDB_* environment variables in a table with type-aware controls (checkbox for booleans, number input for ports, text for strings). Each row shows current value, default, and description. "Reset to Default" per row. "Apply Settings" persists changes to a .env file and hot-reloads auto_flush immediately. Network and storage changes show a restart-required flag..env file in the current working directory at startup. Shell env vars take precedence. The file is silently ignored when absent, so you can commit a template .env.example and keep real values in .gitignore-d .env files.[10 KB] /path/to/chain.tcbin). The running status line now includes the daemon PID so you can identify the process when multiple instances are running.| Gate | Result |
|---|---|
cargo fmt -- --check | Passed |
cargo clippy --all-features -- -D warnings | Passed |
cargo test --all-features | Passed (257 tests, 80 doc-tests) |
| GitHub CI | Passed (x86_64/aarch64 macOS, x86_64/aarch64 Linux, Windows) |
| LoCoMo benchmark | R@10 = 71.80% (single 75.80%, multi 57.20%) |
cargo install mentisdb --force
No manual migration is required. Existing chain files, skill registries, and
agent identities continue to work unchanged. Scripts that reference
mentisdbd should be updated to mentisdb.