bug: Stale Ask Question cards keep loading after the request was answered elsewhere

[soichiyo]

What's broken

When an Ask Question (request_user_input) card is shown in the desktop app and the user answers the same request through another route (for example, by typing into the terminal that the agent is running in, or by responding from the Codex/agent side rather than clicking in the Paseo Ask Question view), the Paseo Ask Question card stays on screen and is treated as still pending.

If the user then tries to clear it from the Paseo UI — Dismiss, or submit an answer in the card — the card flips into a loading state and never resolves. The pending card never goes away unless the agent is killed or the app is restarted.

Steps to reproduce

1. Run a Codex agent in Paseo so it issues a request_user_input (Ask Question) — for example, ask it something that will trigger a clarifying question.
2. Instead of answering inside the Paseo Ask Question view, answer through a different route. For example, type the answer in the terminal that the same Codex session is reading from, or otherwise let the underlying agent receive the answer outside Paseo.
3. Wait for the agent to acknowledge the answer and continue.
4. Return to the Paseo desktop app and click Dismiss (or submit a value) in the still-visible Ask Question card.

Expected

Once the underlying agent has resolved the permission/question request, the Paseo Ask Question card for it should clear automatically. Dismissing or submitting from the card after the fact should resolve immediately without entering a loading state.

Actual

The card stays visible after the agent has moved on, and Dismiss / submit puts the card into a permanent loading state.

Where did this happen

Desktop (Electron)

Paseo version

0.1.101

OS version

macOS 26.3.2

Agent provider

Codex

Notes

The pattern in the daemon logs is respondToPermission failing on the provider side with No pending permission request with id '<id>' (because the underlying agent has already moved past it). The Paseo AgentManager then never dispatches permission_resolved for that request, so the desktop UI's respondToPermissionAndWait never sees a resolution and the card sticks in loading.

I have only investigated this against the current main of this repo and the daemon's AgentManager code path. I have not done an end-to-end manual reproduction in a fresh desktop build, so the repro above is described in terms of behavior I expect from reading the code path; if there is a more reliable way to reproduce, happy to update.

[paseo-bot]

This is plausible, but the report is based on reading the code path and does not include an observed end-to-end reproduction. To distinguish a current runtime bug from behavior that has changed since v0.1.101, please add:

• A reproduction on the current Paseo release, with exact Paseo client, daemon, and Codex CLI versions.
• The shortest real sequence that leaves the Ask Question card stale, including the alternate route used to answer it.
• A short screen recording showing the agent continuing while the card remains pending and then enters the loading state.
• Sanitized daemon and Electron logs covering that occurrence. See Reading the logs: ~/.paseo/daemon.log and, on macOS, ~/Library/Logs/Paseo/main.log.

Please remove credentials, tokens, private source, and unrelated personal data from logs.

[boudra]

Closing for now: we need an observed Codex run showing how the question is answered outside Paseo and the card then stays pending or loading. Please reopen with that sequence, current app/daemon/Codex versions, and the matching permission error.