bliss/bliss-cli
Your Name e7064a7c6a bliss-cli: detect failed logins instead of caching anon sessions
The server issues a connect.sid cookie on every response, including a
rejected login (which re-renders the form as 200). login() treated any
returned cookie as success, so bad creds silently cached an anonymous
session and the CLI stayed logged out with no warning — and since it only
re-authenticates on a 401 (which the server never sends), the stale cookie
was never refreshed.

Trust the redirect status instead (302 = success, 2xx = rejected) and throw
a clear error with the HTTP code on failure. Add a `bliss login` command
that forces a fresh login past any stale cookie.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-08-21 10:17:28 -04:00
..
live-editor inspector updates 2026-08-07 18:40:04 -04:00
bliss bliss-cli: detect failed logins instead of caching anon sessions 2026-08-21 10:17:28 -04:00
client.js bliss-cli: detect failed logins instead of caching anon sessions 2026-08-21 10:17:28 -04:00
SKILL.md doc to prefer literal html injection 2026-08-08 17:57:14 -04:00