Skip to main content

Changelog

The kamu.build docs started on 16.11.2026. The list goes back to v1.102.0; earlier changes to the platform are not listed here.

v1.115.0 (16.11.2026)​

Changes​

  • Sending a document for signature no longer locks it. You can keep editing right after sending, without making an editable copy. Signers see the PDF as it was when sent; edits do not change it.
  • A signature request goes to every signature slot of the document at once. Each slot needs a name and an email address before sending.
  • In the Documents list, each signing round is its own row under the document, with its status (waiting, signed, cancelled, declined). The row opens the PDF and the signers: send a link again, replace a signer or cancel the round. Read more: Documents
  • A document can have one waiting signing round at a time.

Fixes​

  • A document is no longer marked signed when the request went to only some of its signature slots and they signed.

v1.114.3 (14.11.2026)​

Fixes​

  • The Publish button in Studio's toolbar stays visible in a narrower window. When space runs out, secondary buttons show only their icon, and their name appears on hover.
  • Pressing Publish again on a version that is already published no longer ends in an error.

v1.114.2 (14.11.2026)​

Fixes​

  • A domain connected to a site no longer stays Awaiting verification once its DNS records point correctly. Read more: Connecting to a site

v1.114.1 (14.11.2026)​

Fixes​

  • When a domain's DNS records are changed to point at the site, its status no longer keeps showing the old records for about an hour. Check status also sees the change right away. Read more: Connecting to a site

v1.114.0 (13.11.2026)​

New​

  • You can connect your own AI agent without an existing account: choose Create account on the sign-in page and give your team a name. Read more: Connecting an app
  • An agent connected to the whole team at the edit level can create a new trial site and build its content itself. Read more: Creating a new site
  • An agent can draft an order for a site's plan and domain, which you confirm and pay yourself, and link a team domain to a published site. Read more: Ordering a plan and a domain
  • If a site's build fails after a publish, the site's people get a notification. It can be muted like other notifications.
  • Publishes from Studio and from agents show in the team's activity and the site's deployment history.

Changes​

  • When an order has a plan and one domain, the domain is linked to the site automatically after payment and registration.
  • A document's letterhead title can be set separately from the document's name.
  • Contact notifications also show checkbox, number and list answers.

v1.113.0 (12.11.2026)​

New​

  • An AI agent connected to a whole team can be given extra permissions: reading contact requests, reading invoices and billing details, and starting a domain purchase. The agent pays nothing: it makes a draft order that you confirm and pay yourself. Read more: Your own AI agent (MCP)
  • Under Connected apps in your profile, each agent's recent actions are listed, and a site's History page shows the changes agents have made. Besides changes, reading contact requests, invoices and document contents is recorded.

Changes​

  • Connected apps are shown as cards instead of a table on phones.

Fixes​

  • A document's password now applies also when it is set before the first publish. Before, the link opened without the password.

v1.112.0 (12.11.2026)​

New​

  • You can connect your own AI agent to a whole team: it then reaches all the team's sites, including ones added later, and its documents. Alternatively you can grant access to chosen sites only. Read more: Your own AI agent (MCP)
  • The agent can set a password on a document's public link when publishing, or remove it.

Changes​

  • The connection page is reworked. You choose one permission level (read, edit, or edit and publish), and above the buttons it shows what you are about to grant.

v1.111.0 (12.11.2026)​

New​

  • Your own AI agent can also create and edit your team's documents, for example write a new contract or offer. At login you choose the teams and permissions for documents separately. Read more: Documents with your own app
  • Your own AI agent (MCP) has its own section in the docs, with instructions for connecting Claude, ChatGPT and Claude Code.

Fixes​

  • Connecting Claude Code works. The login used to stop at the last step.
  • If the AI agent does not ask for permissions itself, the login page offers all of them to choose from.

v1.110.0 (11 Nov 2026)​

New​

  • You can edit your site with your own AI agent, for example Claude or ChatGPT. The agent connects to mcp.kamu.build, and at login you choose whether it may read, edit or also publish. This also suits an agency you have invited to the site. Read more: Your own AI agent (MCP)
  • In WhatsApp your message is marked as read and you see the typing indicator as soon as Kamu starts working on it.
  • The editor on the Posts page shows the cover image under the image field.

Changes​

  • If the site's file has changed since you started editing a post, the editor says so above the text. You can view the differences and choose whether to use the site's version or keep your own draft.
  • Several messages sent in a row are handled in the order they were sent, both in WhatsApp and in the dashboard chats.

Fixes​

  • The dashboard chat continues when the page is reloaded in the middle of an answer. The answer no longer goes missing.
  • Changes made to a site proposal (description, style, colours, logo) are saved and show when the proposal link is opened on another device.

v1.109.0 (11 Nov 2026)​

New​

  • A blog post can be written and updated in WhatsApp. Kamu saves the text as a draft, and it is published with the publish button in the message. Read more: WhatsApp
  • Kamu can read a web page whose link you send in the conversation and use it, for example, as a source for a blog post.

Changes​

  • When you give Kamu your own text for a blog post, it is saved as a draft straight away, without questions in between.

Fixes​

  • On phones and tablets the keyboard's Enter adds a new line in the chat field instead of sending the message. The message is sent with the send button.

v1.108.2 (10 Nov 2026)​

New​

  • A site draft can be discarded and started over from the published version. The discarded draft is kept and can be restored. Read more: Studio
  • Versions are named automatically from the first request, and the name can be changed from the version menu.

Fixes​

  • Studio's preview now shows sites built with the older Tailwind version correctly, with their styles.
  • In split view the phone is shown at phone height and the desktop view at full height.

v1.108.1 (10 Nov 2026)​

New​

  • The status of signature requests is available at any time from the editor's Signatures button. There you can send a link again, cancel a request, add a signer in place of a cancelled one and download the signed PDF. Read more: Signature requests

Fixes​

  • The document list shows Signed only once everyone has signed. Before that it shows how many have signed so far.

v1.108.0 (10 Nov 2026)​

New​

  • Studio has been redesigned. You edit the site by chatting with Kamu, and the preview updates as changes are made. Text can be edited directly in the preview, and the Pick what to edit tool lets you point at the part you want changed. Save stores your changes in a draft, and Publish puts them on the site.
  • If the previous editor had unpublished changes, they appear in the new Studio as an unpublished draft.
  • On the Documents page you can create documents, presentations and pages with Kamu, organise them into folders and choose whether the whole team can see them. Read more: Documents
  • A brand book can be created from an existing website: the logo, colours and fonts are taken from the site.
  • A document can be sent for signature. The signer gets a link, sees the document as a PDF and confirms the signature with a code sent by email. The finished PDF with its certificate is sent to every party.

Fixes​

  • Refreshing the Domain page now also reloads the status of operations and the registry.

v1.107.0 (7 Nov 2026)​

New​

  • When rebuilding a site you can pick a style for it, such as Quiet, Bento or Nordic. By default the builder picks a style that fits the business.

v1.106.0 (6 Nov 2026)​

New​

  • Contact form submissions are checked for spam. Suspicious messages go to the Spam section of the Contacts page, from where a genuine message can be delivered. Read more: Notifications

v1.103.0 (5 Nov 2026)​

New​

  • The shop notifies you by email and in the notification bell when Stripe starts accepting card payments for the shop. The notification can be switched off in the shop's notification settings.

v1.102.0 (5 Nov 2026)​

New​

  • Shop shipping methods can have weight tiers, so the shipping fee follows the order's weight, and a delivery time shown to the customer at checkout. See Shop.

Changes​

  • The Stripe setup for card payments opens in a new tab, and the dashboard updates its status when you return.