Docs / Changelog
Open app

Changelog

What changed in each release.

Next

Which copy of the site

  • A client's bar is for commenting and checking — pages, comments, every width and device, the keys — without the designer's inspectors, and shows them the threads they started and those given to them; who a comment is for is the studio's to set.
  • The threads table shows who pinned each comment, and filters by author.
  • A thread can be archived or deleted from its chat in the cabinet and from its card in the bar. Archiving an open thread resolves it first; deleting asks, and takes the screenshots too.
  • A new comment remembers the copy of the site it was written on — live, staging, localhost. The bar marks a thread that began on another copy, the cabinet shows it in the thread and filters by it, and the agent reads it.
0.1.7

For every agent

  • The bar's “who is it for” reads AI agent — whichever agent your team runs — and the CLI's help speaks of the agent, not Claude.
  • The npm page starts from what Notemend is: comments on any site, the cabinet, and any coding agent — Claude Code, Codex, Cursor, Gemini or another.
  • Cabinet: Settings → Integrations shows each agent by its mark, and only the two steps that agent needs.
0.1.6

An agent at work, and what the page logged

  • notemend start <id> (and the MCP tool start): an agent takes a comment before fixing it. Its pin breathes, the thread and the cabinet say Codex is on it, and a second agent asking for it is turned away. done and reopen clear the mark; a mark two hours old counts as left behind.
  • A new comment carries what the page logged before it: console errors, uncaught errors and failed requests, up to 20 lines, with tokens and passwords masked. The agent reads them in notemend; the cabinet folds them under the comment and adds them to a GitHub issue.
  • Pinning a comment on an element that already has an open thread says so, with a link to it — the same note is not left twice.
  • A project's channel: new comments, agents' fixes and confirmations posted to Slack, Discord or any https webhook, set in the project's settings with a test button.
  • The sidebar counts what is new in your Inbox.
  • notemend login signs in with a code you allow in the browser — over SSH and in containers too, with nothing listening on your computer. Settings → Account lists every place you are signed in.
  • The npm package has types for notemend/store, and notemend() returns Astro's integration type.
  • A log of who changed the people — added, removed, a role, a project handed on or moved, agent keys, a deleted project — on the team page and in a project's People tab.
  • Overview walks a new studio in: add a site, put the bar on it and pin a comment, let the agent fix it — each step ticks itself off from what is really there.
  • A thread goes to Linear (a filled-in new issue) or, copied as an issue, to Jira or any tracker — as it already went to GitHub.
  • A deleted thread's number is no longer given to the next one.
  • One-click installs of the MCP server: Add to Cursor, Add to VS Code, a .mcpb bundle for Claude Desktop, and a Claude Code plugin that brings the hooks and the tools together. MCP server.
0.1.5

MCP in Claude Code

  • The MCP server answers with the caching hints the 2026-07-28 revision of the protocol requires, so Claude Code takes its tool list.
  • Cabinet: these docs, at /docs.
0.1.4

The queue as an MCP server

  • npx notemend mcp: list_comments, reply, resolve, reopen and screenshot for Cursor, Codex, Claude Desktop, Zed. Replies are signed with the client's name. MCP server.
  • The menu you pin a comment with stays open while you write; its type and who it is for sit in one row.
  • Suggesting a text and recording the screen are hidden for now, while we find them a better place.
  • Cabinet: redrawn — an Overview dashboard, an Inbox, notifications, every thread filter in one row; Settings → Integrations shows the MCP setup.
0.1.3

Every change shows at once

  • Deleting, resolving, reopening, retyping, editing and giving a thread to someone are drawn the moment you press, then sent; a refusal puts things back and says so.
  • A thread already sent can be given to someone from its card — Claude, anyone, or a person in the project.
0.1.2

Agents beyond Claude, and an agent on its own

  • Codex, Gemini CLI, Cursor and any agent that reads AGENTS.md work the queue; notemend init asks which you use. Your coding agent.
  • Agent keys and notemend init --ci: a GitHub workflow fixes threads and opens a pull request. An agent on its own.
  • Who a comment is for: the AI agent, anyone, or one person.
  • Before and after pictures with notemend shot and done --shot.
  • Check: walk through the agent's fixes on their own pages and widths — Looks right, Reopen, Skip.
  • @mentions, and replies that reach an open page within seconds.
  • Pins tell identical elements apart, and follow things that scroll or slide inside a strip.
  • The type inspector shows WCAG contrast.
  • The CLI has --help and --version, stays quiet in hooks when offline, and works on Windows paths.
0.1.1

The bar on any site

  • bar.js: the bar on Webflow, Tilda, WordPress, Framer or any site from one line. The bar on any site.
  • The sign-in stays with Notemend: a hidden frame from the cabinet keeps it and makes the bar's calls.
  • Google sign-in on notemend.com; the cabinet at app.notemend.com.