C:/Program Files/Git/new command should fire SessionStart hooks

Resolved 💬 1 comment Opened Mar 21, 2026 by jarkillo Closed Mar 21, 2026

Problem

When using /new to start a fresh conversation, SessionStart hooks do not fire. They only fire when the claude CLI process is initially launched.

This means any setup logic in SessionStart hooks (loading project context, briefing data, clearing caches, etc.) is skipped when the user starts a new conversation with /new.

Expected behavior

/new should trigger SessionStart hooks, since it effectively starts a new session/conversation. The user expects the same initialization to happen as when they first launch claude.

Current workaround

Users must fully exit and restart the claude CLI to get their SessionStart hooks to fire again.

Environment

  • Claude Code CLI on Windows 11
  • Hooks configured in ~/.claude/settings.json under hooks.SessionStart

View original on GitHub ↗

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