.all

Everything your agents ever need.

Make every fileagent-native

The translation layer between human files and LLMs — search, read, patch, and revert like code.

Get early accessScroll to watch a patch land

2f9c1a · read

Reading was never the hard part

Any model can open a file and describe what is in it. The moment it has to change a real range — in place, without flattening structure or losing formulas — the tooling runs out and someone ends up copying values by hand.

@@ workspace · report.docx · §3.2 @@a41e07

-p12Projected growth: 14%

+p12Projected growth: 19% (rev. model)

-p13Source: prior quarter snapshot

+p13Source: live rollup

p14Assumptions unchanged for Q4

+t2Add cache note for agent re-reads

3 additions · 2 deletionsreversible
@@ workspace · report.docx · §3.2 @@a41e07

-p12Projected growth: 14%

+p12Projected growth: 19% (rev. model)

-p13Source: prior quarter snapshot

+p13Source: live rollup

p14Assumptions unchanged for Q4

+t2Add cache note for agent re-reads

3 additions · 2 deletionsreversible

a41e07 · patch

A patch, not a rewrite

An edit is addressed the way a commit is: a range, the value that was there, the value that replaces it. A few spans change. The rest of the file is untouched — including the parts no parser round-trips cleanly.

@@ workspace · report.docx · §3.2 @@a41e07

-p12Projected growth: 14%

+p12Projected growth: 19% (rev. model)

-p13Source: prior quarter snapshot

+p13Source: live rollup

p14Assumptions unchanged for Q4

+t2Add cache note for agent re-reads

3 additions · 2 deletionsreversible

7bd200 · log

Every change has an author

Each write lands as a commit with a timestamp and a parent. You can read the diff before it ships, and you can see exactly which agent touched which range after it does.

  1. 7bd200patchagent://editor2 spans12:04:11
  2. a41e07patchagent://editor4 spans12:04:09
  3. 2f9c1areadagent://editorreport12:04:02
  4. c0ffrepatchkhushangsingla@dotall.dev1 span09:12:03
  5. 0000000initharshitmorj@dotall.devworkspace09:11:47

0000000 · revert

Revert

One call and the document walks back. Structure returns, the history stays intact. Nothing to restore from a backup, because nothing was ever lost.

The layer

Four tools your agent already knows how to hold

Point .all at a file and it exposes the same surface every time: search, read, patch, revert. .all/ caches reads and versions edits — the way .git/ versions commits. What changes underneath stays underneath.

.xlsx.xls.xlsm.docx.doc.pdf.csv.tsv.pptx.ppt.txt.md.rtf.odt.ods.json.xml.html.eml.msg.mp3.wav.mp4.mov.png.jpg.svg.tif.dicom.edf.bdf.nii.dwg.step.ifc.parquet.feather.h5and more

Office first. Media, medical, CAD next. The catalog grows; the tools stay the same.

every · extension · eventually

One interface, every format

Your agent calls the same tools whether it is holding a workbook, a contract, a PDF, or (later) audio, video, and stranger stuff. No per-format glue code to babysit.

.all/ · cache · versions

Remember what you already read

Parse once into .all/. The next session starts warm — cache every read, version every edit, leave the original file where humans expect it.

commit · diff · revert

Every edit is reversible

Each write lands as a commit with an author, a timestamp, and a parent. You can read the diff before it ships and walk it back after it does.

Early access

Make your files agent-native

We are onboarding a small number of teams whose files are load-bearing — docs, spreadsheets, PDFs, whole workspaces. Tell us where you work and we will send an invite when your formats are ready.

One email. No newsletter.