[Bug]: Hover-only "Discard draft" X in the sidebar deletes the draft on one click, no confirmation or undo

[myfunc]

Area

apps/web (sidebar, shared with the desktop app)

Summary

Each thread row with an unsent draft shows an X ("Discard draft") on hover, at the right edge next to Snooze and Settle. One click on it deletes the draft text and attachments. There is no confirmation, no undo, no toast. The X only appears on hover, so the first time you learn it exists is when your message is gone. I have lost drafts to it several times already.

Steps to reproduce

1. Open a thread, type a message in the composer, do not send.
2. Open another thread. The first row now shows the amber draft marker.
3. Move the pointer onto the first row to go back to it. The hover strip at the right edge shows X, Snooze and Settle over the time/status label.
4. Click while the pointer is on the X.

Expected behavior

A destructive action on user text needs a guard: a confirmation before, or an undo (toast) after. Alternatively the X should not sit inside the row's own click target, so a click meant to open the thread cannot delete its draft.

Actual behavior

The draft is cleared at once and the row loses its marker. Nothing brings the text back. The standalone new-thread draft rows above the pinned block have the same X with the same result.

Hover state right before the click. The X sits where the pointer lands when going back to the thread:

Source

Checked at main @ 7445aa733.

• Thread row: X is rendered only on hover, inside the row, next to Snooze/Settle:

  t3code/apps/web/src/components/Sidebar.tsx

  Lines 1860 to 1888 in 7445aa7

  	{props.settlementSupported || showSnoozeButton || hasUnsentDraft ? (
  	<span
  	className={cn(
  	// focus-visible, not focus-within: a mouse click leaves
  	// the Settle button focused, and a plain focus-within
  	// would keep the controls pinned over the status label
  	// once the pointer moves away (e.g. after a failed
  	// settle) instead of cross-fading back.
  	"pointer-events-none absolute inset-y-0 right-0 flex items-stretch opacity-0 transition-opacity has-[:focus-visible]:pointer-events-auto has-[:focus-visible]:static has-[:focus-visible]:opacity-100 group-hover/sidebar-row:pointer-events-auto group-hover/sidebar-row:static group-hover/sidebar-row:opacity-100",
  	snoozeMenuOpen && "pointer-events-auto static opacity-100",
  	)}
  	>
  	{hasUnsentDraft ? (
  	<Tooltip>
  	<TooltipTrigger
  	render={
  	<button
  	type="button"
  	aria-label="Discard draft"
  	onClick={handleDiscardDraftClick}
  	className="inline-flex cursor-pointer items-center rounded-md bg-transparent px-1.5 text-xs text-muted-foreground hover:text-foreground"
  	/>
  	}
  	>
  	<XIcon className="size-3.5" />
  	</TooltipTrigger>
  	<TooltipPopup side="top">Discard draft</TooltipPopup>
  	</Tooltip>
  	) : null}

• Its handler releases uploads and clears the composer, nothing else:

  t3code/apps/web/src/components/Sidebar.tsx

  Lines 1076 to 1084 in 7445aa7

  	const handleDiscardDraftClick = useCallback(
  	(event: ReactMouseEvent) => {
  	event.preventDefault();
  	event.stopPropagation();
  	releaseComposerDraftUploads(threadRef);
  	clearComposerContent(threadRef);
  	},
  	[clearComposerContent, threadRef],
  	);

• New-thread draft row: same X, calls clearDraftThread:

  t3code/apps/web/src/components/Sidebar.tsx

  Lines 790 to 803 in 7445aa7

  	<Tooltip>
  	<TooltipTrigger
  	render={
  	<button
  	type="button"
  	aria-label="Discard draft"
  	onClick={handleDiscard}
  	className="pointer-events-none inline-flex cursor-pointer items-center rounded-md bg-transparent px-1 text-muted-foreground opacity-0 transition-opacity hover:text-foreground focus-visible:pointer-events-auto focus-visible:opacity-100 group-hover/sidebar-row:pointer-events-auto group-hover/sidebar-row:opacity-100"
  	>
  	<XIcon className="size-3" />
  	</button>
  	}
  	/>
  	<TooltipPopup side="top">Discard draft</TooltipPopup>

  and

  t3code/apps/web/src/components/Sidebar.tsx

  Lines 897 to 906 in 7445aa7

  	const handleDiscard = useCallback(
  	(draftId: DraftId) => {
  	// The /draft/$draftId route redirects home on its own when the draft
  	// it renders disappears, so discarding the open draft needs no
  	// special-casing here.
  	releaseComposerDraftUploads(draftId);
  	clearDraftThread(draftId);
  	},
  	[clearDraftThread],
  	);

• Introduced in feat(web): show which sidebar threads hold an unsent draft #9658 (thread rows) and feat(web): keep unsent drafts one click away in the sidebar #5777 (draft rows). docs/user/thread-sidebar.md does not mention the control.

Relation to existing issues

• Discussion [UX issue] "Discard draft" should be removed from sidebar cards #10349 (Ideas, 2026-09-06) reports the same loss and asks for removal or a confirmation. No response so far. Filing as a bug because the outcome is silent loss of typed text, the same class as [Bug]: Clicking a question option discards text typed into the composer #12569 (accepted) and [Bug]: Typed composer text is lost when clicking Stop during a pending approval prompt #8963, not a feature proposal.

Impact

Major degradation or frequent failure

Version or commit

Desktop 0.0.42, source checked at main @ 7445aa733

Environment

Windows 11 Home 10.0.26200, T3 Code desktop (Alpha), provider Claude Code

Workaround

None after the click. Prevention only: click the left part of the row, or copy the text before leaving the thread.

_{^{lovely composed in pair with Claude Fable 5.1 in Claude Code}}

[juliusmarminge]

Triage

Confirmed in current main (apps/web/src/components/Sidebar.tsx). This is a real web/desktop sidebar bug: a hover-only “Discard draft” X sits on the thread/draft row’s click target and clears the composer on one click, with no confirmation, undo, or toast.

Not a duplicate of an existing issue. Discussion #10349 is the same accidental loss (filed 2026-09-06); this ticket is the actionable bug report for that UX. Same class as #12569 / #8963 (silent loss of typed text), different trigger.

What happens

• Thread rows with an unsent draft: hover strip shows X next to Snooze/Settle. handleDiscardDraftClick calls releaseComposerDraftUploads + clearComposerContent and returns. See Sidebar.tsx around the hover strip and that handler.
• New-thread draft rows above the pinned block: same X, clearDraftThread.
• composerDraftStore wipes prompt, attachments, and contexts. Nothing keeps a snapshot.
• Mobile already guards this: Alert.alert("Discard draft?", …) in apps/mobile/src/features/home/usePendingTaskListActions.ts.
• Sidebar archive/delete already have confirm settings. Discard does not.
• Introduced in feat(web): show which sidebar threads hold an unsent draft #9658 (thread-row X) and feat(web): keep unsent drafts one click away in the sidebar #5777 (draft-row X). Open fix(web): add context menu to draft threads in the sidebar #10637 adds a context-menu Discard for draft rows; it does not fix the hover X.

Repro in the report matches the code. Two independent reports (this issue + discussion #10349).

Suggested fix

Keep the control if we want a way to drop a draft from the list, but add a guard on both discard paths:

1. Confirm before discard (align with mobile and archive/delete), or
2. Undo toast that restores the cleared snapshot.

Also worth keeping the X out of the row’s primary click target so “open this thread” cannot hit Discard. If #10637 lands, its menu item should use the same guard.

docs/user/thread-sidebar.md does not mention this control; update it only if the shipped behavior changes.

Accepting as a web/desktop UI bug. Not Windows-specific despite the report environment.

[juliusmarminge]

Note

Grok responding on behalf of Julius.

Closing as fixed by #10637 (merged). Sidebar draft discard (hover X and the new draft-row context menu) now goes through discardComposerDraft with the sidebar undo notice / thread.undo, so a stray click is recoverable.