Skip to content

fix(gui): remove non-actionable API-key rows from Accounts tab#231

Merged
Ingwannu merged 1 commit into
lidge-jun:devfrom
Wibias:codex/fix-accounts-tab-dead-rows
Jul 22, 2026
Merged

fix(gui): remove non-actionable API-key rows from Accounts tab#231
Ingwannu merged 1 commit into
lidge-jun:devfrom
Wibias:codex/fix-accounts-tab-dead-rows

Conversation

@Wibias

@Wibias Wibias commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Problem

The Accounts tab in the add-provider modal was showing API-key providers (those with hasApiKey or keyOptional) as rows with no buttons or actions. The ProviderCatalog component renders kind: "key" rows with null in the actions column, making them dead weight that confuses users.

Fix

Removed the third group from addModalAccountRows in gui/src/pages/Providers.tsx. API-key providers already appear in the Free/Paid tabs where they can actually be configured. They don't belong in the Accounts tab, which is meant for OAuth and Codex-forward account management.

Verification

  • bun x tsc --noEmit passes in gui/
  • The Accounts tab now only shows actionable rows: Codex-forward accounts (manage/login) and OAuth providers (login/logout)

The Accounts tab in the add-provider modal was showing API-key providers
(hasApiKey or keyOptional) as rows with no buttons or actions. The
ProviderCatalog renders kind:'key' rows with null in the actions column,
making them dead weight that confuses users.

API-key providers already appear in the Free/Paid tabs where they can be
configured. Remove them from the Accounts tab entirely.

Copy link
Copy Markdown
Owner

Reviewed against current dev. This is a small, correct UI cleanup: API-key rows in the Accounts tab have no actionable account controls, while API-key management remains in the provider flow. Full CI is green and no security concern was found. Merging into dev.

@Ingwannu
Ingwannu merged commit 4d61025 into lidge-jun:dev Jul 22, 2026
8 checks passed
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.

2 participants