Heureka
Get Bench

Contents Writing

03

Writing and documents

An editor with the agent wired into the text itself — and a hard rule that it never changes a saved file behind your back.

Most of a scientist's output is prose: protocols, methods, drafts, responses to reviewers, reports nobody else will write for you. Bench treats the editor as a first-class surface rather than a text box next to a chat bot.

The contract everywhere in this section: an AI edit is staged in your buffer, one Cmd+Z reverts the whole of it as a single step, and nothing reaches disk until you save. When something does change a file — deliberately, like adding references — an amber banner asks you to Accept or Keep mine. You are never surprised by your own document.

03.01

The markdown editor

Edit, Preview and Changes — three tabs, no modes to learn.

Edit is a full code editor with the niceties you expect. Preview renders the document, including LaTeX maths, so an equation reads as an equation. Changes is a side-by-side diff of your buffer against the last save — it is how you check what an AI edit actually did before committing to it.

The Changes tab pulses briefly every time an AI edit lands, drawing your eye to the diff without a modal interrupting you. Opening a markdown file collapses the file strip so prose gets the width it deserves.

03.02

Inline edit verbs

Select a sentence, pick a verb, get it back rewritten in a few seconds.

Clarify untangles a sentence that is doing too much. Tighten cuts it down. Grammar fixes it without rewriting your voice. All three work on a selection and return in seconds rather than minutes.

Check refs runs across the whole document and flags citation problems — a reference in the text with nothing in the list, a claim leaning on a citation that does not support it.

They return in seconds, which is what makes them usable for the twenty times an hour you would otherwise sit and fiddle with a sentence yourself.

Selection verbs need Edit mode. Add refs and Review doc work from any mode, because they do not touch your buffer.
VerbWorks onResult goes to
ClarifyThe selectionThe selection, staged in your editor
TightenThe selectionThe selection, staged in your editor
GrammarThe selectionThe selection, staged in your editor
Check refsThe whole documentThe document, staged in your editor
Add refsThe file on diskThe same file, edited in place
Review docThe file on diskA new file in Reviews
  1. Select text in Edit mode.
  2. Pick a verb from the toolbar that appears over the selection.
  3. Review it in Changes, or Cmd+Z to revert the whole edit in one stroke.
03.03

Edits that cannot clobber you

If you kept typing while the agent was thinking, the edit is discarded rather than applied over your work.

Before an AI edit is spliced in, Bench re-reads the exact range it was working on and compares it to what was sent. If the text moved because you carried on writing, the edit is dropped with an inline notice instead of overwriting what you just typed.

There is a second guard on size: a wildly oversized response to a small selection is rejected rather than pasted into your document. Both of these are invisible when everything is normal, which is the point.

03.04

Add references

Hands the manuscript to the agent to find and insert the citations it is missing.

Unlike the selection verbs, this one works on the file on disk and edits it in place — it is a background job with a pill, not a two-second round trip. The feed entry it produces points you back at the manuscript itself rather than at a log about the manuscript.

03.05

Review doc — propose and accept

Concrete, acceptable suggestions in a drawer, not a flat write-up you have to re-apply by hand.

Drop-in fixes show your original text beside a proposed replacement with one-click Accept or Dismiss. Broader structural feedback — this section argues two things at once, this claim needs a control — stays as advisory comments you read rather than apply.

Accepting stages the edit in your editor: one Cmd+Z undoes it, and it writes to disk only when you save. Review works on markdown, PDF and Word documents through the same shared toolbar, and its output is also written to the project's Reviews folder so the critique becomes part of the record.

03.06

Draft Text

Commission a piece of writing — locally, or in the cloud if it is going to take a while.

Point it at what you want written and what it should draw on. Output lands in the project's Drafts folder as a normal file. Long or heavy drafting can be sent to the cloud so you can close the laptop; see Data & analysis.

03.07

Notes on a document

Annotate a passage or leave a free-standing note, and keep them as one list.

Notes on a document are editable cards: quoted, anchored to a selection you highlighted, or free-form. They sit beside the document rather than inside it, so the source file stays clean, and ARC can read them when you ask it about the document.

03.08

PDFs and Word documents

Read, annotate and review a paper or a collaborator's draft without leaving the project.

PDFs open with a thumbnail rail for navigation; Word documents render properly rather than as a download prompt. Both share the same toolbar as the markdown editor, and both support Review doc and document notes — so a reviewer's Word file and your own markdown draft are handled the same way.

03.09

When a file changes underneath you

An amber banner, and a choice: Accept or Keep mine.

If a file is modified on disk while you have it open — by the agent, by a sync, by another application — Bench does not silently reload and does not silently overwrite. It tells you, shows you the difference, and asks which version wins.

03.10

Presentations

Slides authored as text, presented full-screen, kept inside the project.

Lab meeting decks written as structured text rather than dragged into place: themes, a slide editor, a navigator, and a full-screen presenter. Author them by hand or ask ARC to build one from a result you just produced.

Because they are files in the project, the deck you presented sits next to the analysis it presented.

03.11

Chemical structures inside your writing

A smiles fenced block renders as a drawn molecule in Preview.

A protocol or draft can carry the structure itself rather than a description of it. The text you wrote is kept underneath the drawing, so the file is still plain markdown to everything else. See Data & analysis for the rest of the chemistry surface.