Feature Request: Built-in session logging, work timer, and alarm

Resolved 💬 1 comment Opened Apr 19, 2026 by saitoko Closed May 26, 2026

Summary

Three utilities that many power users end up building themselves should be standard Claude Code features:

  1. Session time logging — Automatically record session start/end times (via SessionStart/Stop hooks writing to a log file). Useful for tracking how long Claude Code sessions run.
  1. Work timer (/timer) — A built-in slash command to start/stop named work sessions and report elapsed minutes. Supports parallel tracking with auto-assigned IDs. Useful for time-boxing tasks and reviewing how long work actually takes.
  1. Time alarm (/alarm) — A slash command to trigger a notification at a specified time (/alarm 23:30 or /alarm +5m). Critical for staying focused without leaving the session.

Current workaround

All three require custom shell scripts + slash commands + hook configuration — roughly a few hours of setup per user.

Proposed

Ship these as built-in skills or hook templates. On Windows, timezone handling requires PowerShell (Get-Date) for reliable local time — adding extra friction that built-in support would eliminate.

Use cases

  • "How long did this session take?" → session logging
  • "How long did writing this article take?" → work timer
  • "Tell me when 3 minutes have passed" (e.g., instant noodles) → alarm

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗