[codex] Improve API key scope filtering

[riderx]

Summary (AI generated)

• Redesigned API key organization and app scopes as compact clickable chips to prevent long table rows.
• Added searchable overflow popovers for +N scope lists so users can inspect and choose hidden orgs/apps.
• Reused the shared table filter control for org/app scope filtering, including custom labels and URL filter cleanup.
• Defaulted the API keys table to the currently selected organization when no scope filter is already set.
• Removed a now-unused API key scope formatting helper so dead-code checks stay clean.

Motivation (AI generated)

API keys with access to many apps made the page hard to scan and caused very long table content. The page also needed scope filtering to follow the shared table component pattern and start from the user’s current organization context.

Business Impact (AI generated)

This improves API key management usability for teams with many organizations and apps, reducing friction when auditing or changing key access. It also keeps the console experience consistent with the rest of the product’s table filtering behavior.

Test Plan (AI generated)

• bunx eslint src/services/apikeys.ts src/pages/ApiKeys.vue src/components/DataTable.vue
• bunx oxlint src/services/apikeys.ts src/pages/ApiKeys.vue src/components/DataTable.vue
• bun run lint:deadcode
• bun run typecheck:frontend
• bun run lint
• bun run build
• Commit hook typechecks: bun run cli:typecheck && bun run typecheck:backend && bun run typecheck:frontend
• Browser smoke check opened /apikeys; local session redirected to login with no page-load console errors.

Generated with AI

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

@riderx, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 27 minutes and 14 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 83fa0223-9ad4-45b2-9998-6d4e348e4a27

📥 Commits

Reviewing files that changed from the base of the PR and between 459c065 and 3bcc76e.

📒 Files selected for processing (4)

• messages/en.json
• src/components/DataTable.vue
• src/pages/ApiKeys.vue
• src/services/apikeys.ts

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing codex/apikeys-scope-filter-ui (3bcc76e) with main (459c065)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud