Changelog

What shipped in Clawnify each week, from agents and apps to the API.

Updated weekly · Latest October 26, 2026

Week 19

Clawnify Websites launches with custom domains, alongside a PDF service for apps and new ClawFlow steps.

Clawnify Websites

Every organization can now have a public Astro website that its agent builds and edits from plain instructions, hosted at a myclawnify.com address.

Custom domains for websites

You can now connect your own domain to the website, and connecting the root domain sets up the www version too.

Preview first, then publish to live

Once a website has a custom domain, agent edits land in a live preview that updates as the agent works, and visitors see them only after someone clicks Publish to live.

PDF rendering for apps

Apps can now turn HTML into a PDF through a Clawnify-managed service, using the @clawnify/pdf package and the organization's Clawnify token.

App and integration steps in ClawFlow

ClawFlow workflows can now call your Clawnify apps and run integration actions as built-in steps, instead of hand-written code with its own authentication.

Learn more

Improvements

  • Website builds show a live status line under the badge, such as "Editing Hero.astro", while the agent works.
  • Website edits now build on the site's existing source files, so earlier changes carry over to the next edit.
  • Websites are styled with Tailwind v4 and a DESIGN.md design brief, and pages are composed from flexible layout blocks instead of fixed section types.
  • Website previews show in the dashboard next to the build status.
  • A custom domain goes live as soon as one of its hostnames validates, and setup lists every certificate TXT record to add.
  • A refresh button next to a custom domain rechecks its status on demand.
  • Environment variables are now set for the whole organization and apply to every agent.
  • The Website link moved into the Account section of the sidebar.

Models

  • Requests now retry on their own when a model provider has a temporary error.
  • Model errors in chat now include the provider's explanation instead of only a status code.

For developers

  • clawnify link connects a local folder to an existing app, and clawnify deploy then redeploys that app.
  • clawnify deploy asks whether to update the existing app or create a new one when the app name is already taken in your organization.
  • clawnify init scaffolds apps with React, Tailwind v4, OpenAPIHono and zod-openapi.
  • New @clawnify/pdf package renders HTML to PDF from an app, with self-hosted fallbacks.
  • Each organization now has one Clawnify token for every Clawnify service, available to deployed apps as CLAWNIFY_TOKEN.
  • update_website now takes a single plain-language instruction, on the MCP tool and on the CLI.
  • New publish_website tool and clawnify publish-website command promote a website preview to live.
  • New upload_asset tool returns a permanent public URL for an uploaded image or file.

Fixes

  • Fixed the first message flickering when sent from a new chat.
  • Fixed saving a custom environment variable failing with "Failed to save metadata".
  • Fixed provider keys saved in Settings not reaching newly created agents and newly built apps.
  • Fixed website deploys failing.
  • Fixed connecting a custom domain failing.
  • Fixed reconnecting a domain that had already been added returning an error.
  • Fixed custom domains showing as failed while DNS was still propagating.
  • Fixed custom domain status not updating after the domain was verified.
  • Fixed websites on custom domains not loading.
  • Fixed the app list returned by clawnify ls.

Week 18

Easier setup for extra agents and triggers, saved skills one click away, and a link for every chat.

New agent form

You can now add an agent from a + New agent form by giving it a name, a description and a level, and it starts working alongside the main agent.

Saved skills under the chat box

Tasks your agent has saved as reusable skills now show as cards below the composer on every new chat, so you can run one with a click and the chat shows a Running skill chip.

Instructions for each trigger

You can now tell the agent what to do for each trigger in a What should the agent do? field, and choose whether the trigger connects to the agent right away.

Describe the event, get the trigger

The trigger picker now starts with a text box, so you describe what to react to in your own words and it finds the matching trigger and fills in its settings.

A link for every chat

Every chat, including a new one, now has its own address, so you can bookmark it, refresh it or open it in a new tab without losing your place.

Improvements

  • Your first message in a new chat now goes straight to the agent instead of being preceded by a greeting.
  • The + New chat button and chat history items are now real links, so they open in a new tab with a modifier click.
  • The trigger dialog is wider and lists available triggers in three columns.
  • Inbound emails now arrive with your custom email instructions in the same message, and the agent replies by email rather than in chat.
  • Apps can now use integrations that connect with an API key or a username and password, not only ones that sign in with an account.
  • Agents now run workflows on ClawFlow 1.0.
  • The Clawnify website now offers a free AI Apocalypse Score that rates how exposed a business's website is to AI, across five categories.

Integrations

  • WhatsApp: agents can now create groups, add people to them and share a group invite link.
  • WhatsApp: new links now only accept direct messages from allowed numbers by default.

For developers

  • clawnify deploy now redeploys the linked app, and when a name is already taken it asks whether to update that app or create a new one.
  • clawnify init now scaffolds a React and Tailwind v4 app.
  • Scaffolded projects now pin clawnify as a dev dependency and require Node.js 22 or newer.
  • clawnify dev and clawnify deploy now stop with a clear message on Node.js versions older than 22.
  • Apps that declare API key or username and password integrations receive them as secrets at build time.
  • The API now publishes OAuth protected resource metadata at /.well-known/oauth-protected-resource, so agents can discover how to sign in.
  • The dashboard now exposes listing, reading and creating apps and listing agents as WebMCP tools for browser agents using your session.

Fixes

  • Fixed approving or declining an action in chat stopping the agent mid-task.
  • Fixed linking WhatsApp failing with a "web login provider is not available" error.
  • Fixed enabling Slack and Telegram failing on older agents for the same reason.
  • Fixed the self-chat setting being ignored when first linking WhatsApp.
  • Fixed clawnify dev failing to find the app's backend code in new projects.

Week 17

Agents can now react to events in connected tools, take actions in them, and ask for approval in chat first.

Triggers from connected integrations

You can now turn on triggers from a connected integration's card on the Integrations page, like a new Slack message or a Google Sheets change, and the event goes straight to the agent with no workflow to set up.

Set up a trigger in your own words

Instead of a settings form, the trigger dialog asks one plain question, like which sheet and range to watch, and turns your answer into the trigger's settings, with the full form still under Configure manually.

Agents act in your connected tools

Agents can now run actions in connected integrations, like reading a spreadsheet or posting a message, and the chat shows the integration's icon on each action call.

Approvals in chat

When an action needs sign-off, the agent now asks in the chat you are using and waits, and you can allow it once, allow it always or deny it.

More than one agent in a workspace

Your agent can now create additional agents, each with its own chat, and they show as cards on the main agent's home screen.

Improvements

  • Inbound emails and trigger events now reach the agent's main conversation, with the full content saved to a file the agent opens when it needs it.
  • Workflow triggers can now send events to the agent directly, to a ClawFlow workflow, or to both.
  • The chat composer now sits centered on a new chat and moves to the bottom once you send the first message.
  • An approval request now waits up to nine minutes for an answer before the action is dropped.
  • The Clawnify website now offers a free email signature generator.

For developers

  • Agents on Clawnify can run any integration action with clawnify action <SLUG> and look up valid action names with clawnify list-actions --toolkit <slug>.
  • When an integration action fails, the CLI now shows the integration's own error so the agent can correct the request.
  • New MCP tools create_agent and list_agents let an agent create and list the other agents on its machine.
  • The API now has /v1/policy/check to decide whether an action is allowed, denied or needs approval.

Fixes

  • Fixed creating a trigger from the Integrations page failing.
  • Fixed integration actions failing to run when called by name.
  • Fixed filtering available actions by integration.
  • Fixed trigger events from connected integrations being rejected as unsigned.

Week 16

Two-way GitHub sync for apps, integrations shared across the organization, a billing page and model tiers matched to plans.

Two-way GitHub sync for apps

You can now link any app to a new or existing GitHub repository from the GitHub icon in the app header, so a push redeploys the app and every Clawnify build commits its source back to the repository.

Integrations shared across the organization

You can now connect an integration once from Settings → Integrations and every agent in the organization can use it, while a single agent can still be given its own account that takes precedence.

Billing in settings

A new Settings → Billing page shows your current plan and credit balance and lets you upgrade, downgrade or choose a plan, and it sits next to API Keys in the account menu.

Connected integrations inside apps

Apps can now use the organization's connected integrations, like Google Workspace, by declaring them in clawnify.json, and they get fresh tokens without storing any secrets.

Learn more

Choose which WhatsApp groups your agent joins

You can now add WhatsApp groups one at a time and choose per group whether the agent replies to every message or only when mentioned, instead of an allowlist that silently turned groups off.

clawnify dev

Developers can now run an app locally with one clawnify dev command, which sets up the local database and dev environment from clawnify.json.

Learn more

Improvements

  • Custom environment variables now have their own Settings → Environment Variables page, separate from API Keys.
  • The New chat button now starts the agent's greeting, so it reads its persona and memory before you type.
  • Chats no longer jump to the bottom on every new agent message.
  • Only organization owners can now start a checkout for a plan.
  • Canceling checkout now returns you to onboarding with a notice instead of a blank screen.
  • The extra Start free trial button at the bottom of the onboarding plan step is gone, since each plan card has its own.
  • The app builder now picks a template from clearer descriptions, asks when a request is ambiguous, and builds from scratch instead of forcing a weak match.
  • New custom apps now start from the same scaffold as clawnify init, so the builder customizes a known base instead of generating everything.
  • Apps imported from a repository keep their own build script.
  • GitHub sync leaves build output out of the repository.

Models

  • Automatic model routing is now off by default.

For developers

  • clawnify init now takes --name, --template and --storage flags for non-interactive use.
  • clawnify init now writes a fuller .gitignore.
  • Apps declare the environment keys and storage they need in clawnify.json.
  • Apps declare the integrations they use under app.credentials in clawnify.json, documented in the app template reference.
  • The docs now cover the identity headers apps receive and the Clawnify model tiers and routing.

Fixes

  • Fixed accounts without a subscription being sent away from the dashboard.
  • Fixed checkout errors failing silently, so they now show a message and can be retried.
  • Fixed an agent being created before checkout had completed.
  • Fixed the credit amount resetting to the default when starting a trial.
  • Fixed agents' instructions growing longer with every turn of a chat.
  • Fixed the GitHub connect popover redirecting again when the GitHub app was already installed.
  • Fixed the WhatsApp channel failing to start when saved with an empty allowlist.

Week 15

A rebuilt app builder, credit-based pricing, the first Clawnify CLI and a public docs site.

A more capable app builder

The app builder can now take on larger, multi-file apps instead of generating them in a single pass.

Plans with a credit balance

Every plan now comes with a monthly credit balance you pick from a dropdown, with the price updating as you choose.

Learn more

Clawnify CLI

Developers can now scaffold, run and deploy apps from the terminal with npx clawnify, and use the same commands from Claude Code through its built-in MCP mode.

Learn more

Public docs site

A new documentation site at docs.clawnify.com covers the CLI and the full API reference, and a Copy page menu sends any page to ChatGPT or Claude.

Learn more

Apps know who is signed in

Apps opened from the dashboard now receive the signed-in user and their organization, so they can personalize content and control access without a separate login.

Learn more

Improvements

  • Onboarding is now four steps (Setup, Role, Plan, Review) instead of six, with channels and API keys set up after sign-up.
  • The pricing page was rebuilt to match the onboarding plan cards, with a monthly and yearly toggle.
  • Yearly plans now show "billed yearly" instead of a calculated annual total.
  • Pricing page sign-up buttons now open the sign-up page in a new tab.
  • Credit packs are now offered in three sizes.
  • Onboarding no longer includes a meeting step.
  • When your agent needs approval to run a command, it now pauses and waits instead of queuing follow-up messages.
  • People who open Clawnify inside the LinkedIn, Facebook or Instagram browser can now sign up with email.
  • One connected event source can now start workflows on several agents in the same organization.
  • App builds now upload and unpack files in parallel, so they finish sooner.

Models

  • Clawnify Pro is now the name of the standard model, alongside Clawnify Lite and Clawnify Max.
  • Clawnify models now catch common slips, like stopping early or running a destructive command without confirming, and correct themselves mid-reply.
  • Each Clawnify tier now adapts to the task, giving harder work more capability.

For developers

  • clawnify init scaffolds a new app from a blank or CRUD template, ready to run locally with Vite and a local database.
  • clawnify login signs in through a browser consent page and asks which organization to use.
  • clawnify deploy, ls, logs, open, rm and whoami manage apps from the terminal.
  • clawnify --mcp exposes deploy, list, get and delete as MCP tools for Claude Code.
  • The API now ships an OpenAPI spec with an interactive reference at docs.clawnify.com.
  • The docs site now has a site-wide /llms.txt index and a View llms.txt option on every page.
  • The docs now include an app template reference covering the file structure, the database pattern and a migration guide.
  • Apps receive X-Clawnify-User-Id, X-Clawnify-Org-Id, X-Clawnify-User-Email and X-Clawnify-Caller headers, and any copies sent by the browser are stripped.

Fixes

  • Fixed the send button being blocked while a chat still looked busy after the agent had finished.
  • Fixed agents repeating the same paragraph within a single reply.
  • Fixed buying credits failing for organizations created before credits existed.
  • Fixed the app link missing after deploying an app from the CLI.
  • Fixed the pricing page scrolling sideways.

Try what's new.

Start a three-day free trial with $5 in credits and your own agent.

Start free