Files

Dylan 82ed7bd285 [mcp-server] Update read config interface (#3093 )

## Summary
Follow-up to #3056

This PR updates the mcp-server interface for reading the config settings
saved by the user. At risk of introducing _another_ Config struct, I
think it makes sense to avoid tying our protocol to ConfigToml, as its
become a bit unwieldy. GetConfigTomlResponse was a de-facto struct for
this already - better to make it explicit, in my opinion.

This is technically a breaking change of the mcp-server protocol, but
given the previous interface was introduced so recently in #2725, and we
have not yet even started to call it, I propose proceeding with the
breaking change - but am open to preserving the old endpoint.

## Testing
- [x] Added additional integration test coverage

2025-09-04 16:26:41 -07:00

src

[mcp-server] Update read config interface (#3093 )

2025-09-04 16:26:41 -07:00

Cargo.toml

fix: fix serde_as annotation and verify with test (#3170 )

2025-09-04 10:38:00 -07:00

README.md

fix: introduce codex-protocol crate (#2355 )

2025-08-15 12:44:40 -07:00

README.md

codex-protocol

This crate defines the "types" for the protocol used by Codex CLI, which includes both "internal types" for communication between codex-core and codex-tui, as well as "external types" used with codex mcp.

This crate should have minimal dependencies.

Ideally, we should avoid "material business logic" in this crate, as we can always introduce Ext-style traits to add functionality to types in other crates.