fix: restore pending asks after resume
This commit is contained in:
@@ -3,7 +3,7 @@
|
||||
# @eko24ive/pi-ask
|
||||
|
||||
[](https://www.npmjs.com/package/@eko24ive/pi-ask)
|
||||
[](https://github.com/eko24ive/pi-ask/commits/main)
|
||||
[](https://github.com/eko24ive/pi-ask/commits/main)
|
||||
[](https://github.com/eko24ive/pi-ask/stargazers)
|
||||
|
||||
> [!IMPORTANT]
|
||||
@@ -60,6 +60,7 @@ Once installed, this package gives the agent a native way to ask for clarificati
|
||||
- `/answer` extracts questions from the latest assistant message into an ask flow
|
||||
- `/answer:again` reopens the latest `/answer` form on the current branch
|
||||
- `/ask:replay` replays the latest real `ask_user` form on the current branch
|
||||
- 🛟 Automatic recovery of an unanswered `ask_user` form after startup, resume, or fork
|
||||
- 🗣️ You can talk to your agent to configure pi-ask; it will read the bundled configuration guide and tailor the config for you
|
||||
|
||||
## Feature walkthrough
|
||||
@@ -210,6 +211,12 @@ Replay commands are branch-aware. They read persisted entries from the current p
|
||||
|
||||
Cancellation is local to the UI: closing a replayed form does not start a new agent turn. Submitted answers are sent back as a normal user follow-up message.
|
||||
|
||||
### Interrupted ask forms
|
||||
|
||||
If Pi stops while an `ask_user` form is open, the tool call remains without a result. Starting, resuming, or forking that session reopens the newest unanswered form once. Submitting sends the result as a user message because the original tool execution no longer exists. Cancelling dismisses the automatic recovery. Either outcome prevents another automatic reopen, while `/ask:replay` remains available.
|
||||
|
||||
New sessions and extension reloads do not trigger recovery.
|
||||
|
||||
Kudos to [@k0valik](https://github.com/k0valik) for the `/answer` idea.
|
||||
|
||||
You can also talk to pi to configure this extension. When asked to customize pi-ask settings, keymaps, notifications, or extraction behavior, the agent is instructed to read the bundled `docs/configuration.md` guide first and then edit the config file accordingly.
|
||||
|
||||
Reference in New Issue
Block a user