Anthropic, Manage sessions

Worauf sich diese Seite beruft, wörtlich, abgerufen am 10.10.2026:

• A session is a saved conversation tied to a project directory.bestätigt 10.11.2026
• Claude Code stores it locally as you work, so you can resume where you left off, branch to try a different approach, or switch between tasks.bestätigt 10.11.2026
• Give sessions descriptive names so they're findable in the session picker and resumable by name.bestätigt 10.11.2026
• Not every configuration flag from the original launch is restored.bestätigt 10.11.2026
• The cross-project search resolves the ID only when exactly one other project holds a transcript with messages for it, so a hand-copied duplicate makes Claude Code report not-found rather than resume an arbitrary copy.bestätigt 10.11.2026
• Branching creates a copy of the conversation so far and switches you into it, leaving the original intact.bestätigt 10.11.2026
• If you resume the same session in two terminals without forking, messages from both interleave into one transcript.bestätigt 10.11.2026
• Claude Code stores sessions per project directory.bestätigt 10.11.2026
• Each line is a JSON object: a message, a tool use or result, a record of a request Claude Code sent the model, or a metadata entry.bestätigt 10.11.2026
• that is still running, Claude Code opens the running session itself.bestätigt 10.11.2026
• the dialog can appear when you resume a long conversation after a long break or on a different model.bestätigt 10.11.2026
• its estimate is the share of your 5-hour usage limit that the saved conversation alone would use.bestätigt 10.11.2026
• The estimated use comes when you send your first message after Resume, not when you select it.bestätigt 10.11.2026
• Sessions whose first prompt was a /loop command don’t appear in the picker, and claude --continue skips them too.bestätigt 10.11.2026
• The messages that the last compaction summarized aren’t loaded again.bestätigt 10.11.2026