3.1.0

Release 3.1.0

3.0.0

Release 3.0.0

2.4.2

Release 2.4.2

2.4.1

Release 2.4.1

2.4.0

A thread is open until someone closes it with DONE. That is the whole state — the earlier third state was a mistake.

Who wrote last is not a state but a point of view, and it now only affects the sidebar:

• Open (default) — someone else wrote last, so it is your turn
• Waiting for a reply — you wrote last
• All open, Resolved, All

An AI agent's work is the mirror image: every open thread where the author wrote last. The block type (ASK, EDIT, REPLY, …) never affects any of this, so a reply phrased as a question cannot go missing.

Review findings from the community portal addressed: authorUrl now points at the profile, document.createElement replaced by Obsidian's createEl helpers throughout, language detection via Obsidian's getLanguage() instead of localStorage, typed settings load, explicit void on fire-and-forget promises, substr → slice, and a CSS property dropped that Obsidian 1.6.5 only partly supports.

The description now leads with what this is actually for: working with the AI tools already on your machine. The plugin itself has no network access.

2.3.0

Who wrote last decides whose turn it is.

Until now the type of the last block decided a thread's state. A reply phrased as a question therefore slipped through: it was a REPLY, the thread counted as answered, and it showed up on nobody's list of open items.

• Last block by the configured author → open (the agent is up)
• Last block by anyone else → answered (the author is up)
• DONE → resolved, no matter who wrote it

The block type no longer affects the state, so an AI agent can use REPLY normally again. Without an author name configured, the previous type-based behaviour stays in place.

Also: the Reply dialog now states that your reply puts the thread back to open.

2.2.1

Clarifies what happens when a resolved thread still carries a work instruction.

• Rule 9 for AI agents: if a DONE text contains an assignment, status and content contradict each other — the status wins. The agent does not carry it out silently but reports it, so the author can turn it into an open block with "Follow up".
• The "Mark as done" dialog now says not to put a new assignment into the closing note.

No functional changes to comments, suggestions or the panel.

2.2.0

Review comments that keep their history: highlight, comment, reply, resolve — nothing gets deleted.

Three states, always taken from the last block of a thread: open (a question or change request is waiting), answered (a REPLY is waiting for the author), resolved (a DONE closed it). A follow-up question reopens a thread, even a resolved one.

• Reply threads with follow-up, reopen and a separate "clear the markup" step (per note or vault-wide)
• Suggestion mode: {++insert++}, {--delete--}, {~~old~>new~~} with accept/reject
• Panel covering this note, the folder or the whole vault, with status/type/author filters and search
• Review report as a markdown file or on the clipboard, plus built-in working instructions for AI agents
• Interface in German, English and Japanese

Fork of obsidian-review-comments by Shota Shirai (AGPL-3.0), with its own plugin id so both can be installed side by side.

Developed with AI assistance; see the AI disclosure in the README.