Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
Merge main into fix/kimi-brief-gate-home-marker
AkitaOnRails053218c31fde
diff --cc CHANGELOG.mdindex a7a60364,b1b1f1d3..84fc7350--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -40,13 -117,15 +117,22 @@@ version in [`docs/changelog/`](docs/charejected as containing no extractable text when that was its only cue.WebVTT allows any number of blank lines between blocks; the reader now skipsthem before reading a block.+- Kimi Code gets the compiled project brief on the first prompt of a session+ only, also in a checkout outside `$HOME` whose only `[briefing]` opt-in is+ the operator-home marker. The handoff request takes the home marker as its+ fallback for any cwd, but the once-per-session gate looked for a marker with+ a walk that stops at the checkout root outside `$HOME`. The gate stayed+ shut, no brief marker was written, and every prompt asked for the brief+ again. The gate now reads the same marker as the request (#1665).+ - The startup warning about unusable proxy variables now also fires when the+ user name or password in `HTTPS_PROXY`, `HTTP_PROXY` or `ALL_PROXY` (or a+ lower-case spelling) holds an unencoded `#`, `/` or `?`. The URI grammar+ ends the host at that character, so the client sent provider and login+ requests to a host made of the start of the credentials, such as+ `alice:18080` for `http://alice:18080#[email protected]:3128`, and the failure+ looked like a connection error to a host nobody configured. The warning+ names the variable and the character, not the value, and the network+ behaviour is unchanged (#1637).## [3.2.2] - 2026-10-22