[BUG] CLAUDE_ENV_FILE not sourced after /clear creates new session

[priyanshujain]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When /clear is executed, a new session is created and the SessionStart hook runs correctly, writing to the new $CLAUDE_ENV_FILE. However, subsequent Bash tool calls
do not have access to the environment variables from this file - they still use the environment from the original session startup.

The docs state: "Claude Code will source this file before each Bash command, making the environment persistent across all commands."

• Hook runs correctly (verified via debug logs)
• New env file is created at new path: ~/.claude/session-env/{new-session-id}/hook-0.sh
• But Bash tool calls still use environment from original session startup
• New env file is never sourced

What Should Happen?

After /clear, $CLAUDE_SESSION_ID should reflect the new session ID (e.g., bbb-222) since:

• SessionStart hook runs with source: "clear"
• Hook writes new session ID to the new $CLAUDE_ENV_FILE
• Docs say env file is sourced before each Bash command

Error Messages/Logs

Steps to Reproduce

1. Create a SessionStart hook that captures the session ID:

// hooks/hooks.json
{
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "echo \"export CLAUDE_SESSION_ID='$(echo | jq -Rr 'fromjson? | .session_id // empty' <<< \"$(cat)\")''\" >> \"$CLAUDE_ENV_FILE\""
          }
        ]
      }
    ]
  }
}

2. Start a fresh Claude Code session
3. Run: echo $CLAUDE_SESSION_ID → outputs correct session ID (e.g., aaa-111)
4. Run /clear command
5. Run: echo $CLAUDE_SESSION_ID → still outputs old session ID aaa-111

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.0.72

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

I am using latest version of Ghostty terminal.

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] CLAUDE_ENV_FILE not sourced on resumed sessions (--continue) #12418
2. [BUG] /clear breaks session continuity - --resume cannot find post-clear sessions despite official recommendation #9352
3. SessionStart hooks not working for new conversations #10373

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[priyanshujain]

This is not duplicate as it's not following what's mentioned in docs

Claude Code will source this file(CLAUDE_ENV_FILE) before each Bash command, making the environment persistent across all commands

none of the issues highlight it. And it's also related to /clear. you can even treat both as an independent issues.

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[niksauer]

I have the same problem. This is breaking some of my hooks that have session-specific state.