fix(web): resume an in-progress draft when returning to the index

[sideeffffect]

Problem

Start a new conversation, type into the composer, click into another thread, then return to the / landing (the app logo / "Go to threads"): you're dropped on a blank composer. The landing always mints a fresh draft in the most-recently-active project, and project recency is ranked by server threads — which ignores unsent drafts. So an in-progress draft that lives in a different project than the one you just visited is left parked in the sidebar instead of reopened.

The text isn't destroyed (invested drafts survive and get a sidebar row, per #5777), but "I came back and my message is gone" is exactly how it reads.

Fix

Make the index landing resume the most-recent draft the user has actually invested content in (across projects) before falling back to starting a fresh draft in the most-recently-active project.

• Explicit new-thread surfaces (the + buttons, hotkeys, command palette) are untouched and still mint fresh — this only changes the "return home" landing, where resuming unsent work is what you'd expect.
• Adds getMostRecentDraftSessionWithContent to the composer draft store (non-promoted + composerDraftHasUserContent, newest by createdAt), with unit coverage.

Verification

apps/web typecheck, lint, and composerDraftStore.test.ts pass (incl. two new cases: resumes the newest invested draft across projects / ignores empty sessions; returns null when nothing is invested).

This is a routing/state change with no static visual; the difference is whether / reopens your in-progress draft or a blank one. Happy to record a short before/after clip if that's preferred.

Claude Opus 4.8 via Claude Code.

---

Note

Medium Risk
Changes default index routing and which draft opens on “return home,” though explicit new-thread entry points are unchanged and missing projects skip resume.

Overview
Visiting / no longer always mints a blank draft in the most-recently-active project. IndexDraftLanding now looks for a resumable in-progress draft first and replace-navigates to /draft/$draftId when that draft’s project still exists; otherwise it keeps the old behavior of starting a fresh draft in the latest project.

The composer draft store gains getMostRecentDraftSessionWithContent, which picks the newest non-promoting draft session (by createdAt) that has real user content via composerDraftHasUserContent, including across projects and ignoring empty newer sessions. Unit tests cover cross-project selection and the empty-draft case.

^{Reviewed by Cursor Bugbot for commit 326f2d5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Resume in-progress drafts when navigating to the index route

• Adds getMostRecentDraftSessionWithContent to the composer draft store, which returns the most recently created, non-promoting draft session that has user content across all projects.
• Updates the IndexDraftLanding component in _chat.index.tsx to check for a resumable draft on load; if found and its project still exists, navigates to /draft/$draftId instead of creating a new draft.
• Behavioral Change: visiting the index route no longer always creates a fresh draft — users with an in-progress draft are redirected to it.

^{Macroscope summarized 326f2d5.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ebd17a6b-88dc-469b-9972-30c895a0b73f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces new user-facing navigation behavior - automatically resuming drafts with content when returning to the index instead of creating blank ones. While well-tested and scoped, this is a feature change affecting core UX rather than a simple bug fix.

^{You can add or adjust custom eligibility rules. Learn more.}