jif 6d15bb3d17 Persist session IDs across thread resume (#29327) ...

## Summary

A cold-resumed subagent kept its durable thread ID but could receive a
new session ID, splitting one agent tree across multiple sessions after
a restart.

Persist the root session ID in every rollout `SessionMeta`, carry it
through thread creation, and restore it before initializing the resumed
`Session` and `AgentControl`.

## Behavior

For a nested agent tree:

```text
root session R
  parent thread P
    child thread C
```

The child rollout stores:

```text
session_id:       R
parent_thread_id: P
id:               C
```

After a cold resume, the child still belongs to root session `R` while
its immediate parent remains `P`. The integration coverage uses distinct
values for all three IDs so it catches restoring the session from
`parent_thread_id`.

## Legacy rollouts

Previous rollouts have `id` but no `session_id`. `SessionMetaLine`
deserialization treats a missing `session_id` as `id`, keeping those
files readable, listable, and resumable. When a legacy subagent is
resumed through its root, that synthesized child ID no longer overrides
the inherited root-scoped `AgentControl`. New rollouts always persist
the explicit root session ID.

6d15bb3d17 · 2026-06-22 09:36:08 +02:00

History

..

src

Persist session IDs across thread resume (#29327)

2026-06-22 09:36:08 +02:00

tests

[codex] Initialize exec-server OpenTelemetry at startup (#25019)

2026-06-18 11:03:42 -07:00

BUILD.bazel

[codex] Move release platform rules into bazel package (#27321)

2026-06-10 19:45:29 +00:00

build.rs

Add WebRTC media transport to realtime TUI (#17058)

2026-04-08 10:26:55 -07:00

Cargo.toml

exec-server: default remote transport to Noise (#26245)

2026-06-15 17:39:00 -07:00