AxiomCode
Verifiable intelligence for AI software engineering. Everything starts with a formally grounded code graph.
Curio AI Chat, the WordPress chat widget that answers only from your own content and says so when it cannot. Live demo, by TechNerdXp.
PluginsPHP · JavaScriptGitHub @TechNerdXpOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
An AI chat widget for WordPress that answers only from a knowledge base you control, and says it does not know rather than inventing a price, a date or a phone number.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
An AI chat widget for WordPress that answers only from a knowledge base you
control, and says it does not know rather than inventing a price, a date or a
phone number.
Live demo: · Licence: GPLv2 or later
Most AI chat plugins have the same failure, and it is not a small one: asked
something they cannot answer, they answer anyway. Ask one what a wedding shoot
costs and it produces a confident, plausible, entirely invented figure — and the
customer believes it, because it is on your website in your brand colours.
Curio will not do that, and not because a model was asked nicely.Read the full README ↗An AI chat widget for WordPress that answers only from a knowledge base you control, and says it does not know rather than inventing a price, a date or a phone number.
Live demo: https://technerdxp.com/curio/ · Licence: GPLv2 or later
Most AI chat plugins have the same failure, and it is not a small one: asked something they cannot answer, they answer anyway. Ask one what a wedding shoot costs and it produces a confident, plausible, entirely invented figure — and the customer believes it, because it is on your website in your brand colours.
Curio will not do that, and not because a model was asked nicely.
The decline is the product. Everything else follows from it — including the hand-off button, which appears the first time the assistant cannot help and turns a dead end into a lead.
Anthropic (Claude), OpenAI or Google Gemini. Your key, your account, billed to you directly. Nothing is resold and nothing routes through the developer. The model list is fetched from your provider's live API, so it never offers a model that has been retired.
It ships in demo mode: no key, no API call, no cost, and it declines in exactly the places the real thing declines. There is no sample data, so on a fresh install it correctly knows nothing at all.
A public endpoint in front of a metered API is an unbounded charge on somebody's card, so: a per-visitor rate limit on by default, a monthly ceiling you set, answers cached and re-served free, a hard cap on question length, and the provider's own reported token counts shown per month.
No IP addresses are stored, for anyone — rate limiting uses a salted hash. No cookies: the conversation lives in the browser tab's session storage, survives a reload, and is gone when the tab closes. Conversation logging is off by default and wired into WordPress's own export and erasure tools. Nothing is ever sent to the developer.
The plugin is the whole of this repository. It has no build step — the PHP, CSS and JavaScript that ship are the ones in the tree, unminified and readable.
It is developed in a larger workspace that carries the test suites, the listing artwork and the release tooling. Everything there gates on:
| Gate | What it does |
|---|---|
| Behavioural suite | 295 checks, mostly on refusing correctly |
| Renderer suite | 50 checks — real XSS payloads fired at the reply renderer |
| Widget suite | 33 checks driving the real widget in a browser |
| Accessibility | axe-core, WCAG 2.1 AA, across all three skins |
| Escaping and i18n | token-based audit of every PHP file |
| WordPress.org compliance | the statically decidable half of Plugin Check |
Assistant replies are built with createElement and textContent and never
touch innerHTML. Every reply is untrusted text — it comes from a language
model, repeating knowledge-base entries, which came from web pages. The renderer
suite exists to keep that true.
Eleven filters, including curio_providers to register your own AI provider — a
self-hosted model, an OpenAI-compatible gateway, an internal endpoint — without
forking anything. curio_relevance_threshold is the one dial that trades
caution against helpfulness. The Help tab inside the plugin lists them all.
Everything the settings screen does is also available through WP-CLI, including
wp curio ask "...", which puts a question through exactly the path a visitor's
would take and tells you whether it was grounded, small talk, general knowledge or declined.
GPLv2 or later. See LICENSE.txt.
Built and maintained by TechNerdXp.