sayan-oai 7e802b22f1 Expose conversation history to extension tools (#23963) ...

## Why

Extension tools that need conversation context should be able to read it
from the live tool invocation instead of reaching into thread
persistence themselves.

## What changed

- Add a `ConversationHistory` snapshot to extension `ToolCall`s and
populate it from the current raw in-memory response history.
- Expose all history items at this boundary so each extension can filter
and bound the subset it needs before consuming or forwarding it.
- Cover the adapter and registry dispatch paths and update existing
extension tests that construct `ToolCall` literals.

## Test plan

- `cargo test -p codex-tools`
- `cargo test -p codex-extension-api`
- `cargo test -p codex-goal-extension`
- `cargo test -p codex-memories-extension`
- `cargo test -p codex-core passes_turn_fields_to_extension_call`
- `cargo test -p codex-core
extension_tool_executors_are_model_visible_and_dispatchable`

2026-05-22 01:11:47 +00:00

..

examples

Make context contributors async (#22491)

2026-05-13 16:43:28 +02:00

src

Expose conversation history to extension tools (#23963)

2026-05-22 01:11:47 +00:00

BUILD.bazel

extension: add initial typed extension API (#21736)

2026-05-11 11:06:24 +02:00

Cargo.toml

Make extension lifecycle hooks async (#23291)

2026-05-18 13:53:58 +02:00

notes.md

extension: add initial typed extension API (#21736)

2026-05-11 11:06:24 +02:00