Claude Code Cross-Session Access and Task Tracking

Claude Code added a feature that surfaces sub-tasks discovered during a main task as cards, enabling later execution, and now supports cross-session access to retrieve context from previous conversations. - During a coding session, Claude Code can identify unrelated issues and turn them into card-like tasks; users can open each card to start a new session or continue in the current one, though the UI currently shows up to 5 cards and requires manual selection. - Cross-session access allows an agent in one project to be fed a session ID from another project, letting it autonomously retrieve relevant context without the user summarizing or transferring logs. - A practical example: after testing an app feature in a test project, the user gave the session ID to the source code project’s Claude agent to analyze and propose optimizations based on the original session’s details.
Key insights
Task Tracking Turns Side Observations into Actionable Work Items
The card system mimics a developer’s habit of noting follow-up issues during code review, preserving them for later without disrupting the current workflow. This reduces the mental overhead of context switching.
Cross-Session Access Eliminates Manual Context Reconstruction
By allowing agents to directly retrieve context from past sessions via session IDs, users avoid summarizing or copying logs, reducing information loss and saving time. This is especially useful when diagnosing issues discovered in a different project environment.