Unified Session Manager FAQs

Question 1

How does memory persistence work across sessions?

Accepted Answer

At the end of a session, the skill automatically extracts key learnings and patterns into the .claude/memory/ directory, allowing future sessions to load and benefit from that accumulated context.

Question 2

What is the difference between resuming and forking a session?

Accepted Answer

Resuming continues exactly from the last saved checkpoint of an existing session, while forking creates a new independent session branch based on the current context.

Question 3

Where is the session state information stored?

Accepted Answer

Session state and event logs are stored locally within your project directory under .claude/state/session.json and .claude/state/session.events.jsonl.

Question 4

Can I use this to coordinate multiple Claude Code instances?

Accepted Answer

Yes, you can use the '/session broadcast' command to send messages to all active sessions and '/session inbox' to check for incoming updates from other sessions in the same project.

Question 5

Does this skill handle user authentication for my web application?

Accepted Answer

No, this skill is specifically designed for managing Claude Code's own internal development sessions and process state, not for application-level user login or authentication features.

Unified Session Manager

主要功能

使用场景

Unified Session Manager

主要功能

使用场景