chore(code): make Combobox search and footer sticky

[VojtechBartos]

Summary

• Pin .combobox-input-wrapper with position: sticky; top: 0 and .combobox-footer with position: sticky; bottom: 0.
• Add an explicit max-height: 240px to [cmdk-list] so cmdk's own height tracking can't push the footer outside the popover.
• Fixes the Command Center TaskSelector where "+ New task" required scrolling past the task list when a project had many tasks.

The custom Combobox (built on cmdk) is currently only used by TaskSelector. Other pickers (BranchSelector, GitHubRepoPicker) use @posthog/quill's Combobox, which already has a sticky footer slot — they are unaffected.

Showcase

code-task-sticky.mov

---

Created with PostHog Code

[greptile-apps]

Prompt To Fix All With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/components/ui/combobox/Combobox.css
Line: 292-295

Comment:
**`position: sticky` may not activate in the current scroll model**

`[cmdk-root]` has `overflow: hidden`, which makes it a scroll container per spec — but it never actually scrolls (content is now capped to fit within its 340px `max-height`). `position: sticky` on `.combobox-footer` (and `.combobox-input-wrapper`) is relative to that non-scrolling container, so the declarations are effectively inert. The footer stays visible because `max-height: 240px` on `[cmdk-list]` keeps the total content within the 340px root cap, not because of stickiness.

This isn't a bug (the fix works), but a future maintainer may wonder why sticky seems to have no effect when inspecting layout in DevTools. A short comment would clarify intent:

```css
/* Safety net: keeps input and footer visible if [cmdk-root] ever becomes
   a true scroll container (currently the max-height on [cmdk-list] is
   the primary constraint). */
position: sticky;
bottom: 0;
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "chore(code): make Combobox search and fo..." | Re-trigger Greptile}

[greptile-apps]

position: sticky may not activate in the current scroll model

[cmdk-root] has overflow: hidden, which makes it a scroll container per spec — but it never actually scrolls (content is now capped to fit within its 340px max-height). position: sticky on .combobox-footer (and .combobox-input-wrapper) is relative to that non-scrolling container, so the declarations are effectively inert. The footer stays visible because max-height: 240px on [cmdk-list] keeps the total content within the 340px root cap, not because of stickiness.

This isn't a bug (the fix works), but a future maintainer may wonder why sticky seems to have no effect when inspecting layout in DevTools. A short comment would clarify intent:

/* Safety net: keeps input and footer visible if [cmdk-root] ever becomes
   a true scroll container (currently the max-height on [cmdk-list] is
   the primary constraint). */
position: sticky;
bottom: 0;

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/components/ui/combobox/Combobox.css
Line: 292-295

Comment:
**`position: sticky` may not activate in the current scroll model**

`[cmdk-root]` has `overflow: hidden`, which makes it a scroll container per spec — but it never actually scrolls (content is now capped to fit within its 340px `max-height`). `position: sticky` on `.combobox-footer` (and `.combobox-input-wrapper`) is relative to that non-scrolling container, so the declarations are effectively inert. The footer stays visible because `max-height: 240px` on `[cmdk-list]` keeps the total content within the 340px root cap, not because of stickiness.

This isn't a bug (the fix works), but a future maintainer may wonder why sticky seems to have no effect when inspecting layout in DevTools. A short comment would clarify intent:

```css
/* Safety net: keeps input and footer visible if [cmdk-root] ever becomes
   a true scroll container (currently the max-height on [cmdk-list] is
   the primary constraint). */
position: sticky;
bottom: 0;
```

How can I resolve this? If you propose a fix, please make it concise.