Access
The terminal client gets its own door
The command line client talks to an endpoint of its own now, with its own token, and ZeroLog no longer reads the credential your own agent uses.
ZeroLog serves the terminal client on its own path, /api/cli, with a token
type of its own. Requests carry an mhc- token instead of a browser session, so
the client no longer depends on a cookie it cannot hold.
The first route behind it speaks the OpenAI chat format, at
POST /api/cli/v1/chat/completions. Same provider pool, same spend limits, same
billing as the hosted path.
Credentials
If you connect your own Claude, Codex or Gemini account, its configuration lives in a directory of yours on the NAS now, shared with your agent container. ZeroLog does not read that credential.
The documentation for the bring-your-own-agent page and the CLI page described both points incorrectly. It has been corrected.
A claim we removed
The landing page imitated the thinking indicator of another product. It is gone.