Skip to content

Comments

AskAi: add header button to Codex and centralize config per build type#2772

Open
reakaleek wants to merge 1 commit intomainfrom
feature/codex-ask-ai
Open

AskAi: add header button to Codex and centralize config per build type#2772
reakaleek wants to merge 1 commit intomainfrom
feature/codex-ask-ai

Conversation

@reakaleek
Copy link
Member

What

  • Add an Ask AI button to the Codex header and extract shared flyout logic into a reusable hook
  • Introduce a centralized config that controls AI provider defaults and suggestions per build type (Codex vs Assembler)

Why

  • Codex needs its own Ask AI entry point in the header, separate from the floating action button used in Assembler
  • AI provider selection was hardcoded in multiple places, making it difficult to switch between providers per build type

Notes

  • The flyout body, keyboard shortcuts, and API health check are now shared via a useAskAiFlyout hook
  • Codex forces AgentBuilder as the AI provider; Assembler continues to default to LlmGateway
  • Console logger now prints exception details when available

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@reakaleek reakaleek requested a review from a team as a code owner February 23, 2026 22:27
@reakaleek reakaleek requested a review from Mpdreamz February 23, 2026 22:27
@reakaleek reakaleek changed the title AskAi: add header button and centralize config per build type AskAi: add header button to Codex and centralize config per build type Feb 23, 2026
@reakaleek reakaleek self-assigned this Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant