Skip to content

docs(pro): Responses compression coverage and revision-body toggle - #606

Merged
SantiagoDePolonia merged 1 commit into
mainfrom
docs/pro-responses-compression
Jul 28, 2026
Merged

docs(pro): Responses compression coverage and revision-body toggle#606
SantiagoDePolonia merged 1 commit into
mainfrom
docs/pro-responses-compression

Conversation

@SantiagoDePolonia

@SantiagoDePolonia SantiagoDePolonia commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Updates the Pro page for two in-flight changes:

  • Covered endpoints now include POST /v1/responses (lands with GoModel-pro#7), with the Responses-specific exemptions in "What it never touches": replayed reasoning items (PRO_COMPRESSION_DROP_REASONING is a no-op there — the API requires them back verbatim when store is off) and citation-annotated text parts, whose offsets a rewrite would break.
  • Audit revision chain paragraph documents LOGGING_LOG_REVISION_BODIES (lands with perf(admin): slim audit payloads and gzip admin responses #603): default true; off keeps revision metadata but skips the stored rewritten-body copy, roughly halving audit storage per compressed request.

Merge after GoModel-pro#7 and #603 so the docs don't run ahead of the binaries.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Clarified token-compression exceptions for Responses API requests, including replayed reasoning items and citation-bearing text.
    • Expanded documented endpoint coverage to include Responses API requests and tool-call outputs.
    • Clarified audit and revision storage behavior, including the option to reduce audit storage while retaining revision metadata.

Token compression now covers POST /v1/responses (GoModel-pro#7):
document the endpoint, the structural exemptions there (replayed
reasoning items and annotated text parts), and the new
LOGGING_LOG_REVISION_BODIES flag (GoModel#603) that trades the stored
rewritten-body copy for roughly half the audit growth.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 28, 2026 09:24

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Updated docs/pro.mdx to document Responses API token-compression exceptions and coverage, and to clarify configurable revision-body audit storage.

Changes

Pro token-compression documentation

Layer / File(s) Summary
Document token-compression behavior
docs/pro.mdx
Documents preserved reasoning items, excluded citation-annotated text parts, Responses API endpoint coverage, and LOGGING_LOG_REVISION_BODIES storage behavior.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

Suggested reviewers: copilot

Poem

A rabbit reads the docs with care,
Responses details now bloom there.
Reasoning stays, citations align,
Audit storage follows a clearer design.
Hop, hop—each token’s trail is fine!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main doc update: Responses compression coverage plus the revision-body toggle.
Description check ✅ Passed The description matches the template and explains what changed, why, and the merge dependency context.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/pro-responses-compression

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mintlify

mintlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
gomodel 🟢 Ready View Preview Jul 28, 2026, 9:25 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/pro.mdx`:
- Around line 131-134: Update the audit-storage documentation near
LOGGING_LOG_REVISION_BODIES to explain its dependency on LOGGING_LOG_BODIES:
when master body logging is disabled, both original request and rewritten
revision bodies are omitted, while revision metadata remains available. Qualify
the statement that audit entries retain the original client request so it is not
presented as unconditional.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 5c50b865-5052-4d5e-af51-b645793c20a0

📥 Commits

Reviewing files that changed from the base of the PR and between 5a0ed51 and f4aa2d0.

📒 Files selected for processing (1)
  • docs/pro.mdx

Comment thread docs/pro.mdx
Comment on lines +131 to +134
always recoverable. Storing the rewritten body copy is governed by
`LOGGING_LOG_REVISION_BODIES` (default `true`): turning it off keeps the
revision metadata — rewriter, sizes, tokens saved, the block report — while
roughly halving audit storage per compressed request.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Document the dependency on LOGGING_LOG_BODIES.

LOGGING_LOG_REVISION_BODIES only controls rewritten-body copies when master body logging is enabled. With LOGGING_LOG_BODIES=false, the original request and revision bodies are omitted; as written, “Audit entries keep the original client request” is unconditional and can mislead operators about PII retention. Clarify both settings’ interaction here.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/pro.mdx` around lines 131 - 134, Update the audit-storage documentation
near LOGGING_LOG_REVISION_BODIES to explain its dependency on
LOGGING_LOG_BODIES: when master body logging is disabled, both original request
and rewritten revision bodies are omitted, while revision metadata remains
available. Qualify the statement that audit entries retain the original client
request so it is not presented as unconditional.

@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@SantiagoDePolonia
SantiagoDePolonia merged commit fbd83f0 into main Jul 28, 2026
21 checks passed
@greptile-apps

greptile-apps Bot commented Jul 28, 2026

Copy link
Copy Markdown

Confidence Score: 5/5

The documentation-only change appears safe to merge after the dependent implementation changes identified in the PR description.

The documented revision-body setting matches its configured default and persistence behavior, while the gateway exposes the Responses endpoint to registered request rewriters; no concrete documentation defect was identified.

T-Rex T-Rex Logs

What T-Rex did

  • Validated the general contract by ensuring that the complete command output, working directory, and exit status were captured in the log mintlify-pro-docs-02-after.log.
  • Inspected the log artifact to confirm the recorded run details and post-run state are available for review.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "docs(pro): Responses compression coverag..." | Re-trigger Greptile

@mintlify

mintlify Bot commented Jul 28, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
gomodel 🟡 Building Jul 28, 2026, 9:24 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants