[WIP] feat: @ mentions in AI prompt #3473

jimniels · 2025-09-24T20:33:27Z

Description

Add a @ button picker in AI prompt box that, when clicked, inserts a @ character in your prompt and triggers showing the autocomplete
Adds support for typing @ in the AI prompt which triggers showing an autocomplete
Style the mention and make it clickable, which highlights the selection in the grid
Add an item to right-click context menu items on the grid called "Reference in chat" that opens the AI analyst and inserts a reference to the grid selection in the last focused prompt

Screenshots

Prompt with popup:

Context menu on grid:

Prompt with styled @-mention (color class names: text-primary bg-border)

Todos

Do we need something in the AI context that says like "Internal: if the user does @ followed by a string of text, they're likely referring to some data in the file, like a named code cell, table, sheet, or even just a range like @A1:A5"
Add mixpanel events for usage @jimniels

To Test

Grid context menus:

Right-click code table or chart, inserts named ref, e.g. @Python1
Right-click data table, inserts named ref, e.g. @Table1
Right-click formula, inserts cell reference, e.g. F17
Right-click selection of individual cell(s) on the grid — in a data table, code table, etc. — inserts ref with the sheet name, e.g. Sheet1!A1:A5
- Add sheet name because you can switch sheets while using AI analyst and that will preserve your original intention.
Right-click code or data table column, inserts named reference, e.g. @Postgres1[Agent_Rating]
Reference is always inserted / appended to the last focused AI analyst prompt
- If AI analyst is closed, open Analyst and insert/append to last focused prompt
- If AI analyst is open, insert/append to last focused prompt

AI prompt:

@ button inserts a @ into the current prompt box and triggers showing the autocomplete box
Typing @ triggers showing autocomplete box
Keyboard support for navigating autocomplete box (up, down, enter, esc)
Feature is only available in AI analyst (not right-chat)

qa-wolf · 2025-09-24T20:33:30Z

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

github-actions · 2025-09-24T20:33:57Z

Preview - Build, Deploy & Tests-E2E

✅ Build images
✅ Deploy images - Oct 02, 2025 at 09:24 PM UTC - Preview
❌ Tests-E2E - Report

codecov · 2025-09-24T20:37:47Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.76%. Comparing base (7e2b5e8) to head (553c5fd).

Additional details and impacted files

@@                 Coverage Diff                 @@
##           jim/ai-empty-state    #3473   +/-   ##
===================================================
  Coverage               89.76%   89.76%           
===================================================
  Files                     437      437           
  Lines                   90129    90129           
===================================================
  Hits                    80905    80905           
  Misses                   9224     9224

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

quadratic-client/src/app/ui/hooks/useGetMentions.tsx

graphite-app · 2025-09-24T21:59:19Z

quadratic-client/src/shared/shadcn/ui/mentions-textarea.tsx

+      useEffect(() => {
+        const handleClickOutside = (event: MouseEvent) => {
+          if (mentionState.isOpen && textareaRef.current) {
+            const target = event.target as Node;
+            const isInTextarea = textareaRef.current.contains(target);
+            const isInMentionsDropdown = document.querySelector('[data-mentions-dropdown]')?.contains(target);
+
+            if (!isInTextarea && !isInMentionsDropdown) {
+              setMentionState((prev) => ({ ...prev, isOpen: false }));
+            }
+          }
+        };
+
+        if (mentionState.isOpen) {
+          document.addEventListener('mousedown', handleClickOutside);
+          return () => document.removeEventListener('mousedown', handleClickOutside);
+        }
+      }, [mentionState.isOpen, setMentionState, textareaRef]);


The cleanup function in this useEffect is conditionally returned only when mentionState.isOpen is true. This creates a potential memory leak if the component unmounts while the dropdown is closed. Consider always returning the cleanup function regardless of the dropdown state:

useEffect(() => { const handleClickOutside = (event: MouseEvent) => { if (mentionState.isOpen && textareaRef.current) { // existing logic } }; document.addEventListener('mousedown', handleClickOutside); return () => document.removeEventListener('mousedown', handleClickOutside); }, [mentionState.isOpen, setMentionState, textareaRef]);

This ensures proper cleanup on component unmount in all cases.

Suggested change

useEffect(() => {

const handleClickOutside = (event: MouseEvent) => {

if (mentionState.isOpen && textareaRef.current) {

const target = event.target as Node;

const isInTextarea = textareaRef.current.contains(target);

const isInMentionsDropdown = document.querySelector('[data-mentions-dropdown]')?.contains(target);

if (!isInTextarea && !isInMentionsDropdown) {

setMentionState((prev) => ({ ...prev, isOpen: false }));

}

}

};

if (mentionState.isOpen) {

document.addEventListener('mousedown', handleClickOutside);

return () => document.removeEventListener('mousedown', handleClickOutside);

}

}, [mentionState.isOpen, setMentionState, textareaRef]);

useEffect(() => {

const handleClickOutside = (event: MouseEvent) => {

if (mentionState.isOpen && textareaRef.current) {

const target = event.target as Node;

const isInTextarea = textareaRef.current.contains(target);

const isInMentionsDropdown = document.querySelector('[data-mentions-dropdown]')?.contains(target);

if (!isInTextarea && !isInMentionsDropdown) {

setMentionState((prev) => ({ ...prev, isOpen: false }));

}

}

};

document.addEventListener('mousedown', handleClickOutside);

return () => document.removeEventListener('mousedown', handleClickOutside);

}, [mentionState.isOpen, setMentionState, textareaRef]);

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-09-25T22:19:40Z

quadratic-client/src/app/ui/components/AIUserMessageForm.tsx

+      setTimeout(() => {
+        const mention = detectMentionInText(newValue, cursorPos + 1);
+
+        if (mention) {
+          const position = getMentionCursorPosition(textarea);
+          setMentionState((prev) => ({
+            ...prev,
+            isOpen: true,
+            query: mention.query,
+            startIndex: mention.startIndex,
+            endIndex: mention.endIndex,
+            position,
+            selectedIndex: 0,
+          }));
+        }
+
+        // Focus and position cursor after @
+        textarea.focus();
+        textarea.setSelectionRange(cursorPos + 1, cursorPos + 1);
+      }, 0);


The setTimeout approach for detecting mentions after inserting the @ character introduces potential race conditions with fast typing. Consider directly triggering mention detection with the known cursor position instead. Since you already have the exact position where the @ was inserted (cursorPos + 1), you could construct the mention state immediately rather than relying on a timeout to detect it from the textarea value.

Suggested change

setTimeout(() => {

const mention = detectMentionInText(newValue, cursorPos + 1);

if (mention) {

const position = getMentionCursorPosition(textarea);

setMentionState((prev) => ({

...prev,

isOpen: true,

query: mention.query,

startIndex: mention.startIndex,

endIndex: mention.endIndex,

position,

selectedIndex: 0,

}));

}

// Focus and position cursor after @

textarea.focus();

textarea.setSelectionRange(cursorPos + 1, cursorPos + 1);

}, 0);

// Directly detect mention without setTimeout

const mention = detectMentionInText(newValue, cursorPos + 1);

if (mention) {

const position = getMentionCursorPosition(textarea);

setMentionState((prev) => ({

...prev,

isOpen: true,

query: mention.query,

startIndex: mention.startIndex,

endIndex: mention.endIndex,

position,

selectedIndex: 0,

}));

}

// Focus and position cursor after @

textarea.focus();

textarea.setSelectionRange(cursorPos + 1, cursorPos + 1);

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-09-26T18:20:34Z

quadratic-client/src/app/actions/viewActionsSpec.ts

+    run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {
+      // TODO:
+      // We want to keep track of the last focused prompt input in the AI analyst and
+      // when the user uses this action via the grid, we want to (open if closed)
+      // insert/append a reference to the selection in the last focused prompt input.
+      console.log('TODO(ayush): pass reference to AI analyst chat');


The implementation for the StartChatInAIAnalyst action contains a TODO comment and console log statement that need to be addressed before this feature can work properly. When users select "Reference in chat" from context menus, the current code won't actually pass the reference to the AI analyst chat. Consider completing this implementation by replacing the placeholder code with the actual logic to track the last focused prompt input and insert the reference into it when the action is triggered.

Suggested change

run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {

// TODO:

// We want to keep track of the last focused prompt input in the AI analyst and

// when the user uses this action via the grid, we want to (open if closed)

// insert/append a reference to the selection in the last focused prompt input.

console.log('TODO(ayush): pass reference to AI analyst chat');

run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {

const { dispatch, getState } = store;

const state = getState();

// Open AI Analyst panel if it's not already open

if (!state.ui.isAIAnalystOpen) {

dispatch(uiActions.openAIAnalyst());

}

// Get the last focused prompt input or use the default one

const lastFocusedInput = state.aiAnalyst.lastFocusedPromptInput || 'mainPrompt';

// Insert/append the reference to the selection in the prompt input

dispatch(aiAnalystActions.appendToPrompt({

inputId: lastFocusedInput,

text: ` ${reference.text || reference.cellReference || ''}`,

}));

},

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-09-26T18:20:35Z

quadratic-client/src/shared/shadcn/ui/mentions-textarea.tsx

+export function detectMentionInText(text: string, cursorPos: number) {
+  const textBeforeCursor = text.substring(0, cursorPos);
+  const atIndex = textBeforeCursor.lastIndexOf('@');
+
+  if (atIndex === -1) return null;
+
+  // Check if there's a space after @ (not a mention)
+  const textAfterAt = textBeforeCursor.substring(atIndex + 1);
+  if (textAfterAt.includes(' ')) return null;
+
+  // Check if we're still typing the mention (no space after @)
+  const textAfterCursor = text.substring(cursorPos);
+  const nextSpaceIndex = textAfterCursor.indexOf(' ');
+  const endOfText = textAfterCursor.length === 0;
+
+  if (nextSpaceIndex === 0 && !endOfText) return null;
+
+  const query = textAfterAt;
+  const startIndex = atIndex;
+  const endIndex = cursorPos;
+
+  return {
+    query,
+    startIndex,
+    endIndex,
+  };


The logic in detectMentionInText for determining if a user is still typing a mention appears problematic. The condition nextSpaceIndex === 0 && !endOfText will return null if there's a space immediately after the cursor position, even when the user might still be in the process of typing a mention.

Consider revising this check to handle edge cases more robustly. For example:

// Instead of checking for space at cursor position if (nextSpaceIndex === 0 && !endOfText) return null; // Consider a different approach that better handles cursor positions // within partially typed mentions

This would improve the autocomplete experience when users are typing mentions with spaces nearby.

Suggested change

export function detectMentionInText(text: string, cursorPos: number) {

const textBeforeCursor = text.substring(0, cursorPos);

const atIndex = textBeforeCursor.lastIndexOf('@');

if (atIndex === -1) return null;

// Check if there's a space after @ (not a mention)

const textAfterAt = textBeforeCursor.substring(atIndex + 1);

if (textAfterAt.includes(' ')) return null;

// Check if we're still typing the mention (no space after @)

const textAfterCursor = text.substring(cursorPos);

const nextSpaceIndex = textAfterCursor.indexOf(' ');

const endOfText = textAfterCursor.length === 0;

if (nextSpaceIndex === 0 && !endOfText) return null;

const query = textAfterAt;

const startIndex = atIndex;

const endIndex = cursorPos;

return {

query,

startIndex,

endIndex,

};

export function detectMentionInText(text: string, cursorPos: number) {

const textBeforeCursor = text.substring(0, cursorPos);

const atIndex = textBeforeCursor.lastIndexOf('@');

if (atIndex === -1) return null;

// Check if there's a space between @ and cursor (not a mention)

const textBetweenAtAndCursor = textBeforeCursor.substring(atIndex + 1);

if (textBetweenAtAndCursor.includes(' ')) return null;

// Check if we're at a valid position for a mention

// A mention is valid if it's at the start of text or has a space before it

if (atIndex > 0 && textBeforeCursor[atIndex - 1] !== ' ' && textBeforeCursor[atIndex - 1] !== '\n') return null;

const query = textBetweenAtAndCursor;

const startIndex = atIndex;

const endIndex = cursorPos;

return {

query,

startIndex,

endIndex,

};

}

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-09-26T18:26:32Z

quadratic-client/src/shared/shadcn/ui/mentions-textarea.tsx

+                className="absolute z-50 w-80 rounded-md border bg-popover p-1 text-popover-foreground shadow-md"
+                style={{
+                  position: 'fixed',
+                  top: mentionState.position.top - 24,
+                  left: mentionState.position.left,
+                  transform: 'translateY(-100%)',
+                  pointerEvents: 'auto',
+                }}


The dropdown positioning calculation doesn't account for textarea scrolling. When the textarea contains scrolled content, the dropdown will appear at an incorrect position relative to the mention. Consider adjusting the position calculation in getMentionCursorPosition() to include textarea.scrollTop to ensure the dropdown remains properly aligned with the cursor position regardless of scroll state.

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-09-26T19:52:46Z

quadratic-client/src/app/ui/components/AIUserMessageForm.tsx

+        onChange={handlePromptChange}
+        onKeyDown={handleKeyDown}
+        autoComplete="off"
+        placeholder={enableMentions ? 'Ask a question (type @ to reference data)…' : 'Ask a question…'}


The placeholder text no longer handles the waitingOnMessageIndex condition that was present in the original code. To maintain this functionality while adding the new mentions feature, consider updating the placeholder logic:

placeholder={ waitingOnMessageIndex !== undefined ? 'Waiting to send message...' : (enableMentions ? 'Ask a question (type @ to reference data)…' : 'Ask a question…') }

This preserves the waiting state message while incorporating the new mentions-related placeholder text.

Suggested change

placeholder={enableMentions ? 'Ask a question (type @ to reference data)…' : 'Ask a question…'}

placeholder={

waitingOnMessageIndex !== undefined

? 'Waiting to send message...'

: (enableMentions

? 'Ask a question (type @ to reference data)…'

: 'Ask a question…')

}

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-10-02T20:43:26Z

quadratic-client/src/app/actions/viewActionsSpec.ts

+    run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {
+      // TODO:
+      // We want to keep track of the last focused prompt input in the AI analyst and
+      // when the user uses this action via the grid, we want to (open if closed)
+      // insert/append a reference to the selection in the last focused prompt input.
+      console.log('TODO(ayush): pass reference to AI analyst chat');
+      if (!pixiAppSettings.setAIAnalystState) return;
+      pixiAppSettings.setAIAnalystState((prev) => {
+        const newState = {
+          ...prev,
+          showAIAnalyst: true,
+          initialPrompt: reference ? `@${reference} ` : '',
+          currentChat: { id: '', name: '', lastUpdated: Date.now(), messages: [] },
+        };
+        return newState;
+      });


The current implementation doesn't match the TODO comment's intent. While the code opens the AI analyst and creates a new chat with the reference, it doesn't track the last focused prompt or append to an existing prompt if the analyst is already open. This means users could lose their in-progress work when using this feature.

Consider implementing the described behavior where:

If AI analyst is closed: open it and insert the reference

If AI analyst is open: append the reference to the last focused prompt instead of creating a new chat

This would provide a more seamless experience and prevent potential data loss when users reference items from the grid.

Suggested change

run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {

// TODO:

// We want to keep track of the last focused prompt input in the AI analyst and

// when the user uses this action via the grid, we want to (open if closed)

// insert/append a reference to the selection in the last focused prompt input.

console.log('TODO(ayush): pass reference to AI analyst chat');

if (!pixiAppSettings.setAIAnalystState) return;

pixiAppSettings.setAIAnalystState((prev) => {

const newState = {

...prev,

showAIAnalyst: true,

initialPrompt: reference ? `@${reference} ` : '',

currentChat: { id: '', name: '', lastUpdated: Date.now(), messages: [] },

};

return newState;

});

run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {

if (!pixiAppSettings.setAIAnalystState) return;

pixiAppSettings.setAIAnalystState((prev) => {

// If AI Analyst is already open and there's an existing chat, append to it

if (prev.showAIAnalyst && prev.currentChat?.id) {

return {

...prev,

// Append the reference to the existing prompt if there is one

appendToPrompt: reference ? `@${reference} ` : '',

};

}

// Otherwise, open the AI Analyst and start a new chat with the reference

return {

...prev,

showAIAnalyst: true,

initialPrompt: reference ? `@${reference} ` : '',

currentChat: { id: '', name: '', lastUpdated: Date.now(), messages: [] },

};

});

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

graphite-app · 2025-10-02T20:43:27Z

quadratic-client/src/app/gridGL/HTMLGrid/contextMenus/GridContextMenuCodeTableColumn.tsx

 import { DropdownMenuSeparator } from '@/shared/shadcn/ui/dropdown-menu';

 export function GridContextMenuCodeTableColumn() {
+  const { cursorString } = useCursorPosition();


This component uses cursorString while similar components use cursorStringWithSheetName. This inconsistency means references in chat will lack sheet name context. Consider using cursorStringWithSheetName here for consistency with other components and to ensure complete references.

Suggested change

const { cursorString } = useCursorPosition();

const { cursorStringWithSheetName } = useCursorPosition();

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

jimniels added 7 commits September 10, 2025 14:24

initial commit

3f8306b

prototyping

deac58d

Update AIUserMessageForm.tsx

5abec53

try mentions

fac4b12

Update mentions-textarea.tsx

3229086

Merge branch 'jim/ai-empty-state' into jim/ai-sheet-context

69d8c63

initial change direction

08db6ef

cla-bot bot added the cla-signed label Sep 24, 2025

jimniels changed the base branch from qa to jim/ai-empty-state September 24, 2025 20:33

github-actions bot temporarily deployed to preview-pr-3473 September 24, 2025 20:33 Destroyed

change from edit to view action

c8798c0

graphite-app bot reviewed Sep 24, 2025

View reviewed changes

quadratic-client/src/app/ui/hooks/useGetMentions.tsx Outdated Show resolved Hide resolved

jimniels added 2 commits September 24, 2025 14:46

cleanup

2606f76

more cleanup

3d0f4ae

jimniels self-assigned this Sep 24, 2025

jimniels added 2 commits September 24, 2025 15:50

next iteration

fc813e1

Update mentions-textarea.tsx

d139d14

graphite-app bot reviewed Sep 24, 2025

View reviewed changes

consolidation

c12f044

jimniels mentioned this pull request Sep 24, 2025

[WIP] feat: narrow AI context with sheet data & remove right chat #3443

Closed

4 tasks

jimniels added 2 commits September 24, 2025 16:27

tweaks

a7a08a2

merge latest

397a2ab

github-actions bot temporarily deployed to preview-pr-3473 September 24, 2025 22:39 Destroyed

tweaks

995e475

graphite-app bot reviewed Sep 25, 2025

View reviewed changes

add todos

5aeb7e9

graphite-app bot reviewed Sep 26, 2025

View reviewed changes

update example popup for grouping

41f9a37

graphite-app bot reviewed Sep 26, 2025

View reviewed changes

add more context menus

d1f39d7

graphite-app bot reviewed Sep 26, 2025

View reviewed changes

more menus

9c9ced0

jimniels assigned AyushAgrawal-A2 Sep 26, 2025

merge latest

dd5ba83

github-actions bot temporarily deployed to preview-pr-3473 October 2, 2025 20:41 Destroyed

graphite-app bot reviewed Oct 2, 2025

View reviewed changes

re-use exisiting props

553c5fd

github-actions bot deployed to preview-pr-3473 October 2, 2025 20:56 View deployment

Base automatically changed from jim/ai-empty-state to qa October 3, 2025 23:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[WIP] feat: @ mentions in AI prompt #3473

[WIP] feat: @ mentions in AI prompt #3473

Uh oh!

jimniels commented Sep 24, 2025 •

edited

Loading

Uh oh!

qa-wolf bot commented Sep 24, 2025

Uh oh!

github-actions bot commented Sep 24, 2025 •

edited

Loading

Uh oh!

codecov bot commented Sep 24, 2025 •

edited

Loading

Uh oh!

Uh oh!

graphite-app bot Sep 24, 2025

Uh oh!

graphite-app bot Sep 25, 2025

Uh oh!

graphite-app bot Sep 26, 2025

Uh oh!

graphite-app bot Sep 26, 2025

Uh oh!

graphite-app bot Sep 26, 2025

Uh oh!

graphite-app bot Sep 26, 2025

Uh oh!

graphite-app bot Oct 2, 2025

Uh oh!

graphite-app bot Oct 2, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

-    run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {
-      // TODO:
-      // We want to keep track of the last focused prompt input in the AI analyst and
-      // when the user uses this action via the grid, we want to (open if closed)
-      // insert/append a reference to the selection in the last focused prompt input.
-      console.log('TODO(ayush): pass reference to AI analyst chat');
+    run: (reference: ViewActionArgs[Action.StartChatInAIAnalyst]) => {
+      const { dispatch, getState } = store;
+      const state = getState();
+      // Open AI Analyst panel if it's not already open
+      if (!state.ui.isAIAnalystOpen) {
+        dispatch(uiActions.openAIAnalyst());
+      }
+      // Get the last focused prompt input or use the default one
+      const lastFocusedInput = state.aiAnalyst.lastFocusedPromptInput || 'mainPrompt';
+      // Insert/append the reference to the selection in the prompt input
+      dispatch(aiAnalystActions.appendToPrompt({
+        inputId: lastFocusedInput,
+        text: ` ${reference.text || reference.cellReference || ''}`,
+      }));
+    },

-        placeholder={enableMentions ? 'Ask a question (type @ to reference data)…' : 'Ask a question…'}
+        placeholder={
+          waitingOnMessageIndex !== undefined
+            ? 'Waiting to send message...'
+            : (enableMentions
+                ? 'Ask a question (type @ to reference data)…'
+                : 'Ask a question…')
+        }

	const { cursorString } = useCursorPosition();
	const { cursorStringWithSheetName } = useCursorPosition();

[WIP] feat: @ mentions in AI prompt #3473

Are you sure you want to change the base?

[WIP] feat: @ mentions in AI prompt #3473

Uh oh!

Conversation

jimniels commented Sep 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Screenshots

Todos

To Test

Uh oh!

qa-wolf bot commented Sep 24, 2025

Uh oh!

github-actions bot commented Sep 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Preview - Build, Deploy & Tests-E2E

Uh oh!

codecov bot commented Sep 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

graphite-app bot Sep 24, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Sep 26, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Sep 26, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Sep 26, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Sep 26, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Oct 2, 2025

Choose a reason for hiding this comment

Uh oh!

graphite-app bot Oct 2, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jimniels commented Sep 24, 2025 •

edited

Loading

github-actions bot commented Sep 24, 2025 •

edited

Loading

codecov bot commented Sep 24, 2025 •

edited

Loading