Clarabit Clarabit
← All releases
Feature v2026.05.17 · May 18, 2026

Release v2026.05.17

Release v2026.05.17

✨ What's new in Clarabit

Share pages with anyone — they don't need a Clarabit account. Mint a public link from any page and send it to a teammate, customer, or stakeholder. They review the page and leave comments; their feedback shows up in your normal page-comment view with an "External" badge. They verify their email once via a magic-link; after that, follow-up comments post instantly. Revoke any link from the page header whenever you're done.

In-product release notes. This page. Click "🎉 What's new" in the top nav (or the green dot when there's something new) and a drawer slides in with the latest updates. Also public at clarabit.ai/changelog.

🤖 What's new for your AI helper

If you use Clarabit through an AI helper like Claude Cowork, Claude Code, or Codex, today's update teaches it three new things.

Leave a comment on a specific phrase in a page. Ask your AI to "leave a comment on the third bullet under Risks" and it'll land exactly there. If the phrase shows up in more than one spot, your AI will surface the candidates and ask which one you meant — no more silently anchoring to the wrong place.

Read the existing discussion on a page. Ask "what's still open on this spec?" or "summarize the comments on the launch plan" and your AI can pull up the unresolved feedback (or all of it) without you copy-pasting.

Save shared context for the team. When you tell your AI about a project convention or constraint — "we deploy on Tuesdays, never Fridays" — it can now save that into Clarabit so the next person, or your next AI session, picks it up automatically.

🔄 Heads-up: these AI features only show up after your AI helper picks up the latest version of the Clarabit MCP connector. Most tools refresh automatically when you restart them; a few need a manual "Update tools" nudge in their settings. Technical users, the exact commands are in For agents and integrators below.

🐛 Fixed

  • Pages with comments from removed teammates no longer crash.
  • Agent comments stay clean — internal AI-tool tags (the "<system-reminder>…" kind) get stripped automatically before the comment is saved.
  • Adding a link to a task works with either shape the API accepts — the older "flat" payload no longer 500s.

For agents and integrators

The rest of this changelog is for folks driving Clarabit through MCP, an API integration, or building on top of the platform. If that's not you, you can stop reading here.

⚠️ Update your Clarabit MCP to @limeadelabs/clarabit-mcp@2.3.0

The AI-helper features above (anchored comments, list discussion, save context) are MCP tools. They won't appear in your tool list until you upgrade — existing tools keep working on older versions, the new ones simply aren't registered there.

Requires @limeadelabs/clarabit-mcp@2.3.0:

  • cla_context_create — write new context entries (added in 2.1.0)
  • cla_list_page_comments — list comments on a page (2.2.0)
  • cla_update_page verbose flag — opt back into the full body in the response (2.2.0)
  • cla_prepare_page_comment_anchor — validated anchored-comment offsets (2.3.0)

Upgrade:

# Global install
npm install -g @limeadelabs/clarabit-mcp@latest

# Local install (in a project that pins the dep)
npm install @limeadelabs/clarabit-mcp@latest

Then restart your MCP client (Claude Code, Codex, etc.) so the new tool list is picked up at session start.

New MCP tools and API endpoints

cla_prepare_page_comment_anchor — validates and computes offsets for an anchored page comment without you manually counting characters. Pass one locator: exact_text (unique substring), prefix + text + suffix (disambiguate repeated text), or heading + text (scope to a markdown section). Returns offsets + the body revision the anchor was computed against, ready to drop into cla_create_page_comment. Repeats no longer get silently anchored to the first match — the tool returns a structured ambiguous_anchor error with all candidate positions and their preview context.

cla_list_page_comments — list comments on a page (optionally filtered by resolved state) without first walking projects to find it. Backed by a new flat GET /api/v1/pages/:id/comments route. Pages also now include a comments_count so you can see at a glance whether there's anything worth fetching.

cla_context_create — complements the existing read tools so agents can write new context entries directly, not just edit ones the team already authored.

GET /api/v1/tasks/:id — rounds out the CRUD on the HTTP side; cla_get_task in MCP worked already, this is just for symmetry.

Behavior changes

  • PATCH /api/v1/pages/:id returns a minimal payload by default — id, title, version number, change summary. Pass verbose: true if you actually want the new body back. Cuts the round-trip in half on synthesis-style pages. cla_update_page accepts the same flag.
  • Page JSON now includes version_number — the revision the current body lives at. Anchor helpers stamp this onto comments so drift is detectable later. Note the semantic: the latest snapshot's version_number stores the body that was current before the most recent edit; the current body is logically one revision past that.
  • Page comment author payload is nil-safe — external (share-link) authors are surfaced as { id: null, name, email, external: true } instead of the older { id, name } shape that assumed a logged-in user.
  • Task-link API accepts both shapes — { url, title } and { link: { url, title } } (the flat shape used to 500).