v0.1.2
NAC v0.1.2 makes the web experience easier to navigate, adds safer options for remote operation, and improves the CLI paths used to configure and upgrade an installation.
Highlights
Easier MCP server management
MCP servers now have a dedicated top-bar control that shows how many servers are enabled. The management flow has been reorganized with clearer server details, documentation links, key-value editing, and a mobile-friendly layout. The surrounding session switcher and navigation also fit smaller screens better. (#180)
Complete CLI help and cleaner authentication commands
nac-web --help now exposes the full public command tree, including codex-auth, arcee-auth, and upgrade, with recursive help for each command. Authentication login commands now save credentials and exit instead of unexpectedly opening the dashboard and occupying a server port. (#179, #161)
Explicit remote access
Operators can bind nac-web to a selected non-loopback interface with --allow-remote. Loopback remains the default. Remote binding requires an explicit acknowledgement and includes protections against cross-origin browser mutations; because NAC has no client authentication, it should only be exposed inside an authenticated, encrypted network boundary. (#153)
Opt-in prerelease upgrades
Users who want to test nightly release candidates can run nac-web upgrade --pre-release. Non-interactive use additionally requires --yes; normal upgrades and the standalone installer remain on stable releases. Candidate binaries identify their exact version and source revision. (#184)
Updated Arcee model catalog
MiniMax-M3, Trinity-Mini, and Trinity-Large-Preview have been removed from the seeded Arcee model list. Trinity-Large-Thinking and the remaining supported third-party models stay available. (#157)
Repository issue triage skill
Contributors using compatible coding harnesses can invoke the repository-local triage skill to review open issues, identify duplicates, apply existing labels, request clarification, and group reports by root cause. (#182)
Bug fixes
- Provider failures now redact API keys, authorization values, configured header secrets, redirect credentials, and stream error secrets before events are persisted or messages are logged. (#162)
- Invalid light-model configurations now return the actionable provider or credential cause instead of only
invalid light model settings. (#158) - Long-running servers now evict safe-to-release idle sessions, preventing accumulated SQLite handles from exhausting file descriptors while preserving active, subscribed, and sandbox-backed sessions. (#163)
- Linux process cleanup now uses identity-checked process handles rather than reusable numeric PIDs, reducing the risk of signaling the wrong process and making incomplete cleanup visible. (#160)
Full changelog: v0.1.1...v0.1.2