Quiver

Changelog

What shipped in Quiver, newest first. Every entry is drafted from merged pull requests, reviewed by a human and published from the Quiver workspace itself.

Subscribe via RSS

September 2026

Tessa Kriesel

Set up a workspace in one screen

Paste your product URL and Quiver drafts your whole marketing context — positioning, ICP, messaging, competitors, customer language and proof points — then drops you straight into the workspace. The six-step wizard is gone.

  • Anything drafted without direct evidence from your site is flagged as an assumption, so you know what to confirm instead of trusting a wall of text you did not write.
  • Your dashboard shows how many fields are still assumptions. They clear themselves as you edit a field or approve a change, so the number only moves when something real happens.
  • No website yet? Describe the product in a few sentences and you get the same result.
  • Setup now ends by handing you an API key and your workspace's endpoint, so you can connect your agent before you do anything else.
onboarding
context
Tessa Kriesel

Connect agents that run in your browser

Agent clients that run in a browser can now connect to a workspace by signing in, with no key to paste.

  • Each workspace is its own connection, so a team with several workspaces keeps them separate.
  • Every connection is listed in settings with who made it, and you can revoke any of them immediately.
  • Members and admins can connect. Viewers cannot.
  • Local clients keep working exactly as before with a workspace key.
agents
mcp
Tessa Kriesel

Sessions propose updates to your context

When a session turns up something that changes what your company believes — a competitor you actually compete with, sharper language for your ICP, a customer phrase worth keeping — it proposes the change instead of quietly rewriting anything.

  • Each proposal shows the current value, the proposed value and why. Accept or dismiss it in one click.
  • Accepting creates a new context version, so nothing is lost and you can always see what changed.
  • Early sessions in a new workspace open with one short question about an assumption rather than guessing at it.
  • Next steps from a session can become tasks with owners, due dates and links back to the work that created them.
context
sessions
Tessa Kriesel

Content records where it went live

Tell Quiver your public site once and publishing records the live URL for you.

  • Set a site address and a path pattern in settings; every piece you publish stores its own address from then on.
  • That address is what future performance data attaches to, so numbers land on the right piece without anyone mapping them by hand.
  • Publish dates and campaigns can now be set from your agent, so an imported archive keeps its original dates and lands in the right campaign.
  • Distributions to other platforms now require the URL, because a distribution without one is just a note.
content
publishing
Tessa Kriesel

Public docs, a blog and this changelog

The documentation is public at quivergtm.dev/docs, rewritten around how the system actually works rather than a feature tour.

  • The blog and this changelog both run on our own Quiver workspace, served through the same public Content API your site would use. If it breaks for us, it breaks for you, and we would rather find out first.
  • Both have their own feed.
docs
website