Readable generated context

Kept prompts readable when they included generated context from a terminal, selected page element, preview annotation, or review comment. Each context block appeared as a chip or card in its original position alongside the prompt, without exposing raw markup. Copying the message still included the full context sent to the agent.

Branch: GitHubfeat/conversation-user-context-rendering
PR: #12707Closed…
Status: Superseded
Reason: Upstream now renders generated context from its structured composer records, with inline chips, preview images, and clipboard preservation, so this branch has nothing left to add.

Comments

This fork

Settings search jumps to the wrong row after I filter. The test run shows it:

Terminal 1 lines 34-36

The field that loses the match is this one:

<SettingsSearchInput> (SettingsSearch.tsx:48)

apps/web/src/components/settings/settingsSearch.ts

Turn 2 · +47 to +49

Keep this early return, it is the only guard against empty queries.

4747 const normalized = query.trim().toLowerCase();

48 if (!normalized) return results[0];

48 if (!normalized) return null;

4949 return results.find(result => result.title.includes(normalized));

Make the focus ring less shouty

1 selected element, 1 drawing.2

Can you fix the jump and keep the ring subtle?

10:42 AM

Original

Settings search jumps to the wrong row after I filter. The test run shows it: <terminal_context> - Terminal 1 lines 34-36: 34 | FAIL src/components/settings/settingsSearch.test.ts > jumps to the matched row 35 | → expected "archive" to scroll into view, received "general" 36 | Tests 1 failed | 42 passed (43) </terminal_context> The field that loses the match is this one: <element_context> - <SettingsSearchInput> (SettingsSearch.tsx:48): url: http://localhost:5733/settings/general selector: input[role="combobox"] source: apps/web/src/components/settings/SettingsSearch.tsx:48:7 </element_context>