Repository navigation
cmux NEXT composer: remove the ten-attachment limit - #24626
teamleaderleo wants to merge 3 commits into
Conversation
Accept more than ten attachments in the shared composer and New Tab intake, including saved links and restored chips. Keep per-file and byte limits intact and replace the old refusal assertions with acceptance coverage. Agent-Session: https://cmux.com/deeplink/agent?harness=codex&session=01a16a89-20f0-7ff2-8bb0-ec0bb3ae3a5e&host=big-red
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Pending: CI is running on Last result: Unclear: Written by red: cmux-next checks (god files, concurrency, crash safety, l10n); NEW: Gallery before/after for
States
Pick other states with a |
|
Bead |
|
Found 14 test failures on Blacksmith runners: Failures
...and 4 more test failures. View all on Blacksmith: run 40036933419, run 40036933482
|
Allow chat.upload to carry more than ten files while preserving per-file and total-byte limits, and cover the parser with an eleven-file test. Agent-Session: https://cmux.com/deeplink/agent?harness=codex&session=01a16a89-20f0-7ff2-8bb0-ec0bb3ae3a5e&host=big-red
Bugbot needs on-demand usage enabledBugbot uses usage-based billing for this team and requires on-demand usage to be enabled. A team admin can enable on-demand usage in the Cursor dashboard. |
b4ade6a to
1d1b9c9
Compare
Fixes the remaining concurrency and notification-center findings without touching CloudUploads overlap owned by #24626. Focused checks 12/1 findings to zero; injected observer center is retained and tested in isolation. Independent final-head review SHIP.\n\nagent-identity footer
|
Orphaned: no activity for 51 h, and no lane holds a lease on it. The orphan sweep could not merge |
|
Owned by nx-composer on big-red |
|
Claimed and reconciled against the current Current source has no |
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light-3x.png)
The composer and New Tab accepted only ten attachments because the shared intake, pending chips, kept-chip restore, cloud upload path, and native
chat.uploadparser all enforced the same count. That self-imposed count is gone: batches and restored chips can exceed ten while per-file type, size, and total-byte safeguards remain. The native parser now accepts eleven-file uploads and still rejects empty lists, invalid names, oversized files, and total payloads over 64 MiB.Leo said: “the up to ten attachments per message, did we remove that yet? We should just remove it.”
Validation
git diff --checkAgentPaneUploadTests.acceptsMoreThanTenFilesWithinByteAndNameLimits.@base-ui/utils/useIsoLayoutEffectdependency.Changelog
Removed the self-imposed ten-attachment composer limit, including the native upload parser cap.
agent-identity footer
Agent session: big-red