You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A dependency-free port-light command-line client with doctor, check,
atomic reserve, and token-authenticated release commands. It supports
human or versioned JSON output, stable exit categories, Basic Auth, agent
tokens, custom CA bundles, one-hour leases by default, explicit persistent
reservations, and self or all-peer checks.
Private local reservation-token storage partitioned by server and port, with
stateless JSON/stdin/environment alternatives for automation. The published
container includes the port-light command, and the Python package installs
with pipx or uv tool; releases attach a matching wheel to the same tag.
Container-side tokens default to persistent /data/cli-state storage.
/api/meta now advertises named client capabilities. Port suggestions accept require_count=true for an all-or-none requested count.
Changed
The MCP stdio server and CLI now share one tested HTTP client, response
validator, and error model. Direct python /path/to/mcp/server.py startup
remains supported from outside the repository.
The backend, MCP server, CLI, Python package, and release gate now read one
product version. JSON mode also covers argument-parser failures, and long
options no longer accept unstable abbreviations.
CI lints and tests the command-line package alongside the server, including a
live server round trip for doctor, check, reserve, and release. It installs
the built wheel in an isolated environment and builds the image to smoke-test
both the CLI and MCP entry points.
Fixed
CLI and MCP responses now reject mismatched ports, invalid diagnostic data,
malformed occupancy data, and unverified reservation scopes. Exact CLI
reservations require the server capability that guarantees all-or-none
allocation, preventing an older server from silently creating a partial
reservation.
CLI and MCP environment configuration now uses one shared client factory.
Local token-directory creation failures use the documented error category,
and unexpected MCP failures no longer expose internal exception details.