pakrym-oai f3c1283411 Pair thread environment settings (#26687) ...

## Why

Thread cwd and environment selections are a single logical setting in
core: updating one without the other can silently desynchronize the
next-turn execution context. This change makes that relationship
explicit in the internal thread settings flow while preserving the
existing app-server public API shape.

## What changed

- Moved the cwd/environment pair through internal
`ThreadSettingsOverrides.environment_settings` instead of a top-level
internal `cwd` field.
- Kept `thread/settings/update` public params unchanged, with app-server
translating top-level `cwd` into the paired internal settings shape.
- Moved `Op::UserInput` environment overrides into thread settings so
user turns and settings updates use the same core path.
- Updated core, app-server, MCP, memories, sample, and test callsites to
construct the paired settings shape.

## Verification

- `git diff --check`
- Local test run starting after PR creation.

f3c1283411 · 2026-06-08 13:55:15 -07:00

History

..

src

Pair thread environment settings (#26687)

2026-06-08 13:55:15 -07:00

tests

Update rmcp to 1.7.0 (#24763)

2026-05-27 14:52:06 -07:00

BUILD.bazel

[bazel] Bump rules_rs and llvm (#13366)

2026-03-04 01:59:32 +00:00

Cargo.toml

extension: wire extension registries into sessions (#21737)

2026-05-11 11:38:18 +02:00