feat: setup-token auth — no more throwaway container login#249
Open
woltspace-jerpint[bot] wants to merge 1 commit into
Open
feat: setup-token auth — no more throwaway container login#249woltspace-jerpint[bot] wants to merge 1 commit into
woltspace-jerpint[bot] wants to merge 1 commit into
Conversation
…side auth The old auth flow spawned a throwaway Docker container, told users to type /login, then /exit. Clunky and error-prone. New flow offers three paths during woltspace init: 1. Claude Pro/Max/Team → runs 'claude setup-token' on host, stores CLAUDE_CODE_OAUTH_TOKEN in .env (recommended) 2. API key → paste sk-ant-..., stored as ANTHROPIC_API_KEY in .env 3. Skip → instructions for manual setup later Also: - Detects existing auth (token, API key, or credentials.json) and skips - Falls back to API key prompt if claude CLI isn't installed - Updated .env.example with Claude Code auth section Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The old auth dance (spawn container → type /login → /exit → pray) is gone. Now
woltspace initauthenticates on the host before the container ever starts.Three paths:
claude setup-tokenon host, browser opens, token saved to.envasCLAUDE_CODE_OAUTH_TOKENsk-ant-..., saved asANTHROPIC_API_KEYin.env.envlaterWhat changed
woltspaceCLI — rewrote the auth section ofinit. Detects existing auth (token, API key, or credentials.json) and skips if already set. Falls back to API key prompt ifclaudeCLI isn't installed..env.example— addedCLAUDE_CODE_OAUTH_TOKENsection, reorganized to show auth first.How it works
claude setup-tokengenerates a long-lived OAuth token (~1 year) that goes into.env--env-file— every Claude Code session inside inherits the env varentrypoint_setup.pyalready handleshasCompletedOnboarding— no changes needed thereANTHROPIC_API_KEYworks the same way — double duty for both Claude Code auth and bot LLMTest plan
woltspace init→ option 1 (setup-token) → browser opens, token captured, stored in .envwoltspace init→ option 2 (API key) → key stored in .envwoltspace init→ option 3 (skip) → shows manual instructionswoltspace initwith existing auth → skips auth entirelywoltspace initwithoutclaudeCLI → falls back to API key prompt🦫 no more /login gymnastics.
🤖 Generated with Claude Code