diff --git a/CHANGELOG.md b/CHANGELOG.md index 0e7a97cdd..1bbc780da 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,17 @@ New entries are written as one fragment file per change in [changelog.d/](change ## [Unreleased] +## [0.2.40] - 2026-11-22 + +### Fixed + +- A Bot now learns from its system prompt that one of its own capabilities cannot be used right now, naming the capability and the reason, so it says "GitHub isn't connected (401 bad credentials)" before acting instead of agreeing to the work and failing half a turn later ([#3273](https://github.com/ThinkFlowLab/FlyBot/issues/3273)). Saving a capability URL that carries a username or password is refused, and an older error that quotes such a URL is stored with the userinfo masked, so a credential can never be printed into the Bot's system prompt ([#3273](https://github.com/ThinkFlowLab/FlyBot/issues/3273)). +- A capability's stored failure reason no longer repeats a credential the user typed into the capability itself: when a server echoes a request header or an environment value back in its own error body, the value of a name that promises a credential (`key`, `token`, `secret`, `auth`, `password`, `passwd`, `credential`, `signature`, `cookie`, `session`, `bearer`, and `pat` as a whole segment — `X-Github-Pat` yes, `X-Patch-Id` no) is masked before the reason is stored, longest value first so one credential is never left as a surviving tail, so it can no longer be printed into the Bot's system prompt every turn ([#3275](https://github.com/ThinkFlowLab/FlyBot/issues/3275)). +- A capability's stored failure reason no longer repeats a credential the user typed into the capability's own command or arguments, or under a header or environment name that promises one: a value after a credential-looking flag in a stdio server's `command`/`args` (the next token, the `--flag=value` form, or a `NAME=value` token), and the value of a header or environment name such as `sig`, `hmac` or `pass` — with `sig` and `pass` matched as whole segments, so `assign`, `compass` and `bypass` keep their values — is masked with `[hidden]` before the stored reason is cut at 300 characters, longest value first and a value under six characters left alone, so a failed server's own error line can no longer print that credential into the Bot's system prompt every turn ([#3278](https://github.com/ThinkFlowLab/FlyBot/issues/3278)). +- A capability's stored failure reason no longer repeats a credential typed into a command line saved in the capability's own `command`, or a credential value that begins with `-`: a `command` containing a space or a tab is read as a command line and its tokens go through the same rules as `args` — the token after a credential-looking flag, the `--flag=value` form and a `NAME=value` token are masked with `[hidden]` — and the token after a credential-looking flag is its value even when it begins with `-`, so `--api-key --verbose` stores `--api-key [hidden]` and a second `--api-key` is masked as a value too. A `command` that is one bare token without whitespace stays unmasked, because it cannot be told from a program name, the same limit as a bare `args` token; the stored reason is still one line of at most 300 characters with the mask applied before the cut, longest value first and a value under six characters left alone, so a failed server's own error line can no longer print that credential into the Bot's system prompt every turn ([#3281](https://github.com/ThinkFlowLab/FlyBot/issues/3281)). +- A workflow start the host could not finish saying had one sentence — "the host did not create the run Bots within 60s" — with no node and no reason, so a lane whose node Bots were simply slower than the deadline looked like a silent hang and the same task was dispatched three times; the refusal now names the node the host never answered, the Bots it did create with how long each took, and, when the lane's node count no longer fits the deadline at that host's speed, the seconds it needs (a six-node line at about eleven seconds per Bot reads "needs about 66s … past the 60s deadline"), while a node Bot the host refuses carries the node and the host's own reason — an unavailable model, a taken Bot name, a full tree, or the host's error text — and `workflow/assign` reports a refused start as a failed answer (`ok: false` with `error.code` `bot/refused` and `error.details` naming the node) instead of a value inside the success envelope, so a caller cannot mistake a failed dispatch for a started run ([#3282](https://github.com/ThinkFlowLab/FlyBot/issues/3282)). +- A Workflow now creates its run Bots four at a time instead of one after another, so a six-node line starts in about 20 seconds instead of about 66 and no longer misses the 60-second batch deadline a slow host used to hit ([#3286](https://github.com/ThinkFlowLab/FlyBot/issues/3286)). If the host refuses one node, the line stops asking for new Bots, waits for the ones already in flight, and releases every Bot it did create; the run still maps the graph's nodes to their Bots in the graph's own order. + ## [0.2.39] - 2026-11-21 ### Fixed @@ -1613,7 +1624,8 @@ If you used the legacy `dsh-bot` package, remove it before you install `ds-bot`. - Only one DSH can change a team at a time; a second DSH on the same DSH home opens it read-only ([Data and backups](ds-bot/README.md#data-and-backups)). - Group chats use many tokens: each member reads the group and answers in turn. -[Unreleased]: https://github.com/ThinkFlowLab/FlyBot/compare/v0.2.39...HEAD +[Unreleased]: https://github.com/ThinkFlowLab/FlyBot/compare/v0.2.40...HEAD +[0.2.40]: https://github.com/ThinkFlowLab/FlyBot/compare/v0.2.39...v0.2.40 [0.2.39]: https://github.com/ThinkFlowLab/FlyBot/compare/v0.2.38...v0.2.39 [0.2.38]: https://github.com/ThinkFlowLab/FlyBot/compare/v0.2.37...v0.2.38 [0.2.37]: https://github.com/ThinkFlowLab/FlyBot/compare/v0.2.36...v0.2.37 diff --git a/changelog.d/3273.fixed.md b/changelog.d/3273.fixed.md deleted file mode 100644 index bf7d5c151..000000000 --- a/changelog.d/3273.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A Bot now learns from its system prompt that one of its own capabilities cannot be used right now, naming the capability and the reason, so it says "GitHub isn't connected (401 bad credentials)" before acting instead of agreeing to the work and failing half a turn later ([#3273](https://github.com/ThinkFlowLab/FlyBot/issues/3273)). Saving a capability URL that carries a username or password is refused, and an older error that quotes such a URL is stored with the userinfo masked, so a credential can never be printed into the Bot's system prompt ([#3273](https://github.com/ThinkFlowLab/FlyBot/issues/3273)). diff --git a/changelog.d/3275.fixed.md b/changelog.d/3275.fixed.md deleted file mode 100644 index a53fedc4e..000000000 --- a/changelog.d/3275.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A capability's stored failure reason no longer repeats a credential the user typed into the capability itself: when a server echoes a request header or an environment value back in its own error body, the value of a name that promises a credential (`key`, `token`, `secret`, `auth`, `password`, `passwd`, `credential`, `signature`, `cookie`, `session`, `bearer`, and `pat` as a whole segment — `X-Github-Pat` yes, `X-Patch-Id` no) is masked before the reason is stored, longest value first so one credential is never left as a surviving tail, so it can no longer be printed into the Bot's system prompt every turn ([#3275](https://github.com/ThinkFlowLab/FlyBot/issues/3275)). diff --git a/changelog.d/3278.fixed.md b/changelog.d/3278.fixed.md deleted file mode 100644 index 5779831d4..000000000 --- a/changelog.d/3278.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A capability's stored failure reason no longer repeats a credential the user typed into the capability's own command or arguments, or under a header or environment name that promises one: a value after a credential-looking flag in a stdio server's `command`/`args` (the next token, the `--flag=value` form, or a `NAME=value` token), and the value of a header or environment name such as `sig`, `hmac` or `pass` — with `sig` and `pass` matched as whole segments, so `assign`, `compass` and `bypass` keep their values — is masked with `[hidden]` before the stored reason is cut at 300 characters, longest value first and a value under six characters left alone, so a failed server's own error line can no longer print that credential into the Bot's system prompt every turn ([#3278](https://github.com/ThinkFlowLab/FlyBot/issues/3278)). diff --git a/changelog.d/3281.fixed.md b/changelog.d/3281.fixed.md deleted file mode 100644 index b3e70e326..000000000 --- a/changelog.d/3281.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A capability's stored failure reason no longer repeats a credential typed into a command line saved in the capability's own `command`, or a credential value that begins with `-`: a `command` containing a space or a tab is read as a command line and its tokens go through the same rules as `args` — the token after a credential-looking flag, the `--flag=value` form and a `NAME=value` token are masked with `[hidden]` — and the token after a credential-looking flag is its value even when it begins with `-`, so `--api-key --verbose` stores `--api-key [hidden]` and a second `--api-key` is masked as a value too. A `command` that is one bare token without whitespace stays unmasked, because it cannot be told from a program name, the same limit as a bare `args` token; the stored reason is still one line of at most 300 characters with the mask applied before the cut, longest value first and a value under six characters left alone, so a failed server's own error line can no longer print that credential into the Bot's system prompt every turn ([#3281](https://github.com/ThinkFlowLab/FlyBot/issues/3281)). diff --git a/changelog.d/3282.fixed.md b/changelog.d/3282.fixed.md deleted file mode 100644 index 38050c2b3..000000000 --- a/changelog.d/3282.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A workflow start the host could not finish saying had one sentence — "the host did not create the run Bots within 60s" — with no node and no reason, so a lane whose node Bots were simply slower than the deadline looked like a silent hang and the same task was dispatched three times; the refusal now names the node the host never answered, the Bots it did create with how long each took, and, when the lane's node count no longer fits the deadline at that host's speed, the seconds it needs (a six-node line at about eleven seconds per Bot reads "needs about 66s … past the 60s deadline"), while a node Bot the host refuses carries the node and the host's own reason — an unavailable model, a taken Bot name, a full tree, or the host's error text — and `workflow/assign` reports a refused start as a failed answer (`ok: false` with `error.code` `bot/refused` and `error.details` naming the node) instead of a value inside the success envelope, so a caller cannot mistake a failed dispatch for a started run ([#3282](https://github.com/ThinkFlowLab/FlyBot/issues/3282)). diff --git a/changelog.d/3286.fixed.md b/changelog.d/3286.fixed.md deleted file mode 100644 index e9ec89098..000000000 --- a/changelog.d/3286.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A Workflow now creates its run Bots four at a time instead of one after another, so a six-node line starts in about 20 seconds instead of about 66 and no longer misses the 60-second batch deadline a slow host used to hit ([#3286](https://github.com/ThinkFlowLab/FlyBot/issues/3286)). If the host refuses one node, the line stops asking for new Bots, waits for the ones already in flight, and releases every Bot it did create; the run still maps the graph's nodes to their Bots in the graph's own order. diff --git a/core/package-lock.json b/core/package-lock.json index 94c03983c..36311bed2 100644 --- a/core/package-lock.json +++ b/core/package-lock.json @@ -1,12 +1,12 @@ { "name": "ds-bot", - "version": "0.2.39", + "version": "0.2.40", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "ds-bot", - "version": "0.2.39", + "version": "0.2.40", "license": "Apache-2.0", "dependencies": { "@larksuiteoapi/node-sdk": "1.76.0" diff --git a/core/package.json b/core/package.json index 75c8ff423..ecdac210e 100644 --- a/core/package.json +++ b/core/package.json @@ -1,6 +1,6 @@ { "name": "ds-bot", - "version": "0.2.39", + "version": "0.2.40", "description": "DS Bot: a team of long-lived Bots for DeepSeek Harness, with Main Bots, Bot-to-Bot messages and group chats", "keywords": [ "dsh-plugin", diff --git a/patches/ds-bot/0007-version-and-tooling.patch b/patches/ds-bot/0007-version-and-tooling.patch index b42e52940..d8708375a 100644 --- a/patches/ds-bot/0007-version-and-tooling.patch +++ b/patches/ds-bot/0007-version-and-tooling.patch @@ -95,14 +95,14 @@ diff --git a/package-lock.json b/package-lock.json { "name": "ds-bot", - "version": "0.1.5", -+ "version": "0.2.39", ++ "version": "0.2.40", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "ds-bot", - "version": "0.1.5", -+ "version": "0.2.39", ++ "version": "0.2.40", "license": "Apache-2.0", + "dependencies": { + "@larksuiteoapi/node-sdk": "1.76.0" @@ -733,7 +733,7 @@ diff --git a/package.json b/package.json { "name": "ds-bot", - "version": "0.1.5", -+ "version": "0.2.39", ++ "version": "0.2.40", "description": "DS Bot: a team of long-lived Bots for DeepSeek Harness, with Main Bots, Bot-to-Bot messages and group chats", "keywords": [ "dsh-plugin",