Changelog

What changed in each release.

0.1.2722 Oct 2026

No waiting

Claude's answers land at once. Under the dev server the bar keeps a live line to its store: a reply, a fix or Claude taking a thread shows at once on a local project and within a second and a half on a linked one, where it waited for the next look every 20 seconds. Turbo's session notices a new comment within a moment and marks it taken, so the pin shows Claude on it right away.
No more blinking. A change redraws only what changed: pins stay put while a card opens or a reply arrives, faces are not loaded again, a voice note keeps playing, and a reply that arrives while you type joins the thread without touching your words.
A comment stays on its element. A pin on text over two lines — an address, a card with a heading and copy, an animated title — went «not on the page» the moment it was sent, and every one already saved did too: the server keeps the words on one line and the bar compared them with the line breaks. Now the spacing does not count, so those threads find their element again. Pins on icons and other SVG pieces find theirs too, and a removed card no longer hands its pin to the next card with the same words.
Archived is gone. A fix of Claude's that was archived before anyone checked it went on counting as to check — on the project's card, the Overview and Insights — and kept its pin on the page. Now an archived thread leaves the counts and the page whatever state it was in; Show archived and the Archived tab still find it.
On a phone held sideways a thread's card fits between the top and the bar and scrolls under its head, opened at the reply box. The grid follows the page's centred column, not a form that only looks centred. The pins ring shows even a group of two, and closes. The bar's Pages pill and the cabinet's bell have their tips again.
A thread in the studio's space can be given to the studio only — a client given one would have read all of it. In the cabinet any file goes into a reply, spreadsheets and archives too. A status set on a thread someone resolved a moment before is refused instead of landing on it. Removed from a project, the bar says so from the start.
Docs: every heading has a link, and the CLI reference no longer scrolls sideways on a phone.
A pin in a closed menu says so. It is the pin it would be — who has it, its status — faded, with a closed eye at its foot; blue dashes mean only «nobody's yet» now.
«2 new replies ↓». A thread you open with replies since you last read it opens where it was, and a pill at the foot of its messages says how many are below — a press goes down to them. A reply that lands while you read further up adds to it instead of pulling you down.
Your own width, not a frame. Picking the width your window already is — Laptop on a laptop — shows the page itself again; before, it put the page in a frame of that same width. Desktop on a narrower window still scales the page into a frame.
The bar keeps out of the way. Esc puts down the inspector or the grid in hand. A pin whose element scrolled under the site's sticky header waits out of sight with it, instead of sitting on the menu. The outline under the pointer follows a scroll. A pin in a closed card names that card, not the first one beside it. Hidden away, the bar is out of the Tab order too. Deleting from a panel row asks first, as the card does. A finger held on the page in comment mode no longer opens the phone's menu. A thread's pin tells a screen reader who has it. The page's log a comment carries skips the browser's resize-observer noise and counts a repeated line instead of repeating it.
The cabinet, quicker and straighter. Opening and closing a thread no longer redraws the whole table, and a page asks the database half as often. Resolving from the thread keeps it open. The open thread keeps its place in the list while you answer it. A page's row in Pages opens its own threads. Invite shows only to those who may invite. A link to a tab you cannot see opens the one you can. «Project created» shows on the new project. The people log records the lead and the invite and guest links. On /threads its own keys no longer reach the dev bar too.
Pins with the page. The bar draws the last threads it saw the moment it starts, and under Astro its first reads leave with the page itself, so pins appear about three times sooner on a cloud project; it also does half the work while the page loads.

0.1.2621 Oct 2026

Reopened, and one way to show a person

Who reopened it, and who resolved it. A thread someone sent back shows a quiet «Reopened by Mark · 10:20» line among its messages, in the bar's card and the cabinet — gone once it is resolved again. A resolved thread says who resolved it and when, to a client too.
One way to show a person. People and Admin show someone as a project's People does: the name in semibold, @nickname and (you), the email under it.
Counts by state — on the Overview, a project's Pages and Admin — are set the same way everywhere: each dot close to its number, the states a step apart.
A project's People: «Client comments go to» takes a third of the row like the invite and guest links, instead of a sliver, and the log below keeps its distance. «Type … to confirm» above a delete stays on one line.
A pin says who has the thread. Nobody yet: the writer's face in a dashed blue ring. Someone took it: the writer, then whoever took it, in one pill ringed in the status's colour — one face when the writer took it herself. Their Claude sits at the foot of their face in its step's colour and breathes while it works, so a page says whose Claude is on what. Pointing at a pin says it in words.
On phone, signed in. The project's QR code now signs the phone in as you: scan it, press Open, and the site opens there with the bar ready — no sign-in on a small screen. A code works once, for 10 minutes, and a new one is made each time it is shown. The code sits square in its frame.
Threads: the filters — author, page, width, type, assignee — are always out under the states, no Filter button to press first.
You know when you are in the clients' space. The spaces pill is a switch; in the clients' space a thin frame of their colour goes round the page, glowing for a moment as it appears, with Clients space in a notch at the top and a × back to the studio's. Switching fades the pins, an open card and the panel out and back in.
Filter the pins. A ring after the spaces pill shows whose this page's pins are — nobody's in blue, yours in your colour, everyone else's in grey — with the count in the middle. Press it (or F) to show only nobody's, yours, everyone else's, your Claude's, the ones you wrote or the ones to check; the rest dim, still a click away.
Claude's fix reads the same everywhere. In the cabinet's thread, a fix waiting for your look is the bar's card — Claude fixed it, the note, Looks right and Send back in words — and Claude's other messages no longer wear a tint that looked like your own.
Links read as names. A link in a message shows as a chip — Figma · Notemend, GitHub · notemend #42, or the site and the page — in the bar and the cabinet; it opens in a new tab, the whole address shows on hover and copies as it was written.
Pages says more. Each page shows its name over its address, a line of how far it is, its open threads by status, who wrote last and when, and its sign-off — threads left, Approve once nothing is left, or who approved it and when. Pages that need someone come first.
A client's own thread stays theirs. A thread a client wrote can be duplicated to the workspace, no longer moved there: they read every thread they wrote, so a «moved» one still showed them the studio's replies. In a workspace thread, @ offers the studio only.
Pins stay on their element. A pin no longer counts the bar's own pieces of the page when it finds its element again, so pins on sites with plain body-level blocks stop going «gone» or hiding in the bar. When several elements have the same words and none sits in the pin's block, the thread says it is gone instead of jumping to a lookalike.
A reply that did not land is not lost. It goes back into the box with Retry, and stays saved while it is sent — a sign-in that reloads the page brings the words back.
When the server refuses something it says why — «Comment was not saved: …» — instead of a bare code; files a box would not take are counted in a toast when you send; a removed teammate is told they are no longer in the project.
Two identical files in one message both arrive.
On a phone: a pin can be dragged with a finger and has a bigger target; your own reply scrolls into view; turning the phone with a thread open closes it cleanly; a short screen keeps the reply box on screen.
Desktop in a narrow window shows the page at desktop width, scaled to fit, with its pins.
A blocked microphone says so for longer, and the bar points at the browser's prompt while it waits.
The team page says when it could not load, with Try again, instead of showing one person; a project opens even when names do not load.
Esc closes search even after a click outside the search box.
The sign-in window from a site says what is actually wrong: a broken link, a failed load, or a project you are not in. The unsubscribe page points only to settings that exist. An expired confirm link explains itself.
Docs: the panel is called Threads everywhere; the start guide says where to find the project id; new sections on handing a project over, deleting it and Insights; the CLI reference reads on a phone.

0.1.2520 Oct 2026

Client mode, reactions, unread in the panel

Files up to 50 MB from the bar. One past 3 MB goes straight to storage once you send — the box says it will — and lands in the thread; the cabinet takes 50 MB too.
Looks right resolves. The answer to an agent's fix closes the thread, in the bar and the cabinet, as the tick does. Accepted stays in the status list.
Who said done. «Mark says done — check it» names whoever set Needs review, not whoever the thread is given to.
Two status changes in a row no longer lose the second one as «changed by someone else».
Clients and guests. A client's bar shows the project's owner and its lead — the lead now by name and face, so a guest's comment goes to them, not the owner — and no other address of the studio. On someone else's thread a client reads and answers; Resolve, Archive and Delete are on their own threads only. A guest opening the link again is welcomed back to their notes; People, Team and Insights are the studio's.
Only a project's owner and admins set its webhook and its guest link. A webhook goes only to a public https address, local servers included.
A thread's card fits a phone: it opens where there is room, its messages scroll, the reply box stays above the bar. Line breaks show, and the box counts down near its 10 000 characters.
Threads: the project filter and the tab are in the address, a link to a thread keeps its project filter, and the list shows a skeleton while it loads. Esc and the arrows in a menu stay in the menu; closing a thread puts focus back on its row.
A site at localhost:3000 is saved as http. A password missing a digit is said under the field; a repository the database refuses says so. A session ended elsewhere asks you to sign in again instead of a dead end.
Each page's tour covers what it hides: bulk actions, filters you can share, a client's lead, guest links, push mode.
One set of names. A thread is Open, With agent, To check, Resolved or Archived — the same words in the bar and the cabinet. Needs review is To check, Approved for AI is With agent, a thread nobody has says Anyone, and the bar's panel is Threads.
A guest signs in once. After the name, the site opens in a tab of its own with the bar ready — no second «Sign in to comment».
Drafts that are not work go. A comment of a few letters closed without sending is dropped. A longer one shakes on the first close and is kept as a draft on the second, as in Figma.
Picking someone from the card's person menu shows their face at once — it used to wait for the next refresh.
Studio and clients. Two spaces in a project, switched by a pill left of the bar (M): the studio's threads, and its clients'. A client's thread never reaches the agent — it is duplicated or moved to the workspace from the card's ⋯ menu, and a resolved copy tells the client Fixed — please check. The eye and «Team only / Team and client» are gone.
Who and what, at a glance. A row in the panel shows the author's face with where it stands as a badge — a tick once resolved, the box once archived — and the type as an icon beside the number and the time.
A copied link opens its thread, in its space. A client sees the status of their threads and reopens a resolved one from the banner or the ⋯ menu.
Accepted is gone. A fix that looks right resolves the thread, so the status between was one more green to tell apart from Resolved. Threads that had it are resolved now.
One tooltip. The bar and the cabinet show the same hint — black, small, after a moment — that never runs off the screen or hides under a card's edge. The browser's slow native hints are drawn the same way now.
Grid on any site. A site without its own .container and .grid classes gets 12 columns over its centred content instead of nothing.
Spacing on a button. Pointing at an icon button measures the button — its size and the gap beside it in its row — not the group around it.
People in a big workspace load fast again: who you can see is worked out once per request, not once per person.
Emoji and reactions, as in Figma. The reply box has an emoji button in the bar and the cabinet. Under the comment and each reply, react with an emoji — six at hand, more behind ⋯; a chip shows how many, lit when one is yours, and its hint says who. Anyone who can read the thread reacts, clients and guests too.
Who wrote the newest line. A panel row shows the thread's author, and the newest message under it; when someone else wrote that message, their name comes first, so a reply no longer reads as the author's words.
A thread whose text suggestion holds a long address no longer scrolls sideways in the card or the cabinet.
New in the panel. A thread with messages you have not opened yet is tinted blue in the bar's panel and carries the pin's blue dot; rows are parted by a thin rule.

0.1.2416 Oct 2026

Push mode of its own

Two ways for a session to take comments. /notemend:turbo is live: each comment for Claude is taken as it lands. /notemend:push is in batches: the session takes nothing by itself until someone presses Push to Claude, then the whole batch at once — and again for the next.
Push to Claude is one round button beside Turbo, always there: Claude's mark, how many wait as a badge, the words in its tip. Lit in push mode, quiet while turbo is live, grey with no session — then a press copies /notemend:push. A right click or a long press picks pages and threads.
While Claude works a batch, the button wears an amber ring that breathes, with how many are left; when the batch is done, a toast says so with Check, which walks the fixes one by one.

0.1.2315 Oct 2026

Push to Claude, as it was meant, and pins you can drag

Drag a pin, as in Figma. Inside its element only the spot moves; past the element's edge the one under the pointer lights up in orange — Move to h3 «Fair» — and takes the thread when you let go. Esc puts it back, a toast undoes it. The writer and the studio may move a thread; a client only their own. A click without moving still opens it.
Turbo live or paused, and Push to Claude. Turbo on takes each comment for Claude as it lands. Paused, they wait — and Push to Claude beside it sends every one marked for Claude to the session at once, no word in the chat; the arrow picks pages and threads, and what is left waits for the next push. Undo for five seconds. With no session listening, the button copies /notemend:turbo. (In 0.1.22 it handed out comments nobody had — that was a misreading.)
The page round an open card is only dimmed now, not blurred — the text around stays readable.

0.1.2215 Oct 2026

Any file, resolved apart from the archive, Push to Claude

A gear for the keyboard. The last button of the bar opens settings: who you are signed in as, Keyboard shortcuts (their list in the same menu, with a way back; ? still opens it), Hide the bar and — with bar.js — Sign out on this site.
Give a thread from the panel. Hovering a row shows the card's slider — a person, Anyone, Claude — so a thread changes hands without opening it; the face opens the people, and Claude's stop wears its step in place of the separate mark.
Comments on hidden elements. A comment on something inside a closed menu, a popup or a hover card no longer loses its pin: a dashed one waits where it will show, and moves onto the element once you open it. The card says Hidden right now with Show where; the panel marks the row hidden, or gone for an element no longer on the page.
Focus on the element. While a card is open — a new comment or a thread — the rest of the page dims and blurs a little, and the element it is about stays lit. The bar, the panel and the pins stay above it; a press outside does what it did.
Any file in the conversation. The paperclip, paste and drop take any file but a program (.exe, .dmg, .sh…) — sheets, slides, archives, design files — beside pictures, which keep their own button. A file shows as a chip with its kind on a tile (PDF, XLS, ZIP, FIG…), opens in a tab when a browser shows it safely, and has a download for everyone who sees the thread. A file the box will not take stays in it, red, with why. Up to 3 MB from the bar, 10 MB from the cabinet (50 MB both, since).
Resolved and archived apart. Resolving turns the pin green and keeps it on the page until someone looks: the card says Resolved by Ivan — check it, with Looks right (archive it) and Reopen. The archive box beside the tick, and Archive in the status menu, put a thread away — its pin greys and goes, with Undo. The panel has Show resolved (R) and Show archived (A), a Resolved group with Archive all, and Check fixes walks the resolved threads too. Threads closed before this release are in the archive. In the cabinet: an Archived tab, Archive in the selection, and per project Auto-archive — resolved with no reply for 3, 7, 14 or 30 days goes by itself.
Push to Claude. Beside Turbo, one press hands every comment nobody has — on every page — to Claude, approved, so a listening session takes them at once; the arrow beside it picks pages and threads. People's threads, Claude's own and a guest's waiting for the studio are left alone. Undo for five seconds.
A new comment goes to whoever the last one went to, for as long as the tab is open — no picking Claude for every one of ten.
In an open card, a line under the status row, which stays put while the messages scroll.
The pages button names the page in three words at most.
The overview counts what is yours. Its numbers, Up next, projects and hot pages count the threads on you, on your agent, or given to Claude by you; Everyone beside Review shows the whole workspace, and the choice is remembered. The inbox holds only threads on you and mentions of you.

0.1.2115 Oct 2026

A faster bar, and a tick that never waits for a picture

A tick never waits for a picture. Resolving sends the status at once and the element's after frame behind it — on a page full of pictures the frame took seconds, and a reload inside that wait (an edit's HMR, say) lost the tick while the card already showed it done. A new comment's before frame follows the same way, a small write already on its way survives a reload, and a poll no longer undoes a change for a moment while the write lands.
On screen sooner. The bar's code is one file instead of twenty-two; the open threads are asked for together with the config and drawn first, the resolved ones follow behind when Show resolved is on; a poll that finds nothing new is one call, and the team is read once a minute. On a busy dev server the pins show in about half the time.
One thread written, not the project. In a linked project a status, a reply or a type goes as one row (the cabinet's patch_thread) rather than the whole document back and forth — a tenth of the traffic on a project with a hundred threads, and no race with a teammate's write. The page's logs stay in the store for the agent instead of riding to every bar.
On Next.js the bar no longer waits for React to hydrate before it appears; only its marks on <html> do. bar.js: the keyholder frame starts the bar's first reads while the bar itself downloads, and a hosted site's menu reads only its threads' paths.
Pick the language. The ▾ beside Translate, in the bar and the cabinet, puts a message into Ukrainian, Russian or English; Translate alone still uses your browser's.
Edit and Delete on your reply sit side by side instead of at opposite ends of the line.
A teammate's change is not overwritten. In the cabinet, a status, priority or assignee you set on a thread someone changed a moment before you is refused with a note to look again, instead of quietly undoing theirs; a reply still lands. A lost connection says “You are offline — nothing was saved” instead of Failed to fetch, and errors stay on screen long enough to read. Signing in on a new browser opens the workspace your projects are in, not an empty Personal.
One To check everywhere. A thread a person set to Needs review counts as To check in the thread's header, Insights, the overview and the project list, as it already did in the bar and the Threads tabs; Activity says “confirmed” only for a thread that is resolved.
Signing out signs the bar out. After you sign out of the cabinet, bar.js on your sites stops answering as you within a minute, instead of until its token ran out — someone else at the same computer no longer comments in your name.
bar.js: a client's comment goes to the person the picker shows (it could go to a lead the client cannot see); a comment or reply with only a picture is sent; on a phone the comments panel ends above the bar and steps aside while a thread is open; a lost connection says you are offline instead of “(503)”; something a client may not do answers 403 with the reason, not 500. In the cabinet /threads?project=… opens that project's threads.
The comments panel numbers each thread as the pin and the cabinet do (#68, not “#3 on this width”). While you comment, a short page scrolls far enough for its footer to clear the bar. On a phone the card you type in moves up above the keyboard. Enter on a half-typed @Cl picks Claude even when a refresh closed the list, instead of sending “@Cl”.

0.1.2014 Oct 2026

Comments at every width, the agent in its status colour

Tablet and phone widths on any site. A site that loads bar.js only outside frames — a guard for a CMS preview — left the bar's breakpoint and device copy without the bar, so nothing could be commented there. The bar now hands the copy the same line itself.
The agent's mark wears the thread's status. In the card's bar, on the slider's knob and in the step banner it is the colour the pin already was — blue queued, amber working, pink asking, red quiet, violet to check, green accepted — not Claude's clay. The cabinet's mark and its Approved for AI follow.

0.1.1914 Oct 2026

Nothing lost, and a tighter guard

Nothing you write is lost. A comment or reply sent while the dev server restarts stays in the box; notemend done --shot, shot and the MCP tools no longer write over what the bar saved while they took the picture; the bar, the CLI and the MCP server no longer share one temporary file. A new frame from the CLI replaces the old one instead of piling up.
A quieter dev server. A local store answers “nothing new” with an empty reply instead of the whole file every 20 seconds; on Next.js with a linked project the same answer no longer fails. Pins keep their element between frames and only measure while you scroll.
notemend reopen and the MCP reopen send the thread back as the bar does, not as Claude asking. @Ann is found after @Anna. The bar stays when a page removes an open dialog, starts when the browser blocks storage, and the Turbo switch sits inside the bar on a phone. The person stop is hidden where there is nobody to give it to.
Clients can finish what they see. In the cabinet a client attaches files to a reply on any thread they see, resolves a thread given to them, and sends an agent's fix back to the agent. A thread is checked against its newest version, so a live update never puts an older one back; a failed load says so with Try again instead of an empty account.
bar.js is a 3 KB loader. A visitor who isn't signed in downloads only that; the bar itself, its styles and the screenshot code come after sign-in, each cached for a year by its own version.
One thread at a time. An edit in the cabinet writes only its thread, and other tabs take the changed thread live instead of reloading the project. Screenshot links in the bar stay the same between polls, so pictures aren't downloaded again.
Issues sent to GitHub or Linear carry week-long screenshot links and open in a tab Safari doesn't block. The Accepted banner shows the day when it isn't today.
Security. An app connected through the MCP sign-in reaches only the MCP: it can't make a session of its own, delete the account or change projects, people, hooks or keys. The cabinet's preview hands a session only to the project's own site or localhost. Guests and clients can't change project settings, sign a message as an agent, or set a thread number that stops new threads. Agents get only threads approved for them; threads waiting for the studio's approval stay out of all. Push goes only to the browsers' push services; voice notes and Translate have daily limits per person, per project and overall. Pages run no script the server didn't sign. The old /cli?port= sign-in is gone — update with npx notemend@latest login.

0.1.1813 Oct 2026

Unassigned, three ways to take it

A thread nobody has says Unassigned — it was “Anyone can take it” — with three equal presses: the tick to take it yourself, the agent's mark to give it to Claude, and the people to give it to someone else.
The comments panel's search sits as far from the line above it as from the panel's sides.

0.1.1713 Oct 2026

Faces and agents on the page, a panel you can search, Accepted

A person's pin is their face in their own colour — the one the cabinet gives them — ringed in the thread's status, with a gap between; a blue dot on its corner says something is new since you last opened it.
An agent's pin, any agent: a solid circle with the mark, in the colour of the status its step turns the thread to — blue queued, amber working, pink asking, red quiet, violet to check, green accepted. In the card's bar the mark is whole, in its step's colour, rather than partly lit.
One face for every agent: the mark in violet on nothing, in the bar and the cabinet — no more Claude clay.
Anyone can take it. A thread nobody has yet shows a banner over the reply box with Take and a list of people to give it to; the slider's middle stop, and the cabinet's, read Anyone instead of Nobody.
The fix is the check. When the agent says it is done, its message is a card — Claude fixed it, what it did, Looks right and Send back — in place of the “Done — check it” banner.
Search and a filter in the comments panel. Find a thread by its words, its replies or who wrote it; the filter beside it, as in Figma, shows For me, Agent or All with their counts and orders by Newest or Unread first, and turns orange while it is set. A search that finds nothing says so, with Clear search. Each row starts with its writer's face ringed in its status, or the agent's pin.
The pages menu counts all six statuses — a chip per width and status, in the status menu's colours.
Checking fixes: the bar across the top keeps the count, the arrows and the three answers, without the fix's words.
In an open card the status row sits as far from the first message as from the line above it — 14px each side, not 22 under it.
Comments work in the device preview on a site with bar.js: the copy of the page there makes its calls through the page's own sign-in instead of needing one of its own, which some browsers — and the cabinet's preview — never gave it.
A card's tips are no longer cut at its edge — the slider's “Anyone — nobody has taken it yet” reads whole.
Accepted is a status of its own: the tick in a “check it” banner accepts the fix and keeps the thread among the open, “Accepted · 16:35”; the tick in the card's bar resolves it and moves it to Resolved. Accepted is in the status menu too, between Waiting and Resolved; no agent takes an accepted thread.

0.1.1612 Oct 2026

Statuses you can always set

The status is always a menu, Resolved among the choices — on Claude's threads too, where it follows Claude until someone picks one; another status reopens a closed thread.
The tick in a banner closes the thread and keeps the card open on it, Accepted; the tick in the card's bar still closes and hides it.
Sending a fix back, or reopening, returns the thread to whoever did it — Claude's queue, or the person, in progress — instead of reading Claude's last message as a question.
The type menu lists the six types without their hints.

0.1.1512 Oct 2026

One agent, a quieter card, documents and Translate

One agent, and nobody by default. There is one agent, Claude — no “My agent”, “Any agent” or a teammate's. A new comment is nobody's; the card's foot slides between a person, nobody and Claude, icons only. On Claude's threads the status follows Claude by itself; a person sets their own. @Claude in a reply hands a thread over; taking it back while Claude works asks first.
A quieter card. The bar shows the element's name with its path on hover (no ⓘ), Claude's mark — grey and a button while the thread is not Claude's — the tick, and ⋯ for who sees it and delete. An eye says the client sees it. Banners are one line, and only where something waits on you: Claude's steps, a fix to check, a closed thread. Priority and type moved to the foot, the type as an icon — two new ones, Design and Content. The cabinet's thread follows the same rules.
bar.js asks for its styles by their own version, so a cached copy of one never meets the other's older half.
The agent's way, on the card. The agent's mark sits in the card's bar the whole way now, not only once it says done: its rays fill as the thread moves — queued, working or asking, done and waiting for you — in that step's colour, and its tip says the step. A banner over the reply box says it in words, with the one or two things to do as icons: give it to the agent, take it yourself, resolve the fix or send it back, reopen. A run that went quiet says so. The cabinet's threads wear the same mark and banner.
@mention an agent. The @ list offers agents beside people — Any agent, your own, a teammate's, by the name its person gave it. Naming one in a comment or a reply hands it the thread, approved; a closed thread opens again. The studio only — a client's @ list has people.
PDFs and Word files in the conversation. The paperclip — in the bar and now in the cabinet's reply box — takes a PDF or a .doc/.docx beside pictures; paste or drop works too. It shows as its name under the message, opens in a tab, and the agent gets it as a file. Up to 3 MB from the bar, 10 MB from the cabinet.
Translate. Under a message from Claude or a teammate, Translate puts it in your browser's language in place; Original brings the words back. In the cabinet and the bar.
Admin: confirm an email by hand, sign an account out everywhere, copy a password reset link; give a project to another account or delete it. Each lands in the log with what it touched.
bar.js on a site turns a voice note into words again — the frame it talks through let only the threads past.
Tours no longer start by themselves. The ? at the foot of the sidebar plays the product tour or the page's, when you ask.
notemend done <id> --shot and notemend shot file the element as the thread's after frame (--before: the before one), beside the bar's pictures above the conversation — not as a picture in a message.

0.1.1410 Oct 2026

Worksection's statuses, and a tighter guard

The database keeps what the screen kept. A client or a guest hands a thread to an agent only through the studio: giving it to Any agent or the studio's agent is refused, their own agent stays theirs. A client signs only with their own name; a thread's page is a path and nothing a browser reads as another site; a client sees the screenshots and voice notes of the threads they see, no others; a client is not shown the project's other clients; a thread stays under a quarter of a megabyte; a guest starts no projects or teams.
The bar: a teammate's name in the card's slider is escaped; the dev server's voice endpoint refuses other sites; the pictures of a reply you deleted go with it instead of landing under the message before; a deleted reply no longer counts as the thread's last word or in “N replies”; notemend start refused by another agent writes nothing; done as Claude clears an earlier agent's name; npx notemend login sends its secret in a header, and the Allow card says where the terminal asked from.
Reduced motion covers every pulse and spin in the bar; one easing for its moves; the pins resolve their element once per frame.
The cabinet: a reply stays in the box until the write lands; errors show as errors; “To check” is one number on the Overview, the Threads tab and the project chips (an open thread with Needs review counts); reopening clears the review; the inbox, the KPI strip and the sidebar hold on a phone; Needs review, In progress and Waiting are tokens in both themes.
Four statuses, as in Worksection: New, In progress, Needs review, Waiting — a diamond that fills as the thread moves on, and the pin's ring wears its colour. Resolving is the tick in the card's bar. No agent takes a thread in progress or waiting.
Who takes it: the person stop shows who it goes to by face — a photo or two initials — and the knob slides between the stops. No chevron in it.
A reply of yours can be deleted, not only edited. @mentions are marked in blue; the mention list puts each email under the name.
One mark for the agent, whichever it is: twelve rays in clay — in the bar, its pins and the cabinet.
Your agent, your way. Integrations → Your agent: give it a name and a picture, and its messages, the slider and the agents' menu wear them instead of “Claude · you”. Left empty, it is the mark.
Install: Shopify in place of Tilda — layout/theme.liquid, before </body>.

0.1.139 Oct 2026

A status on the card

A status pill beside a card's type in the bar: Open, In progress, Needs review, Resolved. In progress means a person is on it — no agent takes it; the cabinet's Status menu has it too.
Who takes it is two stops now, a person or an agent — Nobody is gone. You are among the people; Any agent, the shared queue, sits last in the agents' menu, apart from the ones that are someone's.
Pins are a little smaller.

0.1.129 Oct 2026

Before and after, faces, and fewer buttons

Who takes it, as a slider. A card's foot has one control in place of the “for” pill and the AI / Review switches: Person · Nobody · Agent. The lit stop is a picker of its kind — My agent, Any agent, a teammate's agent; or a person. Sliding onto the agent approves the thread for AI; sliding off puts it back to new. Needs review stays in the cabinet's Status menu.
Before and after. Pinning a comment takes a picture of the element as it is, and confirming the fix in the bar takes another. A thread in the cabinet shows them above the conversation — press one for full size, ← → to flip between them. Drawn from the page itself, so no screen-sharing prompt; a few kilobytes each.
Fix now is gone. Approving a thread for the agent is the one way to hand it over; a paused turbo stays paused.
Faces in the bar. An open pin wears its writer's photo (or initial), ringed in its type's colour; who a card is for, and the @mention list, show each person's face beside their name — a teammate's agent with a clay ring.
No more archive. Resolved is where a finished thread goes; the archive button, tab, bulk action and E are gone, and threads archived before are listed under Resolved.
An agent's message run as a teammate no longer pushes its name to the far edge of the thread in the cabinet.

0.1.119 Oct 2026

Whose agent, and colour & border

Each person's own agent. A comment goes to My agent (the default for what you write), a teammate's agent, or Any agent — the shared queue, a GitHub agent's too. Your agent sees the shared queue and its own, never a teammate's; its replies read “Claude · Ann” with Ann's face in its corner, and “Ann's Claude is on it” says whose agent took a thread. The database lets an agent sign only as the person it runs as. Agents.
A status apart from who. A thread is New until someone says go, Approved for AI — an agent may take it — or Needs review: done by a person, waiting for another to check it and tick it closed, its pin violet. On a card on the site they are the two switches in its corner, AI and Review (pressing the lit one puts it back to new); in the cabinet a Status menu beside the assignee, ✦ on a thread and a row (A), and Approve for AI for every selected thread. An agent takes only approved threads; only the studio approves — a client's comment waits for it, as a guest's does. Threads given to an agent before this count as approved.
Your agents in Settings → Integrations: each agent you run, how it was installed and its version, with Update where it is behind and how to update that copy. npx notemend --version says when npm has a newer one, and npx notemend tells the agent to pass it on. The install commands now use notemend@latest: npx kept the first copy of a plain notemend for good.
Colour (O) and border & radius (B) inspectors in the bar: fill and text colour; border per side, its colour and the radius per corner — each colour by the CSS variable it was written with, read from the page's own rules. The type inspector names its colour the same way.
A card's type and who it is for sit above the conversation, smaller; who sees it — the team only or the client too — is a person, or a person struck through, beside delete. Priority is four signal bars at the card's foot — one lit per level — Low unless set, and a press steps it on — Low in green, Mid, High, Urgent in red — with no menu; the cabinet reads a thread with no mark as Low too, and Normal is now Mid.
Turbo no longer wakes for a thread another person's agent took.

0.1.109 Oct 2026

Voice notes, and what a client sees

Team only, or shared with the client. A thread the team writes is the team's own unless marked Shared with client — a pill on the thread in the cabinet and on the card in the bar. A client is handed only their own threads, the ones given to them or mentioning them, and the shared ones; until now the rest was only hidden on screen, now the database keeps it. A client's reply on a shared thread works as before.
A client's comment goes to a person. It starts with the project's lead (Client comments go to in People; the owner until set), and the client may pick another of the team — not the agent.
The client's tour is about comments only — pin one, read the replies, confirm the fix — and the page tours with the team's keys and numbers are the team's.
Recording and writing out are two steps. Done leaves the voice note in the box as it is; the captions button beside it writes it out into the box when you want the words — for the agent, or to edit before sending. A voice note may also go without words.
Voice in the bar. The mic in a card on the site records a comment or a reply the same way — the recording bar, the words written into the box, the voice note sent with them. It replaces the screen recording in the card for now. The words come from the cabinet: the site linked to a project, or, on a site kept on your computer, signed in with npx notemend login.
The bar no longer offers to suggest new wording for an element; threads that already have one still show it.
Voice notes. Speaking a reply turns the reply box into a recording bar — the time, your voice coming in as a waveform, discard and done. What you said is written out as before, and the recording now goes with it: a player in the thread with a waveform that fills as it plays, click to jump, and 1×, 1.5× or 2×; on the site the bar plays it too. The × beside it before sending keeps the words only. Agents get the words, never the sound.
Connecting ChatGPT or claude.ai, the consent page says where the access goes back to — chatgpt.com, claude.ai — and warns when it is an address Notemend does not know, since any app may call itself by any name.

0.1.99 Oct 2026

Threads for every agent

Fix now on a thread — in the cabinet and on a card in the bar — gives it to the agent and lets turbo take it next, even while paused. The bar's keys stay out of a page's open menus and dialogs, and comment mode no longer pins a click on one.
White label: a team sets its colour and logo (Team → Brand), and the bar on its clients' sites and its mail wear them.
Guest links: a client comments with just a name, no account. Their threads wait for the studio's Approve for agent before any agent — the CLI, turbo, MCP, CI — takes them.
A remote MCP server at app.notemend.com/mcp for ChatGPT, claude.ai and other apps with no terminal: they sign in as you through Notemend, and Settings → Account lists and disconnects them. MCP server.
A comment in the bar can suggest the new wording of the element it is on, or carry a screen recording of up to 30 seconds — two icons beside the screenshot one. Its type, who it is for and its priority are one row of pills.
Threads are stored one row each instead of one document per project: no size ceiling on a project, and a change writes only the threads it touches.
Speak a reply: the mic in a thread's reply box records, and the words are written out on the server — in every browser, Arc and Brave included. Up to a minute and a half; the recording is not kept.
Settings → Account ends one session at a time, not only all the others.
The tours were rewritten for people who build sites: five things on a first visit — connect the agent and turbo, the To check queue and its keys, ⌘K, where help lives — and a page tour only where a page holds something not obvious. Skip tour is a button on every card.

0.1.88 Oct 2026

Turbo

The sidebar no longer folds to a rail. In the bar, Resolved moved into the comments panel; turbo is a switch with the lightning in its knob.
Priority reads like Linear's — signal bars, an alert circle for urgent, Set priority when none. The AI agent is an inverted face with a spark; a card in the bar sets its type and who it is for in two labelled fields with their own menu; badges are set in mono capitals; outlined buttons no longer glare in the dark theme; the bar's cards give a message room under its author.
Turbo: /notemend:turbo in Claude Code keeps the session listening — a comment left for the agent is taken, fixed and resolved as it lands, and a round lightning beside the bar shows it and pauses or resumes it. Underneath, npx notemend watch waits for one and exits. Agents.
Thread properties in two rows — what it is, then what you can set — and the type is a menu too. A pin on something inside a fixed panel no longer says it is not on the page.
Checking fixes in the bar reads like a pager: ‹ 1 of 3 › to go back and forth (← and → too), and the answers — looks right, reopen, stop — are icons with tooltips. Check all in the comments panel is a tick and a count that no longer wraps.
Insights can show one project or all of them.
A thread's assignee and priority are picked from a menu of their own — faces, colours, a search, ↑ ↓ and Enter, 1–4 for priority — instead of the system list.
An open thread stands beside the list as a window of its own. The table lost the grey line under each title on wide screens, where the columns say the same; saved views are gone and CSV is an icon, and the states above the table explain themselves on hover.
Tours of the cabinet: on your first visit, the sidebar one piece at a time — the piece lit, the rest blurred — with Back, Next, Skip, the arrow keys and Esc; after it, each page's own short tour the first time you open that page. The ? at the foot of the sidebar plays the product tour or the page's again.
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.78 Oct 2026

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.68 Oct 2026

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.57 Oct 2026

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.47 Oct 2026

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.37 Oct 2026

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.27 Oct 2026

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.16 Oct 2026

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.