Skip to content
Editorialist 3.5.1

Getting Started

Editorialist is desktop only — it won’t appear or load on Obsidian mobile.

Install from the Obsidian Community Plugins directory:

  1. In Obsidian: Settings → Community plugins → Browse, search for Editorialist.
  2. Install, then enable it.

(To install a specific version manually, grab manifest.json, main.js, and styles.css from the latest release and place them in <your-vault>/.obsidian/plugins/editorialist/.)

Choose a manuscript target from the line beneath the panel header: a folder, the current note, the entire vault, or Follow Radial Timeline. Folder targets can exclude supporting notes and include or skip subfolders. If you also use Radial Timeline, following its active book is optional. Follow Radial Timeline lists your books and shows which ones have an editor engagement; choosing another book switches Radial Timeline to it too. The regular review-batch workflow works without it; the active-book pending-edits review depends on Radial Timeline.

Manuscript target dialog with A folder selected: the Book folder, Include subfolders on, a Reconnect option for a moved or renamed manuscript, Book/Research excluded, and a preview of 6 eligible notes

Editorialist registers these commands in the command palette:

Command What it does
Open today Opens Today in the sidebar: your editor engagement, the session to do now, the rest of today, what is coming up, and the active book’s edit grid
Open review launcher Opens the launcher modal to import a review batch or start a pending-edits review
Open editor engagement Opens Editor Engagement, with dates, milestones, history, and a revision schedule
Open author planner Opens Author Planner for vault-wide writing goals and schedules
Open editorial project in workspace Opens the active book’s engagement in a full workspace tab
Open line edits Opens Line edits in the sidebar
Open editorialism panel Opens the Editorialisms Panel in the sidebar
Open pending edits panel Opens the Pending Edits panel in the sidebar
Review pending edits in active book Starts the pending-edits review flow across the active Radial Timeline book
End current round Removes remaining feedback from selected batches while preserving manuscript changes and recorded decisions
Write your response to the editor Opens the response window for a person’s pass: replies to comments and reasons for kept changes, saved as a Word letter or into the editor’s own Word file
Anchor selection to editorialism directive Links selected prose to a checklist item
Go to next unprocessed anchor Opens the next unfinished passage anchor
Mark anchor processed and go to next Records the current anchor and advances
Rescan review blocks for cleanup Re-scans scene notes for review blocks that are ready to be cleaned up
Backup selection to cut file Copies selected text to the scene’s cut file without changing the manuscript
Insert author query Inserts a %%query: …%% marker at the cursor so your next review answers it
Write your response to the editor Opens the response window for a pass from a person: reply to their comments and say why you kept changes, then save it into a copy of their Word file or as a letter

Editorialist ships no default hotkeys — assign your own under Settings → Hotkeys if you want them.

Editorialist handles four kinds of work, the same four the Line edits view’s How Editorialist works section describes:

  • Imported review batch: notes from a human reader or AI editor, appended as a review block to the end of each targeted scene. Accept, reject, or rewrite each suggestion, then clean the block away.
  • Editorialisms: a long-form checklist of directives pinned to the passages they concern, kept permanently as its own document in the Editorialist folder. Each scene shows the directives that apply there as you review.
  • Pending edits: the notes in each scene’s Pending Edits property, the revision notes you keep with Radial Timeline, worked scene by scene across the active book.
  • Contributor directory: see which readers, editors, and AI models give the most useful feedback, under Settings → Contributors.

The Revision Plan schedules the first three together against your deadline and shows progress across the whole book.

A five-minute walkthrough of the core loop:

Run Open review launcher and, under 1 Send your scenes out, click Copy instructions for AI. What’s included shows the format. This copies the review batch format, the Editorialism file format, and the scenes of your manuscript target — their scene IDs, or note names for notes without IDs — to the clipboard.

The review launcher: Your editor's Word file with Choose Word file first, then Or work with an AI with two numbered steps, Send your scenes out and Bring the notes back

The formatting instructions are written for an AI — a human reviewer never works from them directly.

AI review: paste the instructions into your AI conversation along with the prose to review. The AI replies with a review batch.

Human feedback: your editor or beta reader works however they naturally work — margin notes on a printed page, comments in a document, an email. Collect their notes in whatever form they arrive (a photo of the handwritten page, the electronic doc) and hand them to an AI along with the formatting instructions. The AI shapes everything into a properly formatted batch for Editorialist, with your human reviewer credited as the contributor.

Word file with tracked changes: if your copy editor or line editor returns a .docx with tracked changes, skip the AI entirely. The launcher’s first card, Your editor’s Word file, has a Choose Word file… button: pick the file and its changes come straight in. See Word files with tracked changes.

For a normal review pass, you want a review batch. It contains scene-targeted suggestions. An Editorialism is different: it is a separate structural checklist for broad guidance that spans scenes or the whole manuscript.

Copy the reviewer’s reply and run Open review launcher again. The launcher detects the review batch on your clipboard — the launcher imports directly when placement is clear, or opens a destination preview when entries need attention. Unplaced entries are flagged before you import the placed work. (If detection misses, choose Paste AI reply; validation runs as you paste.) Editorialist appends a review block to the bottom of each targeted scene note. Nothing has been applied to your prose yet.

Line edits walks you through the pass: each suggestion is highlighted in the editor with a toolbar — apply it, reject it, rewrite it yourself, defer it for later, or back the text up to a cut file first. It advances scene by scene through the batch.

When every suggestion is resolved, the pass completes and the batch is recorded: per-scene polish state, contributor stats, and revision history all update. For a pass from a person, the completion card leads with Write your response to your editor: reply to their comments and say why you kept any change, then save it into a copy of their Word file (see Responding to your editor). Write it before cleaning up, because the response is built from the review blocks. The review blocks stay in your scene notes until you clean them away with Clean N resolved batches… in the panel’s … menu. The Core settings tab shows your progress across the whole book — see the Settings Reference.

Open Editor engagement → Schedule (or the schedule shown before an engagement is created) to see progress across the whole book and schedule what remains. On an empty plan, Auto-plan all N open items spreads every open batch, directive, and pending edit across your working days up to your finish date. You can also add items by hand from Available work.

For one editor’s larger handoff, import line-level work as batches and structural tasks as Editorialisms. Each import files itself under that editor’s delivery, so open … → Editorial deliveries and add the return deadline. Choose Plan this delivery to preview a schedule for just that handoff, using your working capacity and preferred preset. The Revision Plan page explains triage, estimates, locks, and sessions.

Run Open author planner, choose Add goal, and give your goal a target date and a completion description. Optionally give it a number of words to write in a folder, link a document, or follow a Radial Timeline book-stage target. Choose Fill my days to plan sessions for your goals, and for what is due to an editor, against the hours you have. See Author Planner.

To track an editor’s agreed dates before feedback arrives, choose Create engagement in Editor Engagement. Add the documents you will send, your tasks, and shared milestones, then record each send and other activity as the collaboration progresses.

Path What it is
Your scene notes Review blocks are appended here on import, removed on cleanup
Each scene’s Pending Edits property Pending edits, shared with Radial Timeline
Editorialist/Engagement history/ Optional archived copies of explicitly selected reference files
Editorialist/<Book>/ Editorialism structural guidance documents, kept permanently
Editorialist/Word files/ A copy of each Word file you import, so your replies can go back into it
Editorialist/Responses/ Your responses to editors, as Word files
Editorialist/Backups/ Backups saved from Settings → Contributors
<book-source-folder>/Cut/ Per-scene cut files (default location; configurable)

Engagement records, author goals, delivery records, revision plans, and plan progress live in Editorialist’s plugin data; they reference these source files without replacing them.

Headings set in Kalice, Claude Type, designed by Margot Lévêque.