Before submitting
Area
apps/web
Steps to reproduce
I have a sessionstart claude code hook to do some basic logging of session data (company thing to extend the otel support for data it can't send).
Getting very noisey data from our t3code users (myself included) as there appears to be a 5 minutely probeClaudeCapabilities that creates a session.
Currently unsure if this is a my problem to fix in the hook, or something t3code should change, but a potential solution woudl be to use "settingSources: []" so that hooks aren't loaded for these automated sessions.
Expected behavior
a potential solution woudl be to use "settingSources: []" so that hooks aren't loaded for these automated sessions.
Actual behavior
hooks are run for the 5 minute timer
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Before submitting
Area
apps/web
Steps to reproduce
I have a sessionstart claude code hook to do some basic logging of session data (company thing to extend the otel support for data it can't send).
Getting very noisey data from our t3code users (myself included) as there appears to be a 5 minutely probeClaudeCapabilities that creates a session.
Currently unsure if this is a my problem to fix in the hook, or something t3code should change, but a potential solution woudl be to use "settingSources: []" so that hooks aren't loaded for these automated sessions.
Expected behavior
a potential solution woudl be to use "settingSources: []" so that hooks aren't loaded for these automated sessions.
Actual behavior
hooks are run for the 5 minute timer
Impact
Minor bug or occasional failure
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response