active
Show currently active AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI). A session is active if a live process is attributable to it: Claude Code via the ~/.claude/sessions registry (with per-session status: busy/idle/waiting/...), Codex via its open rollout file — the same correlation `omnisess ps` uses, so the two reconcile. Cursor/Copilot fall back to process-alive + recent transcript activity. Use this skill when asked about active sessions, running sessions, what is currently open, or which AI tools are in use right now. Trigger phrases: "active sessions", "running sessions", "what's open", "current sessions", "is claude running", "what sessions are active", "show active".
- License 许可
- MIT
- 所属仓库
- psacc/omnisess
- 最近更新
- 2026-11-05
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- active
- license
- MIT
- metadata
- { "version": "0.13.0" }
- description
- Show currently active AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI). A session is active if a live process is attributable to it: Claude Code via the ~/.claude/sessions registry (with per-session status: busy/idle/waiting/...), Codex via its open rollout file — the same correlation `omnisess ps` uses, so the two reconcile. Cursor/Copilot fall back to process-alive + recent transcript activity. Use this skill when asked about active sessions, running sessions, what is currently open, or which AI tools are in use right now. Trigger phrases: "active sessions", "running sessions", "what's open", "current sessions", "is claude running", "what sessions are active", "show active".
- allowed-tools
- Bash
- argument-hint
03 SKILL.md 正文
omnisess active
Show currently active AI coding sessions.
Usage
omnisess active
# Agent-ergonomic output: minimal fields + aggregate + next-step hints (compact JSON)
omnisess active --axi
Instructions
- Check that the
omnisessbinary is available:
if ! command -v omnisess &>/dev/null; then
echo "omnisess not found. Install it with:"
echo " go install github.com/psacc/omnisess@latest"
exit 1
fi
- Run the command:
omnisess active "$@"
Notes
A session is considered active when a live process is attributable to it:
- Claude Code: a
~/.claude/sessions/<PID>.jsonregistry entry with a live PID; the registry status (busy/idle/waiting/...) is shown in the STATUS column - Codex: a live codex process holding the session's rollout file open
- Cursor / Copilot (fallback): the tool's process is alive AND the transcript was modified within the last 10 minutes
The same correlation backs omnisess ps, so every claude/codex row here maps to a
process in the ps tree (cross-reference via the ID column).
Example output
TOOL ID PROJECT BRANCH PREVIEW UPDATED STATUS
claude 5c3f2742 prj/myapp main fix the bug 2026-06-10 15:14 ACTIVE (busy)
04 同仓库更多 Skills
stats
Show tool-call counts and file-I/O activity from the transcript SQLite index. Aggregates Read/Write/Edit file paths, line counts, token usage, and error flags across a time window (default 7d) or for a single session. Use this skill when asked which tools were used most, which files saw the most activity, how many tokens were spent, or to inspect a single session's tool-call summary. Trigger phrases: "session stats", "tool stats", "what tools did I use", "tool usage", "files touched", "token usage", "stats for last week", "summarize tool calls", "session tool breakdown".
skills-audit
Classify agent skills by usage tier (Keep / Borderline / Archive / Unknown) using Claude Code session JSONL transcripts as the signal source. Read-only — never modifies skills, sessions, or any file on disk. Use this skill when asked to audit skills, find unused skills, classify skills, check which skills get used, produce a skill usage report, or prune skills. Trigger phrases: "audit skills", "find unused skills", "classify skills", "which skills do I use", "skill usage report", "prune skills", "what skills are unused", "skills I can remove", "trim my skill list". Output is a recommendation (Keep / Borderline / Archive) — acting on it is always a manual step.
show
Show the full detail of a single AI coding session by its ID. Session IDs are in the format <tool>:<id> (e.g., claude:5c3f2742, cursor:a1b2c3d4). Use this skill when asked to show a specific session, inspect a session, read a session, or view the messages in a session. Trigger phrases: "show session", "open session", "inspect session", "read session", "show me claude:5c3f2742", "view session details", "what happened in session".
search
Full-text search across all AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI). Use this skill when asked to search sessions, find a conversation about a topic, look up what was discussed in past sessions, or find sessions mentioning specific code or concepts. Trigger phrases: "search sessions", "find sessions about", "look up in sessions", "what did I discuss about", "find conversation about", "search my history".
recap
Produce a structured markdown briefing of AI coding sessions for a given time window. Groups sessions by project and summarizes each group with intent, outcome, and status. Use this skill when asked to recap recent coding work, summarize today's sessions, show what was worked on, or produce a daily/weekly session summary. Trigger phrases: "recap", "what did I work on", "daily summary", "session summary", "summarize my sessions", "what sessions did I have today", "coding recap". This is the sessions-only public version — no Slack, Jira, or Granola integration.
ps
Show live Claude Code and Codex sessions as a process tree, grouped by shared ancestor chain up to launchd. Covers Claude CLI sessions, Claude Desktop agent mode, and Codex sessions (CLI TUI + Codex.app threads). Use this skill when asked about the process tree, ancestor lineage, which terminal or tmux window a Claude or Codex session is running in, or what's currently running. Trigger phrases: "process tree", "what's running", "lineage", "ancestor chain", "which terminal is my claude in", "tmux tree", "claude process tree", "codex process tree", "session lineage". macOS-only: on other platforms the command prints "unsupported" and exits 0.