brooksbUWO
9f6b68118e
SessionStart hooks fire on every user prompt instead of only at session start. The root cause is clearSessionHookState(), called on every session.idle event, which clears sessionFirstMessageProcessed. This resets the isFirstMessage guard, making it always return true, so SessionStart hooks execute on every prompt. sessionFirstMessageProcessed is session-level state (tracks whether the first message has been processed) and should only be cleared in clearAllSessionHookState() on session deletion/disposal, not on idle. sessionErrorState and sessionInterruptState remain cleared on idle since they are per-response transient state.
23 lines
928 B
TypeScript
23 lines
928 B
TypeScript
export const sessionFirstMessageProcessed = new Set<string>()
|
|
|
|
export const sessionErrorState = new Map<string, { hasError: boolean; errorMessage?: string }>()
|
|
|
|
export const sessionInterruptState = new Map<string, { interrupted: boolean }>()
|
|
|
|
export function clearSessionHookState(sessionID: string): void {
|
|
sessionErrorState.delete(sessionID)
|
|
sessionInterruptState.delete(sessionID)
|
|
// sessionFirstMessageProcessed must NOT be cleared on idle.
|
|
// It tracks whether the first message of a session has been processed,
|
|
// so that SessionStart hooks fire only once per session. Clearing it
|
|
// on idle (which fires after every model response) makes isFirstMessage
|
|
// always return true, causing SessionStart hooks to fire on every
|
|
// prompt instead of only the first one.
|
|
}
|
|
|
|
export function clearAllSessionHookState(): void {
|
|
sessionErrorState.clear()
|
|
sessionInterruptState.clear()
|
|
sessionFirstMessageProcessed.clear()
|
|
}
|