pengy-cli is mostly run by other programs: a skill calling a subagent, a script, a cron job, me
running a task from a shell. A caller that gives up sends SIGTERM. Python's default action is to die on
the spot, and this release is about what was left behind when it did.
Three things were skipped. The running tool's process group: it is its own session, so the signal sent
to the CLI never reached it, and a killed run left the command it was running alive on your machine.
The sudo askpass password file, left in the temp directory. The tool_calls repair, so the saved chat
kept a tool call with no result, which is a broken conversation the next time you open it.
Now, while a turn is running, SIGTERM and SIGHUP unwind it the way Ctrl-C already did: the active
tool's process group is killed, every live askpass helper is removed (the helper's own cleanup() and
a registry both maintain that list), the in-flight API request is abandoned without waiting, and the
chat is repaired and saved. Then the process re-raises the original signal with its default action,
so the caller sees exactly what it saw before: returncode == -15, shell status 143. An interrupted
run never exits 0. With --output json you get {"error": {"type": "interrupted", ...}} on stdout, so
the output is still a document a program can parse.
Ctrl-C during a REPL turn, including inside a slash command like /task, now stops that turn and
returns to the prompt instead of quitting the CLI. A second signal during cleanup ends the process
immediately; SIGKILL cannot be handled, and Windows keeps its default handlers. Tests run the real CLI
against a stub endpoint, which is the only way to test signal behaviour honestly.