Files
codex/codex-rs/guardian-context/Cargo.toml
T
Ruslan Nigmatullin 583ec348cf Centralize thread context ID allocation (#62633)
## Why

Response item IDs and context window IDs use separate generator callbacks.
A shared allocator gives history and inference a single API for both.

## What changed

Use `ThreadContextIds` to allocate response item IDs, retained-context
revisions, and compaction window IDs. Move initial window selection into
`InitialHistory` so resumed threads reuse a valid window ID from their
rollout. Give rollout reconstruction its own allocator.

Assign hook prompt IDs through the session's normal response item
recording path.

## Testing

Move the prefixed UUIDv7 item ID test to the allocator crate and add
coverage for JSON escaping in Guardian's item ID token budget.

GitOrigin-RevId: 31232f50648382033506d1f86815ce7c1de78378
2026-11-20 00:44:31 +00:00

28 lines
716 B
TOML

[package]
edition.workspace = true
license.workspace = true
name = "codex-guardian-context"
version.workspace = true
[lib]
doctest = false
name = "codex_guardian_context"
path = "src/lib.rs"
[lints]
workspace = true
[dependencies]
codex-context-fragments = { workspace = true }
codex-history = { workspace = true }
codex-protocol = { workspace = true }
codex-thread-context-ids = { workspace = true }
codex-utils-output-truncation = { workspace = true }
serde = { workspace = true, features = ["derive"] }
serde_json = { workspace = true }
[dev-dependencies]
codex-thread-context-ids-test-support = { workspace = true }
codex-protocol-test-support = { workspace = true }
pretty_assertions = { workspace = true }