Analyzing documents

This is the feature that most justifies running AI locally. Contracts, offers, medical records, board packs: the documents worth analyzing are usually the ones you would least like to upload. OOMU reads them on your machine.

Both tools live inside a project. Add your files to the project's Files tab first.

---

Ask Documents

Open a project and choose the Ask Documents tab.

"Ask questions across every file in this project. Answers stay on this Mac and link to the exact source passages."

Type a question and choose Ask. The placeholder suggests the shape of a good one: "Compare rates, payment terms, and key differences…"

What you get back

Three things, together:

1. An answer, written from the passages OOMU actually found.
2. Sources Cited: the specific passages behind it. Each one opens to show the text and its page number.
3. A provenance line: "Answered on this Mac in {seconds}s."

The citations are the point. An answer you cannot trace is a claim; an answer with the clause behind it is evidence. Open a citation and check it before you act on anything that matters.

How it finds the right passages

When you add a file, OOMU splits its text into passages of about 1,800 bytes with a small overlap, each tagged with its page and heading, and precomputes two term sets per passage.

At question time it scores every passage three ways and combines them: a BM25 lexical score for exact term matching, a cosine similarity over semantic terms weighted three times higher, and a phrase bonus for contiguous matches. The top passages, up to twelve, go to the local assistant as the only material it may answer from.

All of it is native code and a local model. Retrieval is budgeted to complete in around 300 milliseconds.

Export it

Export Summary (Word) produces a Word file containing the answer and its citations, ready to send to someone who was not in the room.

If there is nothing to read

"Add at least one file before asking a question." Ask Documents works on project files. Files you attach to a single chat are read for that conversation but are not indexed into the project.

---

Document comparison

Choose the Comparison tab.

"Review aligned clauses, commercial terms, and rate differences without sending source files off this Mac."

Select two to five files and choose Compare selected. You can add focus areas to steer it: "For example: rates, payment terms, liability cap."

What comparison produces

Where a document has no counterpart for a clause, the cell says No corresponding section rather than guessing at an equivalent.

The modal is explicit about where the work happens: "OOMU will align clauses and extract comparable terms locally."

Export it

Export to Word writes the summary, matrix, and redline into a single Word document.

Practical limits

Comparison examines up to 80 sections per document and up to 6 KB per section, with word-level differences computed over the first 320 tokens of a changed clause. For very long contracts, focus areas are how you point it at the part you care about.

---

Files attached to a chat

Separately from projects, you can attach files to a single conversation. Drag them onto the composer or choose Attach files.

The composer reports "Reading document locally…" while it extracts, then shows what it found (page counts, sheet counts, column counts, table counts) and marks each file Ready. Extraction is local in every case.

If something cannot be read, OOMU says which problem it hit rather than proceeding with an empty file: "That document couldn't be read locally," "That document type isn't supported," or "Those files are too large to attach."

---

Which one to use

---

Related

• Setting up a project: getting files in, and the cloud access policy.
• Generating documents: the Word exports these produce.
• Evidence & receipts: why citations and provenance lines exist.