sessions
SolidSee active Claude Code sessions on this machine and coordinate across them via direct messages, status announcements, and file-overlap awareness. Triggers when the user asks "who else is running?", "any other claude open?", "what other sessions are active?", "tell <name> to ...", "ping <peer>", "let peers know I'm doing X", "broadcast <status>", "check the cc digest", or any cross-session / multi-agent coordination on this machine.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- anipotts
- Repository
- anipotts/claude-code-tips
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
manage-claude-sessions
Create, continue, fork, inspect, wait for, and interrupt Claude Code sessions through the claude-session MCP tools. Use when the user asks to delegate work to Claude, keep one primary conversation focused while Claude works separately, manage or inspect Claude sessions, branch an existing Claude context, or resume prior Claude work.
message-other-sessions
Message another Claude Code session on this machine or beyond it, using ListAgents and SendMessage. Use when the user wants to tell, ask, warn or hand something over to a session running in another terminal, worktree, machine or the web ("tell the other session", "let the session working on X know", "ask my other terminal whether Y finished", "warn the session in the other worktree"), when work just landed that invalidates what a parallel session is building on, or when they want a notice once another session goes idle. Also use when diagnosing why a cross-session message never arrived, or when deciding between messaging, resuming a session, agent teams and channels.
session
Show what's active in the current session — hooks, rules, agents, skills, memories, MCP servers, model, and CLAUDE.md chain