Skip to content

[Bug]: Auto-generated commits fail when user lacks access to hardcoded gpt-5.3-codex model #1165

Closed

Description

@AriajSarkar

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

  1. Start the T3 Code app.
  2. Open a project with unstaged/staged Git changes.
  3. Select a specific model in the chat UI model picker at the bottom (e.g., gpt-5.2-codex).
  4. Click the "Auto Commit" or "Commit & Push" button in the Git actions block.

Expected behavior

The auto-generated commit message should be created using the model selected in the chat UI (gpt-5.2-codex), as that is what the user has chosen and verified they have access to.

Actual behavior

The app ignores the selected model and attempts to generate the commit message using a hardcoded gpt-5.3-codex model.

Impact

Major degradation or frequent failure

Version or commit

main

Environment

Provider/Model: Codex (gpt-5.3-codex hardcoded, user attempted gpt-5.2-codex)

Logs or stack traces

// The model is currently hardcoded in apps/server/src/git/Layers/CodexTextGeneration.ts 

const CODEX_MODEL = "gpt-5.3-codex";
// ...
yield* childProcess.spawn("codex", [
  "prompt",
  "--model",
  CODEX_MODEL, // Hardcoded, ignores the model selected in the chat UI
// ...

Screenshots, recordings, or supporting files

image.png

Workaround

Currently, the only workaround is to manually type the commit messages instead of relying on the auto-generate button, or use the chat to write the commit message and copy-paste it.

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Mar 17, 2026
  2. AriajSarkar commented on Mar 17, 2026

    @AriajSarkar
    ContributorAuthor

    Another thought: considering cost and usage limits,
    we should probably default to the lowest-cost model (based on the user's provider) that has an adequate context window.
    Since this is just for generating commit messages, we don't necessarily need top-tier models for this specific task.

    re: For example, if the user is using a heavy codex model (e.g. gpt-5.4 on xhigh) for chat,
    we should use a lower-cost/faster model (e.g. gpt-5.4-mini, ⚠️ if it exists in the codex CLI!) for git commits.

  3. added a commit that references this issue on Mar 17, 2026
    5a884a7
  4. changed the title [-][Bug]: Auto-generated commit messages use hardcoded `gpt-5.3-codex` model instead of respecting chat selection[/-] [+][Bug]: Auto-generated commits fail when user lacks access to hardcoded gpt-5.3-codex model[/+] on Mar 17, 2026
  5. UtkarshUsername commented on Mar 18, 2026

    @UtkarshUsername
    Contributor

    Fixed by #1171

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions