fix(pulse-monitor): prevent false positive stalled detection after tool execution
Remove forced monitoring restart in tool.execute.after to avoid false positive stalled session detection when LLM legitimately completes response after tool run. Monitoring now resumes naturally on next session/message event. 🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)
This commit is contained in:
@@ -132,11 +132,10 @@ export function createPulseMonitorHook(ctx: PluginInput) {
|
||||
// Pause monitoring while tool runs locally (tools can take time)
|
||||
stopMonitoring()
|
||||
},
|
||||
"tool.execute.after": async (input: { sessionID: string }) => {
|
||||
// Resume monitoring after tool finishes
|
||||
if (input.sessionID) {
|
||||
startMonitoring(input.sessionID)
|
||||
}
|
||||
"tool.execute.after": async (_input: { sessionID: string }) => {
|
||||
// Don't forcefully restart monitoring here to avoid false positives
|
||||
// Monitoring will naturally resume when next session/message event arrives
|
||||
// This prevents stalled detection on legitimately idle sessions
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user