Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

improvement: authentication synchronization between terminal and browser

Open
#121 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
authentication, cli

Research direction

Start at the supercode login command and trace the Y/N prompt and TUI polling path. Inspect how the CLI reads authorization state, then reproduce the manual-browser-before-prompt sequence; done means an already-completed authorization is detected before polling, while incomplete authorization still follows the existing polling flow.

Written by the indexing model from the issue text.

Description

Description

  1. While running the supercode login command, the CLI prompted me with a Y/N question asking whether to open the browser automatically.
  2. Before responding to the prompt, I manually copied the authentication URL and completed the authorization flow in the browser.
  3. After returning to the terminal, there was no synchronization between the web app and the CLI.
  4. I then selected No, after which the TUI started polling for the authorization response and continued polling indefinitely.

Expected Behavior

If the user completes the authorization flow manually before responding to the Y/N prompt, the CLI should first check whether the user has already been authenticated.

Suggested flow:

  1. Perform a direct database/auth state check to see if authorization has already been completed.
  2. If authorization is not found, start polling for the authentication response.

This would prevent unnecessary polling and ensure that manual authorization flows are handled correctly.

Screenshots:

Image
Dominant language
TypeScript
Stars
214
Forks
41
Avg merge
2h 26m
Merged PRs (30d)
34

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yashdev9274/supercli

All issues in yashdev9274/supercli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.