[FEATURE] Improve Home screen for efficient navigation.

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Title: No way to resume a known project on session start — forces blind filesystem search, risks landing on wrong/unbacked-up folder
Body:
Summary
Opening Claude Code without explicitly picking a folder drops the session into an ephemeral, empty "scratch workspace" with zero visibility into any project I've worked on before — not even a list of folders I've opened previously. Naming a project by name ("bring up the MBIE project") gives Claude no way to resolve that except a blind filesystem-wide search, which is slow, token-expensive, and — in my case — returned a wrong answer: it found a folder with matching filenames on my local C: drive (not backed up) before it found my actual canonical, backed-up project folder in OneDrive. That produced duplicate files scattered across my machine and wasted an entire back-and-forth correcting it.
Steps to reproduce

1. Open Claude Code with no folder selected.
2. Ask it to open a project by name only (no path).
3. Observe: no "recent projects" list is offered. The assistant has to grep/glob the whole filesystem for the name.
4. If two folders on disk contain similarly-named files (e.g. a stray local copy and a canonical cloud-backed copy), there's no signal to prefer the canonical one — it's a coin flip based on search order.

Impact
• Wasted tokens/time re-deriving context that already exists on disk.
• Real risk of an AI-driven session acting on a stale/unbacked-up copy of a document instead of the current one.
• No way to "pick up where I left off" the way you can in almost any other editor or IDE (recent-files list, workspace switcher, etc.).
Requested fix / feature ideas

1. Surface a "recent projects/folders" list on session start (or in a picker) — folder path + last-opened time — so returning to known work doesn't depend on the AI guessing from a name.
2. Support a user-designated default project root (or a small pinned list) that the app/assistant checks first before any wider filesystem search.
3. Make it visually unambiguous when a session is in the ephemeral scratch workspace vs. a real project folder, so it's clear no prior context will carry over.

Environment
• Claude Code desktop app, Windows 11
• Session started with "No folder" (scratch workspace)
• Date: 2026-09-13

Proposed Solution

The Home screen is for humans trying to master software geek paradise - don't assume we all have the same skill sets. Wasting tokens navigating is not AI

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_