[Bug]: Expanding the OpenCode provider does not reveal its models without manual scrolling

[szafranski]

Before submitting

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

Area

apps/mobile

Steps to reproduce

1. Open a thread in the T3 Code iOS app.
2. Open the model and session settings sheet.
3. Locate the OpenCode provider row showing 8 available models.
4. Tap the OpenCode row to expand it.
5. Look at the sheet before scrolling, then scroll down.

Expected behavior

The OpenCode models appear directly below the provider row. If they do not fit on screen, the sheet scrolls enough to show at least the first model or indicates that new content was added below.

Actual behavior

The row switches to its expanded state, but no models are visible and the settings below it stay in place. The models only appear after scrolling further down, with no on-screen sign that the expansion added content. The provider looks empty or broken.

Impact

Minor bug or occasional failure

Version or commit

T3 Code iOS app 1.0.3

Environment

iPhone 13 Pro, iOS 26.6.1, OpenCode provider with 8 models

Logs or stack traces

No relevant logs.

Screenshots, recordings, or supporting files

Screenshots showing the collapsed and expanded states will be attached.

Workaround

Scroll further down in the sheet after expanding OpenCode.

[szafranski]

Screenshots:

[juliusmarminge]

Triage

Confirmed on current main (09aac71563c66a4f65f6fbe701aa9596cb677767). Real iOS model-sheet bug. Expanding OpenCode flips the disclosure chevron, but the newly inserted models stay off-screen and the Options block stays visually glued to the provider row. The reporter’s screenshots match that exact state.

This is still present in the current ThreadSettingsSheet. Shipping 1.0.4 in apps/mobile/app.config.ts does not change the expand/scroll path. Not already fixed.

What happened

On T3 Code iOS 1.0.3 (iPhone 13 Pro, iOS 26.6.1), opening Thread settings with Codex selected and OpenCode collapsed (badge 8) then tapping OpenCode expands the row, but no OpenCode models appear. Reasoning / Context Window / Fast Mode / Service Tier / Runtime stay immediately under the header. The models only show after scrolling further down. There is no scroll indicator or other hint that content was added.

Diagnosis

Mobile Thread settings is one AnimatedLegendList in apps/mobile/src/features/threads/ThreadSettingsSheet.tsx. Catalog rows and the Options card share that list:

• provider header
• that provider’s models (omitted while collapsed)
• next provider…
• one tall options item (Reasoning, Context Window, Fast Mode, Service Tier, Runtime)

OpenCode is not a primary harness. Only claudeAgent, codex, and antigravity start expanded:

const PRIMARY_PROVIDER_DRIVERS: ReadonlySet<string> = new Set([
  "claudeAgent",
  "codex",
  "antigravity",
]);

That default is intentional (large OpenRouter-style catalogs). Starting folded is not the bug. The bug is that a user expand does not reveal the new rows.

toggleProvider only flips providerExpansionOverrides. It does not scroll. The list has no ref and never calls scrollToIndex. When OpenCode opens, eight model items are spliced in above the already-visible Options item. Scroll offset is left alone, and showsVerticalScrollIndicator={false}, so the sheet looks unchanged except for the chevron (and the collapsed count disappearing).

Two list settings make that worse for a last-or-near-last secondary provider sitting just above Options:

1. estimatedItemSize={48} is right for a model row (min-h-11) and wrong for the Options item, which is several settings rows plus section chrome.
2. maintainVisibleContentPosition is { data: false, size: true }. The comment says catalog mutations should use native bounds, and size changes should stay put. Inserting several rows above a much-taller-than-estimated Options item is exactly the case where LegendList keeps the already-painted Options block stable and leaves the new models outside the viewport.

Same navigator is used for an existing thread and New Task, so both entry points pick this up. Android uses the same list; not confirmed in-device here, but likely the same. Web is a different picker (ProviderModelPicker / sidebar + list), not this accordion, so web is out of scope.

I did not run the iOS simulator in this environment. The screenshots plus the current list construction are enough to treat this as confirmed.

Suggested fix

Keep OpenCode (and other secondaries) collapsed by default. Do not add opencode to PRIMARY_PROVIDER_DRIVERS as the fix; that only hides the bug for small OpenCode catalogs and fights the “don’t bury the list” rule.

On expand, scroll the first newly revealed model (or the provider header with a viewPosition / offset that leaves room below it) into view via LegendList scrollToIndex. Give the list a ref to do that.

Also give options a real estimated size (getEstimatedItemSize / getFixedItemSize, same idea as ThreadFeed). A 48px estimate for a ~300px card is why the rows below a just-expanded header fail to land on screen.

Optional: show the vertical scroll indicator while the catalog overflows, or at least after an expand that adds off-screen rows. Today showsVerticalScrollIndicator={false} plus a static Options block is why the provider looks empty.

Tests

providerSectionIsCollapsed is already the pure disclosure helper and is untested. Cover: primary/selected start open, other providers start closed, a tap inverts that, search/filter forces open.

Do not mount ThreadSettingsSheet to assert scrollToIndex wiring. If the expand helper returns a target index, unit-test that: collapsed OpenCode under an expanded Codex catalog should point at the first OpenCode model after toggle.

Related

• Not a duplicate of #9350. That was desktop hide/favorite preferences not applying on mobile. Different bug, already closed.
• Not a duplicate of discussion #7337. That was missing upstream provider labels on OpenCode models, fixed in #8573. The models here exist; they just are not scrolled into view.
• #8072 grouped the web OpenCode picker by vendor. Different surface.
• #7562 is about sub-provider labels, not expand/scroll.

Workaround

Scroll down after expanding a secondary provider. Searching the catalog also forces sections open (isNarrowed), which is a usable bypass if the user knows a model name.

Severity / labels

Minor, but it makes OpenCode look empty/broken on a common iPhone viewport (Codex open, OpenCode next, Options filling the rest). Same failure for any non-primary, non-selected provider in that position (Cursor, Grok, OpenRouter, a second OpenCode instance).

Labels: add via-triage, bug. No needs-triage on the issue today.

Filed by: Cursor Grok 4.6 via cloud issue triage

[juliusmarminge]

Native verification update, September 5, 2026: I could not reproduce the missing rows in the available current-code setup. This is a partial check, not proof that the reported iPhone 13 Pro failure is fixed.

I tested the mobile JavaScript at be7796d8. The mobile code is unchanged on the latest fetched main, 485782b2. On an iPhone 17 Pro Max simulator running iOS 26.5, with a reused development binary and an isolated catalog of three Codex and eight OpenCode models, both expansion attempts displayed all eight OpenCode rows before scrolling. Manual scrolling then reached all options. No provider turn or account call was made.

There are important differences from the report:

• Current existing-thread settings only offer that thread's provider. I exercised the shared picker through New Task, where both groups are available.
• Current Codex options expose Fast through Service Tier, rather than the older separate Fast Mode row. The options card is shorter.
• This is not the reported physical device, iOS version, or a fresh native build.

The earlier source-only diagnosis is not a substitute for a matching reproduction. I am leaving this open. A retest on a current build with its exact version and whether this occurs in New Task or an existing thread would help narrow the remaining difference.

Collapsed:

Expanded, before any scrolling:

After manual scrolling:

GPT 6 Astra via Codex in T3 Code.

[szafranski]

I believe it is because my bug shows in in-session picker. Not in thread settings - assuming I understand app UI correctly.

…

On Sat, Sep 5, 2026 at 14:09 Julius Marminge ***@***.***> wrote: *juliusmarminge* left a comment (pingdotgg/t3code#10082) <#10082 (comment)> Native verification update, September 5, 2026: I could not reproduce the missing rows in the available current-code setup. This is a partial check, not proof that the reported iPhone 13 Pro failure is fixed. I tested the mobile JavaScript at be7796d <be7796d>. The mobile code is unchanged on the latest fetched main, 485782b <485782b>. On an iPhone 17 Pro Max simulator running iOS 26.5, with a reused development binary and an isolated catalog of three Codex and eight OpenCode models, both expansion attempts displayed all eight OpenCode rows before scrolling. Manual scrolling then reached all options. No provider turn or account call was made. There are important differences from the report: - Current existing-thread settings only offer that thread's provider. I exercised the shared picker through New Task, where both groups are available. - Current Codex options expose Fast through Service Tier, rather than the older separate Fast Mode row. The options card is shorter. - This is not the reported physical device, iOS version, or a fresh native build. The earlier source-only diagnosis is not a substitute for a matching reproduction. I am leaving this open. A retest on a current build with its exact version and whether this occurs in New Task or an existing thread would help narrow the remaining difference. Collapsed: [image: Current New Task picker with three Codex models and OpenCode collapsed] <https://camo.githubusercontent.com/b9d96d770a20d994583629dc58c365e477229a974a051c154702b97ea09f6f69/68747470733a2f2f67682d66696c652d64726f702d6170692d70726f642d6d6935667933736f77763633756674652e70696e676c6162732e776f726b6572732e6465762f662f363565613065663634633031653436322f31303038322d6e65772d7461736b2d636f6c6c61707365642e6a7067> Expanded, before any scrolling: [image: All eight OpenCode rows visible immediately after expansion] <https://camo.githubusercontent.com/b141e50026ef6f9d0ebf63a959304d9e831aaf163905f9c0173cd6516e56ed12/68747470733a2f2f67682d66696c652d64726f702d6170692d70726f642d6d6935667933736f77763633756674652e70696e676c6162732e776f726b6572732e6465762f662f336362643335646261636565666534662f31303038322d6e65772d7461736b2d657870616e6465642d756e7363726f6c6c65642e6a7067> After manual scrolling: [image: Expanded OpenCode catalog with the settings options reachable below it] <https://camo.githubusercontent.com/a0288ef9b281a622bfcb5878cfe0d859eda3a4d5fe9a4bb307bbc0abdbc0dd36/68747470733a2f2f67682d66696c652d64726f702d6170692d70726f642d6d6935667933736f77763633756674652e70696e676c6162732e776f726b6572732e6465762f662f396363363561653365663263333065382f31303038322d6e65772d7461736b2d657870616e6465642d7363726f6c6c65642e6a7067> GPT 6 Astra via Codex in T3 Code. — Reply to this email directly, view it on GitHub <#10082?email_source=notifications&email_token=AFUHCAD6MS4IEIG7HDZWHOL5NP7AJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJVGE3DSOJZG442M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5551699979>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUHCACIBHX534FHK7GCIZ35NP7AJAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNJTGEZTAMZUHE5US43TOVSTWNJTGU3TAOJRGY4DFILWAI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[juliusmarminge]

Yes, I mean the model button inside an existing conversation. My wording "thread settings" was confusing: that is the code's name for the sheet opened by that button, not a separate thread-details screen.

I opened that in-conversation button first. In my test setup it offered only the thread's current provider, so I used New Task for the additional three-Codex/eight-OpenCode expansion control shown above. Those screenshots do not rule out your reported in-session failure.

Could you share a short recording starting before you tap the model button, along with the app version and the provider selected in that conversation? That will help me match the exact route and group layout. I am keeping this open.

GPT 6 Astra via Codex in T3 Code.