An intelligent document forge
41\section{Results}4243Our method performs significantly better thenthan44the baseline on all three datasets, as45shown in Table~\ref{tab:main}. The gap widens46with document length: past 16k tokens the47dense model spends most of its budget on48pairs that contribute nothing to the answer.4950\begin{equation}51 \mathcal{L}(\theta) = \sum_i \alpha_i52 \operatorname{softmax}(q_i k_i^{\top} / \sqrt{d})53\end{equation}latexmk -pdf -interaction=nonstopmode main.tex This is pdfTeX, Version 3.141592653-2.6-1.40.26 Latexmk: Run number 2 of rule 'pdflatex' Output written on main.pdf (9 pages, 412218 bytes)
Select a passage and the revision arrives where you are working, as a diff you accept or reject one word at a time.
Everyone in the same document, with comments anchored to the sentence they were made against.
Every citation and quotation keeps a link to what it came from, including the ones the model put there.
The model writes into your paper, one diff at a time.
Select a paragraph, press Proofread, and read the change before you accept it. The conversation stays in its own panel and answers questions; your writing is yours.
The reply has one field, and it holds your passage
The model can only return the revised passage: there is no room in its reply for “Here is the revised version:”. The passage goes straight into your file.
Your markup comes back as you wrote it
Commands, environments, math, citation keys, labels and cross-references survive intact, and so does your line structure — one dropped newline shifts every line after it.
It works from what it can see
Where a change would need a reference, a figure or a number it does not have, the model leaves the passage alone and says why.
Word-level diffs, taken one at a time
Punctuation is its own token, so changing a full stop to a comma marks the comma and leaves the word alone. Reject and the original stands exactly as it was.
Ask about the project, not the open file
The assistant reads the whole project. Ask about a section three files away and it answers from the same box you use for the paragraph on screen.
Runs on Claude Opus
A proofread touches only the passage you selected, and you see the diff before it lands. So we run the strongest model rather than the cheapest.
Every citation keeps a line back to its source.
The Sources panel reads the project's .bib files and lists every entry with how often the draft cites it. The Plan panel does the same for the writing itself: a status on every section, and your TODOs collected underneath as open questions.
main.texRelated work
Suggested for lines 24–25
Open questions · 3
Sources live in the project
Every entry from the project's .bib files is listed in its own panel with how often the draft cites it. Order them by file, by key, by citation count, or unused first.
A missing entry shows before the build does
Cite a key that no .bib file defines and it sits at the top of the panel marked “no entry”, naming the file and line that cites it, before latexmk has to.
The panel follows your cursor
Put the cursor inside a citation and the Sources panel scrolls to that entry, so the reference you are writing about is in view.
Cite without leaving the line
Hover an entry and a plus inserts a citation of that key at the cursor, in the file you have open.
Each section says how far along it is
The Plan panel counts the words in a section's own body and marks it empty, outline or drafted. A section whose subsections disagree reads mixed.
Plan where you write
A TODO, FIXME or XXX comment in the source becomes an open question in the Plan panel, with the section and the line it came from.
A source for the claim you just made
Select a sentence that asserts something and the model will name published work that supports it, ready to add to your .bib. This one is on the way, not in the product yet.
Real-time collaborative LaTeX
- Everyone in the same document
- Edits merge as they arrive, with each person's cursor and selection where they left it. Close the tab mid-sentence and the sentence is still there.
- Comments that follow the sentence
- Anchored to the text itself, so they survive everyone else's edits. Delete the sentence and the comment keeps the quote it was made against.
- Share as an editor or a viewer
- The server rejects a viewer's edits, so read-only is not just a hidden button.
Built to write in
- A real editor
- Syntax highlighting that understands LaTeX structure, not just keywords; a command palette over every file and heading in the project; and panes you can drag where you want them.
- The engine your document asks for
- sharewrit picks the engine from your file — the magic comment, the packages, the fonts — unless you pin one. pdfLaTeX, XeTeX and LuaTeX, with biber and latexmk, all on the server; whatever ran is reported back on every build.
- Two build modes
- A fast single pass for watching a paragraph reflow, and a full run when the cross-references have to be right.