Skip to content

Fix stale model picker shortcut labels - #4433

Closed
colonelpanic8 wants to merge 1 commit into
pingdotgg:mainfrom
colonelpanic8:fix/model-picker-shortcuts
Closed

colonelpanic8 wants to merge 1 commit into
pingdotgg:mainfrom
colonelpanic8:fix/model-picker-shortcuts

Fix stale model picker shortcut labels

c7ac18d
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Jul 28, 2026 in 5s

Effect Service Conventions: No issues found

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.

The changed files (apps/web/src/components/chat/ModelPickerContent.tsx and its test) contain a React rendering optimization (memoized extraData for a virtualized list) and a component test. They do not create, move, refactor, or consume any Effect service, and no Effect service conventions apply to the changed scope. No violations found.


🔍 Agent activity — reasoning, no tool calls

💭 Looking at this diff, I'm checking whether it involves Effect service changes. The modification adds a modelListExtraData useMemo hook and passes it to LegendList in a React component, along with a corresponding test update. Since this is purely a React rendering optimization with no Effect service creation, refactoring, or consumption, there shouldn't be any findings to report. The response needs to be valid JSON per the schema, and with no violations detected, I should return a success state.