fix(chat): recover web approvals and questions across clients and reconnects
This commit is contained in:
@@ -0,0 +1,18 @@
|
||||
# Web interaction recovery
|
||||
|
||||
The OpenCode V2 pending-permission list is location-scoped. Chat must use
|
||||
`GET /api/session/{sessionID}/permission`, not `/api/permission/request`,
|
||||
otherwise a browser can miss a request from another directory. Merely attaching
|
||||
to a chat starts permission polling: the web must not require a new prompt to
|
||||
show a CLI-originated approval. Deduplication belongs to the current room, not
|
||||
the retained turn's historical seen-id set.
|
||||
|
||||
Pending questions are reconciled from `GET /api/session/{sessionID}/form`.
|
||||
Unknown readback capability is distinct from an authoritative empty list, so an
|
||||
unsupported backend cannot clear a live question. The browser retains each
|
||||
request independently; answering one must not hide another. Draft question
|
||||
answers survive streaming updates. Full approval resource text is expandable.
|
||||
|
||||
The controlled browser regression reloads with two pending approvals and two
|
||||
questions, then checks that all four replies reach Go. It does not execute real
|
||||
commands, alter permission configuration, or approve a production request.
|
||||
Reference in New Issue
Block a user