Skip to content

You choose the OpenAI model; desktop cherry-picks and reverts merge commits - #154

Merged
antonarnaudov merged 2 commits into
mainfrom
feat/ai-pick-your-model
Nov 7, 2026
Merged

antonarnaudov merged 2 commits into
mainfrom
feat/ai-pick-your-model

Conversation

@antonarnaudov

Copy link
Copy Markdown
Contributor

Two follow-ups from the 1.24.0 / 2.9.0 release.

You choose the OpenAI model (extension + desktop)

  • Extension: gitstudio.ai.openai.model* default to blank (were gpt-4o-mini / gpt-4o); the AI panel's OpenAI card no longer comes filled with gpt-4o; Connect asks for a model; a detected /models list is offered, filled in only when it has a single entry (it took the first — alphabetically babbage-002).
  • Existing extension setups on the old defaults keep them: written once as the user's own values, so AI doesn't switch off on update.
  • Desktop: OpenAI and Azure presets seed no model; each model field gets suggestions from ai:models; the add toast says what's left ("…and choose a model"). No retired OpenAI default is swapped for you any more, and migrateRetiredModels never moves a tier onto a blank.
  • Extension provider: OpenAI reasoning ids (o-series, gpt-5+) get max_completion_tokens + reasoning_effort: low instead of max_tokens (HTTP 400). Shared helper moved to @gitstudio/engine/ai/aiCore.

Desktop: cherry-pick / revert a merge commit

  • Was refused with a terminal command. Main now answers with the merge's parents (mergeSides), the bridge asks which side (the extension's words, every parent of an octopus offered) and resends with mainline → -m N. Invalid mainline refused.

Tests: apps/extension/test/aiChooseModel.test.ts (defaults, panel in headless Chrome, keep-former-defaults, wire body), packages/ai/test/retiredDefaults.test.ts, apps/desktop/test/mergeSideBridge.test.ts, real-git cases in gitBridge.ops.test.ts, harness checks a-merge-cherry-pick-… / a-merge-revert-…. npm run verify green locally. 13 locales translated.

🤖 Generated with Claude Code

antonarnaudov and others added 2 commits November 7, 2026 12:51
…hich side

A cherry-pick or revert of one merge commit used to be refused, naming
`git cherry-pick -m 1` to run from a terminal; the extension asks. Now main
answers such a request with the merge's parents (`mergeSides`), and the
bridge asks which side — once, for every door, in the extension's words —
then sends the same request again with `mainline` (-m). Every parent of an
octopus merge is offered; a mainline that is not one of them is refused,
never guessed at.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… product

The extension's OpenAI model settings defaulted to gpt-4o-mini / gpt-4o and
the AI panel's OpenAI card came filled with gpt-4o; the desktop's OpenAI and
Azure presets seeded models too. Now they are blank: the model field lists
what your key can use, Connect asks for one, and a detected list is offered,
never picked from (it took the first, alphabetically).

A setup already running on the old extension defaults keeps them, written
once as its own values, so nothing switches off on update. The desktop no
longer swaps a retired OpenAI default for you, and never moves a tier onto
a blank.

The model you pick is spoken to properly: OpenAI's reasoning ids (o-series,
gpt-5 and later) get max_completion_tokens and low reasoning effort — they
answered the extension's max_tokens with HTTP 400. One helper, shared with
the desktop's provider, in @gitstudio/engine/ai/aiCore.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@antonarnaudov
antonarnaudov merged commit 846ea9e into main Nov 7, 2026
13 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.

1 participant