Skip to content

Update from code changes: file lifecycle and delete cascades - #1640

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/54d109e7
Open

mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/54d109e7

Conversation

@mintlify

@mintlify mintlify Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents the new file lifecycle from #1625: chat uploads stage and then live with the conversation, /user/files becomes an explicit keep-shelf, and deleting a conversation or app now erases its files and blobs.

Changes

  • User data: POST /files now stages at /user/uploads/<prefix>-<name>; clients must echo the returned path in the message's file part, and the receiving turn homes the file at /user/threads/<threadId>/files/<name>. Shelf vs. conversation semantics, the six-hour staging sweep, same-name rules, the copy-into-app step when building on a dropped file, a new "Deleted means deleted" section, and a migration warning for hosts that assumed /user/files/... paths.
  • HTTP routes: new Files section for the upload door; thread delete documented as a cascade.
  • Server API: putUserFile clarified as a shelf write, stageUpload on HarnessTurns, and eraseStore's new byThread / byWorkspacePath selectors.
  • Persistence: byThread example and a note that ordinary thread/app deletes already run the full cascade on a SQL-backed store.

Context

Source: #1625

@mintlify
mintlify Bot requested a review from yousefh409 as a code owner August 25, 2026 16:17
@mintlify

mintlify Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

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

Project Status Preview Updated (UTC)
Vendo 🟢 Ready View Preview Aug 25, 2026, 4:17 PM

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.

0 participants