From d088d575369014bdc81e34a929efb63a36876024 Mon Sep 17 00:00:00 2001 From: Pedro Pombeiro Date: Wed, 19 Aug 2026 11:31:35 +0200 Subject: [PATCH] fix(homeassistant): document one notification per pending request Release automation only tracks the plugin packages, so the concurrent wait fix in packages/_shared would never have been published on its own. This carries it into a release by documenting the behaviour it changes. Records that each pending request now gets its own webhook and poll, that requests can be answered in any order, that the session resumes only once all of them are answered, and that automations must key responses by request ID rather than assuming a single outstanding request. --- packages/homeassistant/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/homeassistant/README.md b/packages/homeassistant/README.md index 7963e83..4ee1d3d 100644 --- a/packages/homeassistant/README.md +++ b/packages/homeassistant/README.md @@ -236,6 +236,8 @@ To enable this, add the following to your config: 4. Plugin reads the response, clears the entity, and replies to OpenCode 5. If the user answers locally in the TUI instead, the plugin receives a `permission.replied` / `question.replied` event and stops polling immediately +Each pending request gets its own webhook and its own poll. When an agent asks for several permissions at once, you receive one notification per request and can answer them in any order. The session resumes only after every request has been answered, so make sure your automation includes the request ID in the response rather than assuming a single outstanding request. + **Response formats** The entity value is disambiguated by splitting on `:`. A first segment of `question` marks a question response (3 segments); anything else is a permission response (2 segments).