Skip to content

docs: clarify request-size limits and large input strategies - #3963

Merged
aheritier merged 6 commits into
mainfrom
large-input-and-413-docs
Aug 10, 2026
Merged

docs: clarify request-size limits and large input strategies#3963
aheritier merged 6 commits into
mainfrom
large-input-and-413-docs

Conversation

@aheritier

Copy link
Copy Markdown
Collaborator

Summary

  • Explain HTTP 413 troubleshooting and configurable request-size guidance, including the distinction between the agent's limit and proxy/provider/model limits.
  • Clarify the native Docker Agent API versus an OpenAI-compatible chat server, and cover all three inbound HTTP surfaces, including run --listen.
  • Add a canonical decision guide for large inputs: prompt files, stdin, RAG, and attachments, with independent HTTP, local, and model limits.
  • Document remote initial requests versus steer/follow-up attachment behavior, including when attachments must be sent again.

Validation

  • Markdownlint
  • Canonical docs validation
  • Offline link checks
  • Hugo and llms validation
  • Focused request/body-limit tests

@aheritier
aheritier requested a review from a team as a code owner August 10, 2026 18:15
@aheritier aheritier added area/docs Documentation changes kind/docs Documentation-only changes labels Aug 10, 2026
@aheritier
aheritier enabled auto-merge August 10, 2026 19:31
…path rejection UX

Oversized-file rejection is not one shared text/binary rule or one
shared notification path. The TUI applies a single flat size ceiling
to every file reference before it even inspects the file's type,
while CLI/--exec message assembly inlines text up to its own ceiling
and hands supported binary files to a separate, higher-capacity path
-- so a file that clears the CLI/--exec binary path can still trip
the TUI's flatter, lower ceiling.

Only the interactive TUI's /attach command surfaces a visible error
notification (with a file-picker fallback). A bare @path reference is
only checked speculatively as you type, and a rejection there is
logged at debug level only, left as plain text with no on-screen
notice. Outside the interactive TUI, neither the CLI's --attach flag
nor --exec's own /attach parsing -- which reuses the same non-TUI
assembly and rejection path as --attach, not the TUI's notification
flow -- prints anything about a rejected attachment in normal run
output; the message falls back to text-only and the reason is visible
only in the debug log under --debug.
@aheritier
aheritier force-pushed the large-input-and-413-docs branch from 6e72456 to 4e9e234 Compare August 10, 2026 19:32
@aheritier
aheritier merged commit 7e498b0 into main Aug 10, 2026
19 checks passed
@aheritier
aheritier deleted the large-input-and-413-docs branch August 10, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs Documentation changes kind/docs Documentation-only changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants