You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d8333f2
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
## Unreleased
8
8
9
9
### Fixed
10
+
- An MCP follow-up (`pro_consult` with `continue_task` or `continue_thread`) used up one of the automatic follow-ups (`PRODEX_MAX_AUTO_FOLLOWUPS`, default 5) even when the browser refused it before anything was typed. Measured 2026-11-02 in the browser container: two follow-ups in one conversation refused as `composer_not_ready` were recorded as its follow-ups 3 and 4 of 5, so the agent had one left with no prompt sent. A follow-up is now reserved once its prompt is typed, right before it is submitted. A follow-up the budget no longer covers is still refused before any task is created or the browser is touched, and a send that fails or is uncertain after submitting still counts. If another follow-up uses the last of the budget while this one waits for the browser, it stops before submitting as `awaiting_user`.
10
11
- A follow-up with `--tool` (or MCP `pro_consult``tools`) sent after a new chat in the same tab was refused as `Selected "Web search" but the composer never showed it as active.` although the tool was on, and the tool was left on in the composer. A new chat leaves the home page's composer mounted in a hidden workspace ahead of the conversation's composer, and the check read the first editor in the page, which was that hidden one. Measured 2026-11-03 in the browser container on a test conversation: the follow-up was refused as above with the tool showing in the visible composer; the same check reading the composer the prompt is typed into, built on the container branch, sent it. The tools button lookup also skips an open "Edit message" editor, as the model lookup now does.
11
12
- A follow-up that named a model or a reasoning step failed as `composer_not_ready` ("model selector button not found") for as long as a message in the conversation was open for editing, and the advice to retry could not help: only reloading the page did. "Edit message" on a user turn opens a form with its own editor inside the transcript, ahead of the composer, and the model lookup took the first editor on the page, whose form has no model selector. Found 2026-11-03 tracing four follow-ups the browser container refused on 2026-11-02 while new chats in between went through; reproduced on a test conversation by opening "Edit message", where this lookup from 0.40.49 refused as above. It now skips editors inside a message, as typing the prompt already did.
12
13
- A consult's session id carried the start of its prompt, lowercased: a prompt beginning "Reply with only the word" became `sess_<date>_<time>_<random>-reply-with-only-the-word-...`, its first 31 characters. The session record itself does not keep the prompt, but the id is listed by `prodex sessions`, written into receipts, and returned by MCP `bridge_list_sessions`, which the HTTP MCP server answers for any client holding its token. Found 2026-10-30 reading a session listing. A new session id is the date, the time and a random part only. Ids already recorded are read as before.
0 commit comments