feat(modes): add native compact and extreme surfaces - #4
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dcd53747e0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| boundary. Extreme uses a smaller boundary only when the initial delivered response | ||
| is at least half the size of the exact response; otherwise it passes the exact | ||
| response through unchanged. |
There was a problem hiding this comment.
State Extreme's 50% threshold in the correct direction
For an Extreme response whose projected delivery is more than half the exact response, the implementation passes it through (minimumSavingsRatio: 0.5 and the check in src/result-capsule-store.ts); projection occurs only when the delivered response is at most half the original size. This text says the opposite, which can mislead users evaluating when Extreme will activate. The Chinese README already describes the intended “at least half smaller” behavior.
Useful? React with 👍 / 👎.
Summary
0.2.0-alpha.1line.validate arguments against the original schema before contacting upstream,
and keep exact result recovery through
read_result.public mode evaluation runner, schemas, deterministic evidence, and agent
engineering contract.
Why
The new surface keeps a small, predictable tool interface where it helps Host
compatibility while preserving parameter completeness and recoverable delivery.
Native remains available for Hosts that need the normal authorized catalog.
Validation
npm run ciSafety and scope
migration.
model calls are included.