This repository was archived by the owner on Aug 6, 2026. It is now read-only.
fix(agent): Put most capable Claude at top - #3658
Merged
Merged
Conversation
Invert MODEL_FAMILY_ORDER so the family order is least-capable first. The picker opens upward (side="top") from the composer, so items later in the list render nearest the trigger and read as the top of the menu — this lands the most-capable family (Fable) on top. Update the picker-order tests accordingly. Generated-By: PostHog Code Task-Id: ab97f429-92f1-4d95-8a32-ad67d14df18d
|
😎 Merged manually by @charlesvien - details. |
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
Twixes
marked this pull request as ready for review
July 21, 2026 19:46
Contributor
|
Reviews (1): Last reviewed commit: "fix(agent): put Fable on top of the mode..." | Re-trigger Greptile |
charlesvien
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Human tldr: Agent picker was showing Haiku first, then Sonnet, then Fable - not the most intuitively as a hierarchy.
Problem
The Claude model picker listed families most-capable-first in the DOM. But the picker dropdown opens upward (
side="top") from the composer, so the first list item renders at the far top of the popup and the last item sits nearest the trigger where the eye lands — leaving the strongest model (Fable) visually stranded away from where you look. Raised in a Slack thread (link).Changes
Inverted
MODEL_FAMILY_ORDERto least-capable-first (haiku → sonnet → opus → fable). Because the menu opens upward, this renders Fable nearest the trigger — the visual top of the menu. Updated the picker-order unit tests to match.How did you test this?
pnpm --filter @posthog/agent test— thecompareModelsForPickerandapplyAvailableModelsAllowlistsuites pass with the new ordering (641 tests passed).Automatic notifications
Created with PostHog from a Slack thread