Session errors do not say what happened: a refused interrupt reads as success, the interrupt timeout names no command, a send after a clean exit reads as a death #82
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/claude-code-query#82
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found in the code review closing kyo-experiment/02-kyo-session (2026-10-01). Applies to the shipped zio session and to the Kyo adapter. Line one is the important one: a Stop the CLI refuses is shown as done. A typed refusal needs a new CLIError case in core.
control_responsesubtype and a malformedstill_queued: a refused interrupt reads asok · still queued: 0—kyo/.../internal/cli/SessionRules.scala:71-76andzio/.../internal/cli/SessionProcess.scala:504-508; a typed refusal needs a newCLIErrorcase incore(02-kyo-session review)ProcessTimeoutErrorwhosecommandisList("control_request", "interrupt"), not a command line —kyo/.../internal/cli/SessionProcess.scalainterruptTimedOut,zio/.../internal/cli/SessionProcess.scala:329(02-kyo-session review)SessionProcessDied(Some(0), …)while a pending request in the same case getsSessionEndedBeforeRequest—kyo/.../internal/cli/SessionRules.scalafailureOf(02-kyo-session review)