The drop
A private place per app for what the crew needs to read and cannot find in the repository: database dumps, CSVs, PDFs, CAD files, images, video. Only people who can write the app, and its crew, see it; nothing in it is ever served publicly, and to anyone else (anonymous included) it is not_found.
- Open the app's page and follow Drop (
/<owner>/<name>/drop): it shows the forge's quota (used of total, shared by every app), then a form: choose files, press Send. It works with no script (a multipart POST, up to 32 MiB a request); with script the same button streams each file to the API, so a file of any size up to the limit goes without a reload. With script you can also drag files from your desktop onto the upload row: the page checks each against the file limit and the forge's remaining space before sending, shows a progress line, and reloads when done; a refusal is said in the same words as the API's and nothing is stored. - Each file is a row with its kind, size and a cheap extract: a CSV's first rows, a PDF's text, a SQL dump's
CREATE TABLEschema, an image's size and a thumbnail. Large or binary files have no extract: the crew is told their path. - The crew's next run is told the folder and each file's name, kind and size in its brief — never the contents — and reads them with its own tools. The folder is mounted into the run's sandbox read-only (
readAllowinsrc/crew/sandbox.ts); every other app's drop stays denied. - By API:
curl -T dump.sql -H "authorization: Bearer $TOKEN" "$FORGE_URL/api/v1/repos/<owner>/<name>/drop?name=dump.sql"streams a body to disk (GET …/droplists,GET …/drop/<file>?range=0-4096reads up to 64 KB of a text file,DELETE …/drop/<file>removes). By MCP: thedroptool,action: list|put|read|remove. In the terminal: Drop in the palette while the repository is open (j/kmove,xremoves; a terminal has no drag, so putting a file in is the page's, the API's or the MCP tool's), live as files come and go.
Limits: a file is at most 512 MiB and 500 files an app; the forge's quota is 2048 MB unless FORGE_DROP_QUOTA_MB says otherwise, and a put past it is refused with quota (413) before or while streaming, leaving nothing behind. A file of the same name is replaced.
Where it lives: <data>/drop/<repo id>/<name>, beside apps/ and outside every environment's FORGE_APP_DATA. The nightly snapshot includes it (drop/…); deleting the repository removes it.
Where the code is: src/drop/store.ts (layout, quota, streaming put), src/drop/extract.ts (kind and extract), src/actions/drop.ts (the gate every door shares), src/http/api/drop.ts, src/http/mcp/tools/drop.ts, src/web/studio/drop.ts (the page and its no-script form), src/tui/screens/drop.ts. Tests: test/drop.test.ts.
Not done: a drop for the whole forge rather than per app. The quota is checked again just before a file is kept, so two uploads that began together cannot both land past it.