fix: gateway password auth + login screen with auto-lock #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's in here
Two things rolled into one branch:
1. Gateway password auth fix (previous commit)
CLAWDBOT_PASSWORDenv var for gateway password auth modehandleChallengeearly return when no token setok: falseconnect responses instead of silent timeoutWS_NO_BUFFER_UTIL=1support for bundled ws environmentspython3 make g++to Dockerfile for arm64 native module compilation2. Login screen + auth system (new)
Right now anyone with the URL can hit /monitor and /workspace. This adds a proper login screen so only people with the password or API token can get in.
What you get:
Zero new dependencies. Uses built-in
crypto.randomUUID()andcrypto.timingSafeEqual().Uses existing
CLAWDBOT_PASSWORD/CLAWDBOT_API_TOKENenv vars — no new config needed.Test plan
CLAWDBOT_PASSWORDset, verify gateway auth works