OAuth login URL is not shown when running remote server with auth
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Bug description
When running
thv run --remote-auth-skip-browser
I expect to see the log
Please open this URL in your browser:
However, the foreground process exits too quickly and it's not possible to see the log unless I open the .log file.
This makes it difficult to log in to remote servers when my shell doesn't have permissions to open a browser.
Steps to reproduce
thv run context7-remote --remote-auth-skip-browser
Expected behavior
I expect to see the login URL printed:
Please open this URL in your browser: https://context7.com/api/oauth/authorize?client_id=...
Or another mechanism that allows me to continue the OAuth flow.
Actual behavior
thv run return immediately. The log with the URL is only available when searching through the log file.
Additional context
This problem becomes more painful given the 30s timeout when connecting to remote servers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the thv run path handling --remote-auth-skip-browser and trace how the OAuth URL is logged for remote servers. Reproduce with thv run context7-remote --remote-auth-skip-browser; done means the foreground process presents a usable login URL or another way to continue the OAuth flow before the connection timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100