メニュー
Use when user asks about session duration, elapsed time, how long they've been working, or "quanto tempo". Also use when any skill or workflow needs to know session elapsed time.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/aguinaldotupy/claude-session-tracker --skill session-statusコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when user asks about past sessions, worklog, accumulated hours, "quanto trabalhei hoje", "worklog do dia", "histórico de sessões", "horas trabalhadas", "session history", or wants to review time spent on projects across sessions.
Use when user asks to reset, restart, or zero out the session timer. Trigger phrases include "reset timer", "restart session time", "reiniciar tempo", "zerar timer".
SOC 職業分類に基づく
SKILL.md を表示中
| name | session-status |
| description | Use when user asks about session duration, elapsed time, how long they've been working, or "quanto tempo". Also use when any skill or workflow needs to know session elapsed time. |
Reports current Claude Code session elapsed time.
A SessionStart hook writes $(date +%s) to ~/.claude/session-env/<session_id>/session-tracker. The session ID is stable across compaction, so the timestamp survives context resets.
UserPromptSubmit/Stop and PreToolUse/PostToolUse hooks append events to
events.log: P <ts> (prompt), T <ts> <tool> / D <ts> <tool> (tool
start/done), S <ts> (stop). Active (working) time is computed additively by
the shared awk that SessionStart deploys to $HOME/.claude/session-env/active-time.awk:
each prompt → stop bracket counts in full, plus up to grace seconds of reading
after each Stop (SESSION_IDLE_THRESHOLD_SECONDS, default 120). A session parked
while you work elsewhere stops accruing after the grace, so the number reflects real
attention rather than wall-clock. Wall-clock elapsed is reported as secondary context.
Get the live session and today's total in one call, then render (see Output Format below for the canonical example):
bash "$HOME/.claude/session-env/session-query.sh" status --session "${CLAUDE_SESSION_ID:-${CLAUDE_CODE_SESSION_ID:-}}"
Returns JSON: {live:{elapsed_seconds,active_seconds,started_at,issue_key}, today:{active_seconds,sessions}}.
Convert seconds to Xh Ym. If issue_key is set, show it. source:"none" means no history yet.
Compute idle = live.elapsed_seconds - live.active_seconds (wall-clock time not counted as active).
"Trabalho hoje" = today.active_seconds + live.active_seconds (finished sessions from the store plus the still-open live session, which isn't in the store yet), formatted Xh Ym.
Display to user:
Trabalho: 1h 50m · sessão aberta há 2h 15m (idle 25m, desde 14:30)
Trabalho hoje: 5h 42m (sessões concluídas + atual)
Current issue: LIN-456
Active time (live.active_seconds) is the headline; wall-clock (live.elapsed_seconds, "aberta há…") and idle time are shown as context only. live.started_at (epoch) formats to desde HH:MM. The reading grace after each Stop is configurable via SESSION_IDLE_THRESHOLD_SECONDS (default 120 = 2 minutes).
If source is "none" and live.started_at is 0, inform: session tracking hook not configured. If only today's total is empty (today.sessions == 0) but live has data, still show the live session and skip the "Trabalho hoje" line (or show it equal to the live active).
To reset the live timer, tell the user they can use /session-tracker:reset-session or ask naturally.
To see a full worklog, suggest /session-tracker:session-history.