From ea45e021cb53e62369faf357d14c6a8d085bb2ba Mon Sep 17 00:00:00 2001 From: Abir Abbas Date: Tue, 22 Sep 2026 16:05:57 -0400 Subject: [PATCH 1/2] changelog: v0.4.1 rolled up Co-Authored-By: Claude Fable 5.1 --- CHANGELOG.md | 37 +++++++++++++++++++ .../1381-changelog-v0-4-0-rolled-up.md | 12 ------ .../1385-waiting-message-survives-leaving.md | 17 --------- 3 files changed, 37 insertions(+), 29 deletions(-) delete mode 100644 docs/changes/unreleased/1381-changelog-v0-4-0-rolled-up.md delete mode 100644 docs/changes/unreleased/1385-waiting-message-survives-leaving.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 65181f8ffe..fa04cd9eec 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,6 +18,43 @@ rule. +## v0.4.1 — 2026-09-22 + +### Fixed + +- **a waiting message stays waiting when you leave the chat, and still goes when its answer ends** — [#1385](https://github.com/Agent-Field/codeaf/pull/1385) · `chat` + +
4 things that are no longer true + + - A conversation switch used to fold every message parked above the box into the draft and drop the pictures parked with it, so a follow-up parked before esc, enter came back as unsent text without its picture and was never sent. The parked queue now travels with the conversation as itself — words, pictures, pasted documents, standing mark, order — and comes back as the same waiting block. + - A parked message used to go only when its conversation was in front at the turn's close. It now also goes when the turn ends while the conversation is held behind the screen: the keeper sends the oldest one through that conversation's own agent, one per finished turn, after any ctrl+q follow-up the session already holds. + - /new no longer drops the messages waiting in the conversation it leaves; they stay with that conversation and go when its answer ends. Opening a session from the welcome box still drops them and says so. + - On a connection that holds one conversation at a time the waiting words still fold back into the box, and their pictures and pasted documents now come back onto the tray with them instead of being lost. + + Since #1071 esc opens Home, and Home stands the cursor on the conversation before + this one, so the natural esc, enter is a switch. Santosh met it as "esc when a + message is waiting does not seem to send it, it seems to just cancel the running + one". The switch is what lost the message, and a switch is not a quit: the turn + keeps running, so the message can keep waiting and go when it ends. + +
+ + +### Internal + +- **v0.4.0 is rolled up into CHANGELOG.md** — [#1381](https://github.com/Agent-Field/codeaf/pull/1381) · `build` `docs` + +
1 thing that is no longer true + + - Ninety entries sat loose under docs/changes/unreleased/ and CHANGELOG.md ended at v0.3.0. They are the `## v0.4.0` section now, and the stable release reads its notes from it. + + The roll-up is a pull request of its own, as docs/rules/changelog.md asks, so + the section lands on `dev` and is promoted like anything else; this entry is + the one that rides in the release after v0.4.0. + +
+ + ## v0.4.0 — 2026-09-22 ### Added diff --git a/docs/changes/unreleased/1381-changelog-v0-4-0-rolled-up.md b/docs/changes/unreleased/1381-changelog-v0-4-0-rolled-up.md deleted file mode 100644 index 8f2db1e784..0000000000 --- a/docs/changes/unreleased/1381-changelog-v0-4-0-rolled-up.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -kind: internal -pr: 1381 -title: v0.4.0 is rolled up into CHANGELOG.md -surface: [build, docs] -invalidates: - - "Ninety entries sat loose under docs/changes/unreleased/ and CHANGELOG.md ended at v0.3.0. They are the `## v0.4.0` section now, and the stable release reads its notes from it." ---- - -The roll-up is a pull request of its own, as docs/rules/changelog.md asks, so -the section lands on `dev` and is promoted like anything else; this entry is -the one that rides in the release after v0.4.0. diff --git a/docs/changes/unreleased/1385-waiting-message-survives-leaving.md b/docs/changes/unreleased/1385-waiting-message-survives-leaving.md deleted file mode 100644 index 5fd1d60ec1..0000000000 --- a/docs/changes/unreleased/1385-waiting-message-survives-leaving.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -kind: fixed -title: a waiting message stays waiting when you leave the chat, and still goes when its answer ends -pr: 1385 -surface: [chat] -invalidates: - - "A conversation switch used to fold every message parked above the box into the draft and drop the pictures parked with it, so a follow-up parked before esc, enter came back as unsent text without its picture and was never sent. The parked queue now travels with the conversation as itself — words, pictures, pasted documents, standing mark, order — and comes back as the same waiting block." - - "A parked message used to go only when its conversation was in front at the turn's close. It now also goes when the turn ends while the conversation is held behind the screen: the keeper sends the oldest one through that conversation's own agent, one per finished turn, after any ctrl+q follow-up the session already holds." - - "/new no longer drops the messages waiting in the conversation it leaves; they stay with that conversation and go when its answer ends. Opening a session from the welcome box still drops them and says so." - - "On a connection that holds one conversation at a time the waiting words still fold back into the box, and their pictures and pasted documents now come back onto the tray with them instead of being lost." ---- - -Since #1071 esc opens Home, and Home stands the cursor on the conversation before -this one, so the natural esc, enter is a switch. Santosh met it as "esc when a -message is waiting does not seem to send it, it seems to just cancel the running -one". The switch is what lost the message, and a switch is not a quit: the turn -keeps running, so the message can keep waiting and go when it ends. From 06f9bf3932d0120af5ddc82be1bd38b8771a597d Mon Sep 17 00:00:00 2001 From: Abir Abbas Date: Tue, 22 Sep 2026 16:06:10 -0400 Subject: [PATCH 2/2] docs: the roll-up's change entry names its pull request Co-Authored-By: Claude Fable 5.1 --- .../unreleased/1386-changelog-v0-4-1-rolled-up.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 docs/changes/unreleased/1386-changelog-v0-4-1-rolled-up.md diff --git a/docs/changes/unreleased/1386-changelog-v0-4-1-rolled-up.md b/docs/changes/unreleased/1386-changelog-v0-4-1-rolled-up.md new file mode 100644 index 0000000000..b164df27c9 --- /dev/null +++ b/docs/changes/unreleased/1386-changelog-v0-4-1-rolled-up.md @@ -0,0 +1,12 @@ +--- +kind: internal +title: v0.4.1 is rolled up into CHANGELOG.md +pr: 1386 +surface: [build, docs] +invalidates: + - "Two entries sat loose under docs/changes/unreleased/ and CHANGELOG.md ended at v0.4.0. They are the `## v0.4.1` section now, and the stable release reads its notes from it." +--- + +The roll-up is a pull request of its own, as docs/rules/changelog.md asks, so +the section lands on `dev` and is promoted like anything else; this entry is +the one that rides in the release after v0.4.1.