Skip to content

feat(tui): integrate ServerAuth headers into transport configuration for external served TUI thread#29876

Open
OpeOginni wants to merge 1 commit into
anomalyco:devfrom
OpeOginni:fix/tui-thread-auth
Open

feat(tui): integrate ServerAuth headers into transport configuration for external served TUI thread#29876
OpeOginni wants to merge 1 commit into
anomalyco:devfrom
OpeOginni:fix/tui-thread-auth

Conversation

@OpeOginni
Copy link
Copy Markdown
Contributor

Issue for this PR

Closes #29847

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

  • Only enter external mode from explicit CLI flags: removed the config-derived conditions. Now the TUI stays in internal worker mode unless the user explicitly passes --port, --hostname, or --mdns.

  • Pass auth headers when external mode is used: when the TUI does enter external mode (explicitly requested), it now generates auth headers from ServerAuth.headers() and passes them through to the SDK client and validateSession, just like attach.ts already does.

How did you verify your code works?

Typecheck passes, and tested out running the tui with a password and passing the --hostname and --mdns flags to create an external server instance with the TUI.

Screenshots / recordings

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OPENCODE_SERVER_PASSWORD breaks TUI startup with --mdns or --hostname

1 participant