Run TomaTío yourself
Your own brain, on your own WordPress.
When the code goes public, anyone should be able to install TomaTío on their own WordPress, connect Claude in minutes, and keep getting every improvement the team ships. This page walks that journey step by step, says honestly what works today and what is still missing, and shows where it sits on the launch roadmap. The dates are proposals.
The promise to self-hosters
What someone running their own copy can count on, from the first public release.
- Same software as ours.The brains we host run the exact release zip anyone can download. No private fork.
- Updates arrive by themselves.New versions show up in WordPress's own Updates screen, with one-click or automatic updates.
- Updates are safe.Database changes migrate automatically, connectors keep working, and every release has a changelog.
- Nothing is locked.Every feature is in the free plugin. Optional services stay optional.
- You can leave.Export everything with the Portable Context Protocol (PCP) and move to any host or tool.
- Verifiable.Every release zip has a checksum, and the code is GPL on GitHub.
Three ways to try it
from a quick look to real use| Where | Good for | Connects to | Today |
|---|---|---|---|
| On a host you already have WordPress 7.1+, PHP 8.3+, HTTPS | Real use with a team; best on its own subdomain | claude.ai, Claude Desktop and Claude Code; other AI tools being tested | Works, rough edges |
| On your laptop WordPress Studio or any local WordPress | Developers trying it alone | Claude Code, with an application password on localhost | Not tested yet |
| In the browser WordPress Playground, one link | A look around the screens, with no setup | Nothing: a site that lives only in your browser has no address an AI can reach | Idea |
The journey, step by step
what a newcomer does, and what is in the wayStartedFind it and see how to start
This page is the start. The README will open with what TomaTío is, the requirements, a 10-minute install, how to connect Claude, and the Bill of Rights.
HurdleMeet the requirements
- WordPress 7.1 or newer and PHP 8.3 or newer: the plugin will not activate on older versions
- HTTPS, so Claude can sign in
- Ideally a site or subdomain of its own, not inside a busy existing site
PHP 8.3 is the likeliest hurdle, because some shared hosts still default to 8.1 or 8.2. The team is deciding whether 8.2 is enough, and the install guide will show how to switch PHP versions.
Not public yetGet the right zip
Every release already builds a ready-to-install zip with a checksum; they are not public yet. When the code goes public, each release on GitHub carries that zip. GitHub's own “Download ZIP” of the source will not work, because it lacks the packages and built files, so the README points at the releases.
WorksUpload and activate
Plugins → Add New → Upload, then Activate: standard WordPress. Before the code goes public, the plugin's name, description and links move to TomaTío.
Next releaseA brain that is ready to use
The Get started checklist walks through scopes, agents and connecting an AI. With the next release, a new brain also starts with a team scope, so there is nothing to set up first.
WorksConnect Claude
The Connect an AI page gives the exact address to paste; claude.ai, Claude Desktop and Claude Code sign in with OAuth. ChatGPT, Cursor, VS Code and other tools are being tested.
Hard todayShare a document
Share links need a separate preview subdomain today, which most people running their own copy will not set up, so sharing stays off for them. A way to share from the brain's own address is being designed, with security reviewed first.
The big oneKeep getting every improvement
Today a self-hosted copy does not hear about new versions: the plugin has no update source yet, and it is not on WordPress.org yet.
- Before the code goes public: a built-in updater that checks TomaTío's GitHub Releases, verifies the zip's checksum, and offers the update in WordPress's normal Updates screen (one click, or automatic if the site allows it).
- After the public launch: the WordPress.org listing takes over updates, and the built-in updater steps aside, so nobody is offered the same update twice.
- Always: the database migrates on update, tool names stay stable (a renamed tool keeps its old name as an alias), every release has a changelog, and an export before updating is one click.
AlmostTake everything with you
PCP export, restore and import are built and ship in releases 1.5 and 1.6. Export opens to everyone after a final round trip between two test brains.
Before “Self-host ready”
proposed for ~7 November, with the code going public| What | Status |
|---|---|
| Built-in updates from GitHub Releases, with checksum checks, until WordPress.org takes over | Planned |
| Every release publishes its zip and checksum to GitHub Releases | Planned |
| The plugin's name, description, author and links say TomaTío | Planned |
| A README and install guide: requirements, a 10-minute install, connecting Claude, updates, and leaving | Planned |
| The PHP minimum: 8.3 today; 8.2 would reach more shared hosts | Deciding |
| Sharing without a preview subdomain | Being designed |
| A new brain starts with a team scope | Next release |
| Export open to everyone | After the round trip |
| Someone new installs from the zip on ordinary hosting and connects Claude in under 10 minutes | ~21 Nov |
On the launch roadmap
see the full roadmapMilestoneSelf-host ready
The code public on GitHub, release zips there, built-in updates working, and a README with the 10-minute install. Anyone can run it, and it stays up to date.
CheckThe 10-minute install, done by someone new
One of the checks in the “Open it up” gate before the public launch, including “receives the next update without doing anything”.
PlannedThe WordPress.org listing
Install from inside WordPress by searching for TomaTío, with updates from WordPress.org. Review can take a few weeks, so it is submitted at the public launch.
IdeaTry it in the browser
A WordPress Playground link with TomaTío and sample data, for a look before installing. It cannot connect an AI, so it complements the real install rather than replacing it.