Status and roadmap

packages/core

72

Names, the tree, renaming and moving, the trash and the trash that empties itself, versions, search, changes; the top of the drive for each owner, roles down the tree, Shared with me and what is new in it, links with a password or a number of uses; settings, space, archives, activity, text found in a file, folder colours and placeholders; groups of the application, reached down the tree and in Shared with me. Requests for files read as given, and shares that end.

packages/server

159

The routes on the disk and on an S3 kept in memory, uploads in parts, resumed and given up, quotas, who may do what, sharing and links read without signing in, with a password or for one download, news of what is shared, the same file found again, settings, pictures in sizes, addresses good for an hour, the drive held in memory, activity and text on memory, SQLite and Postgres on PGlite, pages of another origin, and the signature against AWS’s example. Uploads refused before and after they arrive: by beforeUpload, by the type their bytes are, by a ClamAV that knows EICAR, and while it is down; uploads left halfway swept from a bucket and the disk. The events: each told only what they may see, from this process and from another on the same SQLite, and the client coming back after a cut. The drive a piece at a time: what SQLite and Postgres answer to each query is what the drive held whole answers; rows of before filled once; two hundred thousand entries listed in milliseconds, never read whole. Comments, threads, resolved, taken back; a legal hold and a minimum of days; everything of a person exported. onChange, the logger, OpenTelemetry, limits by person, by link and by address. Only the parts of a version that changed sent, the rest copied in the bucket and on the disk. Pictures, placeholders and text made by the server with sharp and pdf.js, a PDF’s first page among them. Copies of a file; requests for files sent signed out, looked at, and reminded of by email; the people and groups of a directory; webhooks signed and tried again; and `onRead` told who read what.

packages/drive

46

The client against the routes and against a bucket: uploads in parts with progress, resumed after a cut, the headers a bucket signed, versions, refusals; the queue of uploads, three at a time, its speed and time left, the same file or name asked about; folders of the computer read as they were; the .zip written and read back; the text of a file; the drive kept in the page; what the server refused, said in each language. A QR code drawn as SVG.

packages/react

18

The hooks in components, against the drive kept in the page: a folder, a search, Recent and the trash asked again after a change through useActions; a view loading as itself, not as the last; useEntry after a rename; settings and the language following them; uploads and their end; what someone else changed shown without asking; and <FileDrive> beside the hooks; and useComments. Starred and received, a copy, a colour, fields and a review through useActions; an entry’s activity, a search by what is written, notifications seen, requests for files and people looked up, what is about to expire and the files of one record, each in a hook of its own.

packages/sync

8

A folder of the disk and a drive behind its routes kept the same: what is made, changed, moved, renamed and taken away on each side, both changed as a conflict kept twice, a folder and a file of one name, the files of the systems left out, a disk found empty refused; and a sync that goes on, run by the drive’s events and by a file of the disk.

examples

5

Next.js, Express, Hono and Fastify, each served on a port and asked over HTTP: a folder, a file of two parts uploaded and read back, and the events of a change; and who asks from a JWT, a forged one refused.

packages/mcp

19

The protocol and every tool over HTTP and stdio, two people’s assistants each doing only what its person may; activity, a search by what is written, folder colours; Rebodocs’ tools on the drive’s Word documents, each change a version; and driven by the official SDK as a client.

apps/desktop

5

Which server the window is of, kept between starts and tried before it is taken; and in Rust (cargo test), a name taken in Downloads made free, a path of the folder synced that would leave it refused, and what is listed, moved and taken away there.

npm run test:browser

72

The playground in Chrome with Playwright: uploads in parts, several at once, stopped and resumed, folders dropped, the same file and the same name asked about; the preview and the viewer; .zip downloads; search by name and by what is written; sharing with Bea, links signed out, one with a password, what is new in Shared with me; the list in an order of one’s choosing, its menu, undo; settings and quotas; activity; folder colours and pictures shown blurred; the keyboard alone; axe on every state, light and dark; the drive with no framework and from the hooks alone; the demo’s Claude through the MCP tools; a folder made and renamed in one window seen in another without loading again; a folder of four hundred, of which only what is in sight is in the page, gone through with the keyboard and the grid; comments said, answered, edited and resolved, axe on them, seen in another window; a legal hold; a PDF’s first page made by the server and shown as it comes. All of it in WebKit too. A copy made from the menu; a share for a week, until when; requests for files sent signed out, with documents and photos, and looked at in Received; the drive without its own bar, driven by the application’s, and kept in a folder.