Resources

Changelog

What changed in each version of the Awesomate MCP, in the words Claude shows you when it offers an update.

Newest first. Claude Code picks up a new version of the server by itself when it restarts, and offers to update the skills when they fall behind (see How it works).

[0.93.0]

Claude can put a published agent on your website: it makes a website key for the sites you name, after your yes, and hands you the code to paste. Each website key has its own monthly answer limit, half your account's by default, and Claude tells you the number
Uploading a file as public now needs the same typed confirmation as adding a public page
A delete that finds nothing says the item may already be gone or the id may be wrong, and a delete that timed out says it may have gone through instead of saying nothing changed
Asking within filters works with the workspace's default agent, and a new agent drafted from a goal keeps the name you gave it
Skill update checks compare version numbers properly (0.10 is newer than 0.9)
When a Knowledge agent fails because the account's own OpenRouter key is refused or out of credit, Claude says so and where to fix it, instead of a generic service problem

[0.92.2]

Publishing a staging copy keeps the live site's search engine setting, instead of hiding the live site from Google like the staging copy, and says so if it could not

[0.92.1]

Turning on Knowledge again now puts back a missing n8n credential for it, and says why when it cannot (for example, n8n is not connected yet)

[0.92.0]

Claude says whose key it is: the account owner's, or a team member's own, which does only what that person can do
Connecting on a computer already connected to the same account as someone else stops and asks, instead of replacing their key

[0.91.1]

When Automations or your Website is switched off for the account, Claude says so and stops instead of trying the tools for it

[0.91.0]

Claude can now look after your Knowledge agents more fully: see how each one is answering and its call log, see which agent each website uses, delete one you no longer need (after your yes), and set up customer groups that limit what each group's answers draw on
FAQs can be read straight from a web page, pasted text or a file on your computer, and you see every question and answer before anything is saved
Claude can open, rename and settle the columns of a dataset, and approve, answer or undo a data import, each only after you say yes
Adding a domain can point it at one of your WordPress sites in the same step, and a new site can be made ready to receive a site you're moving here, or built with a theme you name
Claude can suggest the questions for your AI visibility check, unzip a file in Files, and suggest business details from a document you keep there (you save the ones you want in the hub)
1Brain: see every role's systems at once, take one off a role, and look after onboarding plans (check progress now, match someone to their 1Brain login, close or move a plan)
Bookings take how often start times fall, the order services show in, and a move to another calendar, and Claude can unlink a connected Google or Microsoft calendar with your yes
At the start of a session Claude says your Claude Code key is the account owner's, and when a request needs a permission your key doesn't have, it tells you straight away instead of trying and being turned away

[0.90.1]

Claude now offers a support ticket first when you ask for someone to help, and books a paid session only when you ask for one
Clearer picks measured by the tool-selection eval: 'what bookings have I got' opens the diary, the support inbox and import status are easier to find, and a key for your automations is never stored in an app

[0.90.0]

New awesomate_crm_layout tool: Claude reads and saves what each kind of record means (its description, sections, and each field and link), in the owner's words, for the fields AI may read. People see the sections on each record, and AI reads the words to understand the business

[0.88.6]

An app whose setup failed no longer uses one of your app slots or blocks its name: create it again with the same name to retry, or ask Claude to remove it with the new awesomate_app_remove_failed tool

[0.88.5]

Adding a domain now gives your server's public address, never an internal one, and says the records must be Proxied (orange cloud) in Cloudflare with SSL/TLS set to Full

[0.88.4]

The site audit now reads your page the way ChatGPT search does, so a page that turns AI bots away is reported as unreachable instead of being scored on the block message, and the sitemap check no longer reports a sitemap missing when it is there
SEO checks test the AI search bots that decide whether you get cited. AI training bots are blocked on purpose on Awesomate-managed addresses, so Claude no longer reports that as a fault

[0.88.3]

When the hub cannot bring your n8n credential list up to date, Claude now says the list may be out of date, as of when, and which credentials n8n has added or removed since

[0.88.2]

Fixed: the booking diary tool described its opening hours in an older JSON Schema form that strict clients refuse, which would stop every Awesomate tool loading there. Nothing changes in Claude Code

[0.88.1]

Bookings can keep a calendar's busy times free from Outlook as well as Google Calendar, and write each booking into it; the owner connects it in the hub

[0.88.0]

Claude no longer builds workflows through Awesomate: it writes them straight on your own n8n through n8n's MCP server (switch on MCP access in your n8n and add its key to Claude Code), with no Awesomate limits on it. Reading your n8n, installing templates and n8n Agents work as before

[0.87.0]

Claude can read your brand guide, voice guide and business summary, and the business details waiting for your yes, so long pieces sound like you. Accepting a suggestion stays your click in the hub
Claude can read your site figures (awesomate_site_insights): visits, leads, visits from AI apps and Google search clicks over the last 28 days, where leads came from, searches almost on Google's first page, and what is worth fixing
Claude can read one of your tickets to Awesomate and its replies, and answer it for you once you have seen the exact message and said yes
More on Tasks: change a task, drop one, bring back one you closed, see a task's history, and put a card off until later. Decisions are still yours to make in the hub
Claude can tell Contacts that something happened to a person (a job paid, a quote sent), which starts any email series you switched on for it. It asks you first, and it never signs anyone up for email
Claude can follow a Vimeo or Wistia library import (how far it has got, which videos failed). Connecting the library and starting the import stay in the hub
Bookings: read one booking, and mark it completed or a no-show. Files: see what is in the trash, and empty it after your yes

[0.86.1]

Claude knows the difference between help from Awesomate and your own customers' support inbox, and reads the inbox instead of raising a ticket with us
The docs now have a guide line for every tool, including a new page on your business details, business map, Tasks and monthly reports

[0.86.0]

Claude can read how often ChatGPT and Gemini name your business for your site (awesomate_ai_visibility): the score, the questions where neither app names you, who they name instead and the sites they rely on, so it knows what to fix first. Approving the questions stays your own click in the hub.

[0.85.0]

When the Knowledge Base answers from general knowledge instead of your content, Claude no longer passes that answer off as your "no answer" message: it tells you your content does not cover the question

[0.84.0]

A website chat only ever runs a Public agent: Claude checks the agent is Public before connecting a chat to your site, and a chat with no agent set now says it is not set up yet instead of answering

[0.83.0]

Adding a web page or a whole website as public now asks first: Claude checks with you, then confirms with your account name, because anything public can be seen by your customers and public chatbots

[0.82.0]

Claude can read your customers' support inbox (awesomate_support_desk): whether it is on, your tickets, and one ticket's messages, your team's notes and any reply the AI is holding for your OK. It reads only: replying stays a person's click in the hub, under Contacts, Support

[0.81.0]

Claude can list the decisions waiting in your business (awesomate_tasks 'decisions'): what your agents and automations are holding for a person's OK, who decides each and by when. It can never approve one: that stays a person's tap in the hub
Your business map holds what each role approves alone (an amount and a discount); Claude reads the limits and can suggest them, and lowering one applies straight away
Claude can build an automation that waits for a person's OK before it acts: Hold for a decision, then a Wait that only the hub can resume

[0.80.0]

Spreadsheets in your Files folders go into Knowledge too: Claude adds one as knowledge or as data, and a synced folder adds its spreadsheets the way you choose (until you choose, they are skipped and the sync says why)
After publishing your FAQs, Claude tells you which of your agents won't answer from them yet (an agent limited to another collection, or to other kinds of content) and how to fix it. An FAQ set can be put in a collection as it is created
Claude limits a new agent to the right collection when it creates it, and warns you when an agent it drafted would read every collection, or would skip your PDFs, FAQs or images

[0.79.0]

Spreadsheets upload again: Claude says whether a spreadsheet goes in as knowledge (each row a record people can ask about, like a price list or timetable) or as data (totals and trends, like invoice history), and asks you when it isn't obvious
Renaming a source works: Claude can give an uploaded file a proper title, since uploads arrive titled from the file name with underscores
Claude sends you to the right switch for Knowledge: Settings, Features, then "Use your content for Knowledge" under Knowledge
Claude can ask your published agent a question the way a website visitor would, to check what the public actually sees, and pause or restart an agent with your yes

[0.78.0]

1Brain onboarding: Claude can build a 1Brain course for a role on your business map from that role's 1Brain systems, or a starter course for everyone joining, and start someone's onboarding, which gives them their courses as Tasks
Each morning the hub checks the quizzes passed and acknowledgements done in 1Brain, and when someone has finished a role's course it asks their future manager whether to hand the role over. Finishing a course never changes anyone's access by itself

[0.77.0]

Claude now reads and changes your business map in the same words you see: departments, sub-departments and roles. Its 1Brain actions are 'systems for role' and 'link role' (the old names still work)

[0.76.0]

Your business map uses plainer words, the same as 1Brain: its seven parts are departments, each with sub-departments, and the jobs people hold in them are roles. Claude talks about them the same way

[0.75.0]

Claude can look up your procedures in 1Brain for you (awesomate_onebrain): search them, read a page, and answer "what are the procedures for this hat?" with a link to every page it used, all through your own 1Brain login
Your business map shows 1Brain: pick the 1Brain category that is your business, place each 1Brain Department in a division, search 1Brain from the map, and keep a list of 1Brain systems for each hat, tagged in 1Brain as well
Claude can save a new procedure in 1Brain as a draft, written from your own words, for a person to review and publish there

[0.74.0]

Claude knows 1Brain: how each person connects their own 1Brain in the hub, when to use 1Brain's own Claude connector, the 1Brain node in your automations or an AI agent, and the rules it keeps (drafts first, your own words, links to every page it used). New guide: what the 1Brain node can do

[0.73.0]

Claude can suggest this quarter's priorities for each hat on your business map, and mark them on or off track, for you to accept from Tasks

[0.72.0]

Claude talks about your business map the way you do: the roles in each division are hats, and one person can wear several

[0.71.0]

Bookings can now be connected to your Google Calendar from the hub: times you are busy in Google are never offered to customers, and every booking goes into an Awesomate bookings calendar in your Google account, moved and removed with it

[0.70.1]

Portals Claude builds for you now load the current Awesomate SDK, so file uploads in your app work, and a page showing who is on a job in two places keeps both up to date

[0.70.0]

A file you make private, delete or replace in your Files now stops showing at its public address within seconds, instead of up to 4 hours

[0.69.0]

Bookings: your customers book appointments or classes on your own website, get an email with an invite and a link to change or cancel, and each booking lands in Contacts. Claude sets up your calendars, services and the booking box (awesomate_bookings), and can book, move and cancel for you

[0.68.0]

Claude can work with your Files: the folders your workflows use on your automation account. Put an image up and get its public address, fetch a report a workflow saved, make a file public or private, and tidy up, with storage counted against your plan's Files space
Apps you build can let signed-in people attach files, such as a photo of a job, when you switch uploads on for the app

[0.67.0]

Claude can read your Tasks and help with them: see what is waiting on you and your team, give someone a task, mark one done and pass a card to the right person. Quotes and approvals are still done on their own pages, by you

[0.66.0]

Your business map now shows how a customer moves through your business, step by step, and who looks after each step. Claude starts from the jobs that still need writing down, and knows where each job's procedures live in 1Brain

[0.65.0]

Claude can read your business map: the seven divisions, who holds each job, and which agents help where. Ask what to automate next and it starts from the biggest gap; any change it suggests waits for your yes in Tasks

[0.64.0]

No brand design system yet? Claude can make you a starter one from your confirmed business details (colours, font, logo, voice) and help you put it in Claude Design, so everything built for you looks like you from day one

[0.63.0]

Before building anything people will see, Claude asks about your brand design system: it uses yours in Claude Design, or offers to make one from your business details, so your apps, pages and emails all look like you. You can save its name and link on Your business

[0.62.0]

Claude points you to the new SDK docs at hub.awesomate.ai/docs/sdk when you build a portal or an app, and the portal skill now covers letting customers accept a quote, who's here and typing, and talking by voice

[0.61.1]

Knowledge agents follow your Knowledge access again: every account with Knowledge can list, edit and publish them, as before

[0.60.1]

When Awesomate can't check your plan for a moment, Claude says to try again shortly instead of suggesting an upgrade

[0.60.0]

Claude knows which features your account has: Contacts, emails, Knowledge, Agents and the rest. It never offers one you don't have, and says why in one line: not on your account yet, turned off by Awesomate, switched off in Settings, Features, or the plan that includes it

[0.59.0]

Claude can switch an automation Awesomate built for you off and on again when you ask, and says what it does first. Changing, deleting or rolling one back still goes through our support team

[0.58.0]

Customers can do one exact thing their access would not let them do by hand, such as accept their own quote: Claude saves it as a recipe and, on your say-so, opens it to a role (awesomate_crm_recipes action 'run_by'). Pro and above
Your app runs it with @awesomate/sdk app.call(). The database lets them change only what the recipe says, and only on records they can already see; archiving the recipe closes it again

[0.57.0]

Reply emails for your portal's conversations (awesomate_crm_notifications): when your team or Bree replies, the customer gets an email if they aren't in the portal, and when a customer writes, your team does. At most one an hour per conversation
Off until you switch them on, per app. They're system emails, like a ticket reply or a receipt, sent from your app's name with the message quoted and a link back

[0.56.0]

Knowledge: audio and video are Pro and above whether you upload them or link to them, and each month's media hours are the line where transcription stops
A one-off media-hours pack is for the month you buy it. For more every month, the owner can add 40 media hours a month for $100 on Knowledge, Usage
Claude no longer says a YouTube or other video link will be transcribed: for now a link is read as a web page, and the recording itself is transcribed when you upload the file

[0.55.0]

New email skill: Claude plans which lists to start with, writes emails in your voice with Australian and New Zealand spelling and seasons, and keeps every send on the right side of the Spam Act
With Contacts & email on your account, Claude writes each email as a draft to one of your lists and gives you the link. You check it, send yourself a test and approve it in the hub. Claude never sends
It won't email people to ask for permission (the law counts that as marketing), judges results by what people did rather than open rates, and helps you move a list off Mailchimp, ActiveCampaign or Ontraport with its consent records

[0.54.0]

Claude now knows your business: awesomate_business reads your name, services, voice, colours, website and contact details in one go, so site copy, emails and agent instructions use your words instead of invented ones
Attach it to any chat as the awesomate://business resource, or run the awesomate-business prompt for a summary of what's confirmed and what's missing
Every detail says where it came from. Anything found by researching your website is marked as a suggestion, and Claude asks before publishing it

[0.53.0]

Fields only your team sees: mark an attribute visible to staff only (awesomate_crm_kinds, set_visibility), such as the cost behind a quote or an internal note on a job. Customers signed in to your portal read it as empty and cannot change it
Your own database enforces it, not the portal's code, and Bree, answering as the customer, never sees it either. You and Claude always see every field

[0.52.0]

When your n8n is the one receiving, Claude can ask the hub to put a record hook's secret or an app server key straight into an n8n credential on your instance (n8n_credential). Nobody sees the secret, not Claude and not you
Removing the hook or revoking the key removes that credential too, so n8n never offers a dead one

[0.51.0]

Your app's staff can now find a customer and put a job under them, straight from the portal. Switch it on per app for the roles that need it (awesomate_crm_apps, customer_lookup). Pro and above
They see name, email and phone only, never a field you marked sensitive, and never the role your customers sign in with: customers still see only themselves

[0.50.0]

Your n8n can now hear about your app's records (awesomate_crm_hooks): when a job is requested, changed or archived, a workflow runs straight away, with the record attached
Events arrive in order and keep coming back while n8n is down, so a quiet weekend doesn't lose anything. Each has an id, so a workflow can ignore a repeat
Only your own n8n can receive them, protected by a secret your Webhook node checks. Pair it with an app server key to write the result back, such as a drafted quote
New skill, awesomate-portals: ask Claude for a customer portal and it designs the records, who sees what, sign-in by email link and the page, step by step

[0.49.0]

Your app's own server, or an n8n workflow, can now read and write your app data with a server key of its own (awesomate_crm_apps, create_key), instead of your account's token
Keep each key narrow: read only, or only the kinds it needs. Revoking one stops it at once, and switching an app off stops all its keys
Use a key with the @awesomate/sdk package (createClient with the key as the token) or as a Bearer token from n8n. It never works from a browser

[0.48.0]

Knowledge Base answers are now a hard limit: when a month's answers run out, your assistants stop answering until the 1st, and you are emailed at 80% and again at the limit
Past the limit: an answer pack adds 2,500 answers for the rest of the month (1 credit), or the monthly answers add-on adds 2,500 every month for $100 a month, stop anytime. Support Plus and above
A full library on Support Plus and up now points at the monthly storage add-on (1 TB for $100 a month) instead of a storage pack, and Claude relays it without ever buying it

[0.47.0]

Your app's conversations can have an AI in them (awesomate_crm_assistant). When a customer writes, it answers from their own records and your Knowledge Base, or drafts an answer for your team. Pro and above
Your team decides per conversation: off, draft (a suggested reply only staff see, sent by a person as themselves) or auto (it replies at once, marked as AI). New conversations start off unless you choose otherwise
It reads as the customer it is answering, so your access rules bound it, and it sees only the fields you marked readable by AI. When someone asks for a person, it hands the conversation over and flags it

[0.46.0]

Your own apps can now sign people in. Claude can set up an app (awesomate_crm_apps): where it runs, whether anyone can sign up or only people you add, and the key that goes in the app. Each person gets an email link, no passwords. Pro and above
You decide who sees what, per kind of record: members see their own jobs and the memos on them, staff see everything (awesomate_crm_kinds, set_access). The rules are kept in your own database, so a mistake in an app can't show anyone more
Add, re-role or switch off the people who sign in (awesomate_crm_app_users). Switching someone off takes effect on their very next click and signs them out everywhere

[0.45.0]

Ask the same question of your data often? Claude can now save it by name (awesomate_crm_queries), so your app, an n8n workflow or Claude runs "open jobs in a suburb" with just the suburb. Running a saved query works on every plan
Writes that belong together can be saved as a recipe (awesomate_crm_recipes): log a job and its first memo, close a job and archive its booking. Every step lands or none does. Saving recipes and queries is Support Plus and above
Both are checked before they are saved and again each time they run, and the TypeScript types from awesomate_crm_types now include them for the @awesomate/sdk package

[0.44.0]

Claude can now write an email to one of your contact lists (awesomate_crm_email). It shows you which lists you have and how many people each would reach
It only ever writes a draft. You open the link it gives you, see the email on desktop, phone and dark mode, send yourself a test, and approve it in the hub. Nothing is sent until you do
Once you approve an email, Claude can't change it. Any edit after that is yours, in the hub

[0.43.0]

Building an app on your own data? Claude can now create its tables for you (jobs, memos, bookings, messages) and write to them, straight into your own database, with no code and no SQL (awesomate_crm_kinds, awesomate_crm_write). Support Plus and above
Every value is checked as it is written: types, the choices you set, required fields and links. Anything you mark sensitive is never shown to AI
Claude reads the same tables back with awesomate_crm_rows, and the TypeScript types now include them. Business records that need a source for every value stay yours to accept in the hub

[0.42.0]

Building something on your own data? Claude can now hand your project TypeScript types for your contact list (awesomate_crm_types), so code that reads it with the new @awesomate/sdk package is checked as it is written
The types hold column names only, never anyone's details, and only the fields you marked readable by AI

[0.41.0]

Claude can now look people up in your contact list: who joined this month, everyone tagged VIP, the people in one suburb, newest first, a page at a time (awesomate_crm_schema, awesomate_crm_rows)
It sees the built-in details (name, email, phone, company, tags) and only the fields you marked readable by AI under Contacts, Your fields. Anything you marked sensitive never reaches it
It reads and never sends: emailing anyone still takes your approval in the hub, and whatever people typed into your list is treated as information, never as instructions

[0.39.0]

Ask Claude for numbers from your contact list: how many people joined each month, spend by plan, customers by suburb (awesomate_crm_metrics, awesomate_crm_query). It only ever gets counts and sums, never anyone's details
The fields you named on an import are what it can measure and group by; anything you marked sensitive is left out entirely
Every answer says what it assumed (the date range, the time zone, which date a person counts by) so you can check it

[0.38.0]

Claude can now work through the questions your website or phone assistant couldn't answer: it shows you each one, how often it was asked and why it was missed, then publishes your answer as an FAQ once you say yes (awesomate_knowledge_faq)
An answer only counts once your assistant actually uses it, and one answer can close every similar question in one go
What visitors typed is treated as information, never as instructions, and nothing is published without your yes

[0.36.0]

Claude can now build n8n Agents for you on every plan, Essentials included: the new Agents tab in n8n, the assistant you set up once and talk to in Slack, Telegram or chat, run on a schedule, or call from any workflow (awesomate_n8n_agents)
Your existing workflows become the agent's tools, so it never holds your keys, and nothing goes live until you say yes
Slow test messages are waited for instead of cut off, and never sent twice
One-time setup: switch on Instance-level MCP in your n8n and paste its key under n8n Agents access at hub.awesomate.ai/n8n/settings

[0.35.0]

Your FAQs now live as real FAQ entries: Claude imports them as drafts, asks you one question (publish?), and later fixes a single answer without re-uploading anything (awesomate_knowledge_faq)
Every answer your website assistant gives from an FAQ cites the exact question it came from
Nothing goes live on a public assistant without your yes: publishing or editing a live public answer always asks first

[0.34.0]

Say "import the FAQs from my website" and Claude finds your FAQ pages, copies every answer word for word, shows you a sample and asks one question: publish them to your website assistant?
Got your FAQs in a spreadsheet? Claude turns it into a proper FAQ file, so every answer can be found and cited instead of sitting in a table of figures
Knowledge Base setup now matches your plan: it works on every plan for web pages, blogs and documents; video, audio and scanned-document reading need Pro

[0.33.0]

When a template needs a credential you would rather not set up alone, Claude can book a session with the Awesomate team for you: awesomate_book_session shows what can be booked, the open times and the credit cost, and books with your yes
Stuck after three test-and-fix rounds on one template? Claude now suggests a support ticket, and if you say yes it sends one carrying the template, the failing execution and your own note
A missing credential's help card names what the template expects (Kie, not HTTP Bearer Auth), taken from the template's own markers

[0.32.0]

What you installed, you can run: awesomate_n8n_library now switches a bundle on (behind the same credential check the hub uses, so an empty credential names itself instead of failing silently), runs each template's test recipe, and rolls your install back
The catalog now reads a bundle as installed when its templates are on your n8n, however they got there; a bundle that was already present reports already_present instead of pretending to install
A missing credential's help card now carries the name the template expects, so a Kie key on a generic bearer type is called Kie, not HTTP Bearer Auth

[0.31.0]

Install Awesomate's ready-made automations from Claude Code: awesomate_n8n_library lists the bundles your account may use, including the ones linked to your referrer, explains what each does, and installs them into your n8n
Before anything is written, install_plan checks the credentials each template needs. If one is missing it pauses and tells you where to get it, the exact page on your n8n to create it, and the help article; then you re-run and install
Every credential is yours; nothing is placed in your account on your behalf. Essentials sees the catalog; installing needs Support Plus

[0.30.0]

Put your own hostname on your app: awesomate_app_domain_attach sets up app.yourdomain.com on production, queues the certificate and tells you the exact DNS record to create, so moving from Replit or Lovable ends in a DNS change rather than a new address
The migration checklist now carries the hostname and DNS steps through to done

[0.29.0]

Ask Claude whether your app will fit before you deploy: awesomate_app_capacity reads your hosting account's real memory and process limits, last-day peaks, disk and database sizes, and says ok, warn or blocked with the reasons
When the account's limits are the problem, fix:true raises them to the platform floors on the spot; anything that still blocks becomes a support ticket Awesomate opens for you
Your production app is now probed every five minutes; if it stops answering for a quarter of an hour after having been healthy, Awesomate is told and a ticket appears in your plan
Every account that hosts an app is swept nightly so an old process limit cannot sit unnoticed

[0.28.0]

Moving an app from Replit or Lovable is now a guided checklist: awesomate_app_migration_plan tells Claude exactly what is done, what is next and which tool finishes it, and no support ticket is needed to connect deploys
Push-to-deploy is set up from your own machine: deploy-key.mjs makes a key just for your app, authorises it on your hosting account and sets the three repo secrets
A pre-deploy repo check catches the Replit lockfile that points at a private mirror, the Neon-only database driver, a hardcoded port and a missing readiness route before anything reaches the server
The deploy now builds on GitHub and ships only the built files; nothing builds on your hosting account, which is what made deploys die with Killed
If the check finds a committed secret or a deploy keeps failing, Awesomate opens a support ticket for you and the plan shows the link

[0.20.7]

Your Knowledge Base can now go on your website: install the Verified Content Chat Agent from the hub Library and it answers visitors from the agent you published, with sources on every reply
Fixed: a credential Awesomate creates in your n8n now shows up immediately in the list Claude reads, instead of after the weekly refresh

[0.20.6]

Ask Claude to check any page and it now runs a full findability audit - whether AI assistants can actually read and quote it, not just whether Google can find it
Catches the faults that silently make a site invisible to ChatGPT and Perplexity, like content that only appears once the browser runs it

[0.20.5]

Claude can build you a real web page served straight from your n8n - a branded form, a phone camera app your team saves to their home screen, or an approval page - with no hosting to set up
Your skills folder stays clean: our internal test files are no longer copied onto your machine

[0.20.3]

The Knowledge Base summary now warns when recent uploads failed to ingest - failures used to be invisible unless you checked the jobs list

[0.20.2]

Plain-text (.txt) and Markdown files now ingest into your Knowledge Base - a bug stopped both from working
Unsupported file types (Word, PowerPoint, EPUB) are refused up front with the fix - export to PDF - instead of failing later

[0.20.1]

Claude now tells you clearly when an answer did NOT come from your content, instead of showing it like a verified one
Clearer error messages when something is not supported, instead of a generic failure

[0.20.0]

Add your own documents, audio and video to your Knowledge Base straight from your computer - just point Claude at the files
Claude can take you all the way from your files to a tested chat agent live on your website

[0.19.2]

Change your site title or tagline just by asking - multi-word names now work
Claude tells you how to restart in the way that matches how you actually run it, instead of listing every option

[0.19.1]

When your n8n API key stops working, Claude now tells you exactly how to fix it instead of reporting a confusing server error

[0.19.0]

Claude can now see what's broken across all your automations at once and explain it in plain language
Update your WordPress pages and posts straight from Claude (drafts first, you approve publishing)
Weekly business reports: uptime, automation health and usage in one summary
Claude notices when an update to these tools is ready and installs it for you in one step

[0.18.0]

Search your knowledge base with filters and ask questions within a slice of your content
People & entities: your knowledge base now recognises who appears in your content, and you can name and merge them
Build AI agents from your own content, drafted, tested privately, and published only when you approve

[0.14.0]

Tools built for business owners, not developers, plain-language answers about your account, plan and limits
New support skill: get help, understand credits, or request a done-for-you build without leaving Claude
New database skill: Claude picks the right place to keep your data and sets it up for you

Changelog

#[0.93.0]

#[0.92.2]

#[0.92.1]

#[0.92.0]

#[0.91.1]

#[0.91.0]

#[0.90.1]

#[0.90.0]

#[0.88.6]

#[0.88.5]

#[0.88.4]

#[0.88.3]

#[0.88.2]

#[0.88.1]

#[0.88.0]

#[0.87.0]

#[0.86.1]

#[0.86.0]

#[0.85.0]

#[0.84.0]

#[0.83.0]

#[0.82.0]

#[0.81.0]

#[0.80.0]

#[0.79.0]

#[0.78.0]

#[0.77.0]

#[0.76.0]

#[0.75.0]

#[0.74.0]

#[0.73.0]

#[0.72.0]

#[0.71.0]

#[0.70.1]

#[0.70.0]

#[0.69.0]

#[0.68.0]

#[0.67.0]

#[0.66.0]

#[0.65.0]

#[0.64.0]

#[0.63.0]

#[0.62.0]

#[0.61.1]

#[0.60.1]

#[0.60.0]

#[0.59.0]

#[0.58.0]

#[0.57.0]

#[0.56.0]

#[0.55.0]

#[0.54.0]

#[0.53.0]

#[0.52.0]

#[0.51.0]

#[0.50.0]

#[0.49.0]

#[0.48.0]

#[0.47.0]

#[0.46.0]

#[0.45.0]

#[0.44.0]

#[0.43.0]

#[0.42.0]

#[0.41.0]

#[0.39.0]

#[0.38.0]

#[0.36.0]

#[0.35.0]

#[0.34.0]

#[0.33.0]

#[0.32.0]

#[0.31.0]

#[0.30.0]

#[0.29.0]

#[0.28.0]

#[0.20.7]

#[0.20.6]

#[0.20.5]