Skip to content

Conversation

@Raviguntakala
Copy link
Contributor

@Raviguntakala Raviguntakala commented Jan 5, 2026

Problem

GitHub Copilot Enterprise authentication is missing in TUI /connect command. The CLI (auth login) supports enterprise login with deployment type selection and conditional prompts, but TUI /connect has no option for enterprise authentication at all.

Solution

Added enterprise authentication support to TUI /connect by implementing the same prompt collection logic as CLI:

  • Added prompt collection loop to gather user inputs (deployment type, enterprise URL, etc.)
  • Implemented conditional prompt logic for enterprise-specific fields
  • OAuth callback now returns actual provider ID (github-copilot-enterprise vs github-copilot)

Changes

  • dialog-provider.tsx - Added prompt collection before authorization
  • auth.ts, server.ts - Return actual provider ID from OAuth callback
  • dialog-model.tsx - Filter by provider.id instead of model.providerID
  • provider.ts - Check both regular and enterprise auth for github-copilot plugin

Testing

  • /connect with GitHub Copilot (public)
  • /connect with GitHub Copilot Enterprise
  • ✅ Enterprise models display correctly

Note: If these changes are approved, I will raise a separate PR for Desktop app support.

Before :

Screen.Recording.2026-01-05.at.11.12.39.PM.mov

After :

Screen.Recording.2026-01-05.at.11.19.25.PM.mov

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

The following comment was made by an LLM, it may be inaccurate:

Duplicate PR Search Results

No duplicate PRs found. The searches returned the PR itself (#6974) and one tangentially related PR about IDE integration, but no other active PRs addressing the same GitHub Copilot Enterprise authentication feature in the TUI /connect command.

Summary:

This appears to be a new, unique feature addition for TUI support of GitHub Copilot Enterprise authentication. You're good to proceed.

@Raviguntakala Raviguntakala force-pushed the feature/connect-deployment-type branch 2 times, most recently from 69e66a7 to 3ecdd17 Compare January 8, 2026 06:32
@Raviguntakala Raviguntakala force-pushed the feature/connect-deployment-type branch from 3ecdd17 to 4448c52 Compare January 8, 2026 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant