Docs

Crads-AI is the AI foundation for you and your business, and everything about how it works is here, in the open: what a mineral is, how you get one, how to talk to it and teach it, how to connect things to it, and what happens if we go away. Start from what you came to do.

Watch

An assistant that knows you: why I built it, what it is, the four Cs, and how you get one. Three and a half minutes, captions, no voice.

Four short tutorials sit on their pages: Set it up, Sign in, then Claude Code, The interview, and How you ask.

By goal

I want to know if this is for me

What it actually is, the questions everyone asks, and the two words that follow.

I want to set one up

A token, fifteen minutes of building, and an interview that makes it yours.

I want real work out of it

Get it doing things, ask it well, tell it what it got wrong, and know where it stops.

I want it in my inbox and my pocket

Mail and calendar with your own key, a private Telegram bot, and every other plug.

I want it safe and mine

The backup only you can do, the machines that can open it, and what outlives us.

I want to fix something

The symptom list, the one page that tells the truth about a connection, and a hand.

What it can do

Every skill your mineral ships with, straight from the code. Each one runs when you ask, and most take a schedule.

Everything, in reading order

Start here3 pages

What this is, whether it is for you, and the two words everything else uses.

What an AI EA actually isThe category, explained without the hype: what changes about your week, who it is for, and what it is not. What a mineral isThe two words these docs use for the thing you get, and why it is a private box of your own rather than a seat in someone's software. Questions, answered straightThe questions people actually ask before and after getting a mineral, each answered in a few sentences with the deep page beside it.

Getting set up7 pages

From nothing to an assistant that is awake, knows you, and reaches your phone.

Get a Hetzner API tokenThe five-minute walk from no account to the token the setup wizard asks for, and what that token actually is. Get a DigitalOcean API tokenThe five-minute walk from no account to the token the setup wizard asks for when you pick DigitalOcean, and what that token actually is. Your first hourFrom opening the app to an assistant that is awake, one small step at a time, with what you should see at each one. The interviewThe hour that turns a blank machine into an assistant that knows your world, and what it asks about. Your first weekSeven days from a finished setup to an assistant you would miss: what to switch on, what to correct, and what to ask. Connect Google, with your own keyFive console visits, one file, one sign-in, per account. Your Google key never touches our infrastructure, and here is why we made you do it the hard way. Connect TelegramYour assistant in your pocket, step by step: your own private bot, made in about two minutes, that drafts and never sends.

Working with your EA11 pages

How to talk to it, teach it, build on it, and get it to find what you are missing.

How your assistant thinksThe one picture behind every page of these docs: a mind that is rented, a memory that is yours, and senses you add one at a time. A day with your assistantOne ordinary working day, morning to close, showing where the assistant fits and why tomorrow is slightly better than today. The CRIT methodFour steps that turn a vague ask into a brief your assistant can act on, and why the third step is the one people skip. Six prompting habitsThe small changes in how you ask that make the biggest difference to what comes back, with an instead-of table you can keep open. Grow the brainThe everyday habits that turn a seeded brain into one that knows your business: correct it, tell it things, capture, and bring documents in. Teach it your voiceThe three-step loop that makes drafts sound like you, the self-check you can ask for, and the one page in the brain where your voice lives. Write your own skillTurn a task you do more than twice into a command you run by name, without writing code. Starter recipesTwelve recipes for a working week, five already on your mineral to switch on and seven to build as skills of your own. What it will not doThe limits that are built in, the rules I hold mine to, and how to tell a broken connection from a thin brain. Find what you do not knowFive ways to make your assistant surface what is missing, from your brain, from a plan, and from a decision you are about to make. Use Claude Code on your mineralWhere you talk to your assistant. The app is the window onto your mineral; Claude Code is the room you work in.

Every page of the app7 pages

Each screen, opening with the app's own words for it.

OverviewThe page your mineral opens on: what your assistant knows, and how it is doing. Your pebbleThe machine itself: its name, where its backup goes, the computers that can open it, and your own pages. BrainEverything your assistant knows, drawn from the files actually on your mineral. SkillsWhat your assistant can do, and when it runs. ConnectionsWhat your assistant can reach, and whether each one is still working. SecretsEvery password, token and key this mineral holds, and what each one is for. TerminalTalking to your assistant directly, and when that is the right way in.

Keep it running6 pages

Backups, connections, other machines, and what to do when something looks wrong.

Back up your mineral, and get it backWhat is already backed up, the one thing you have to do yourself, and why the passphrase matters more than the backup. Fix a connection that has stopped workingWhat an expired token looks like, why it happens, and the one place that tells you the truth. When something looks wrongThe short list of symptoms, what each usually means, and where to look before you worry. Machines that can open your mineralThe roster, what a key is, removing a machine, and why the door has no back door. Add another computerA machine you already trust lets the new one in, over SSH, with no account and no service in the middle. Let someone look at your mineralGranting support access: what it opens, when it closes, and how to end it early.

Understand it3 pages

The honest mechanics: who edits what, how updates arrive, and what happens if we go away.

Who edits whatThree layers on every mineral: the machinery the project maintains, the infrastructure you own, and the pages you build. How updates reach youYour mineral restarts nightly onto new software, what that does and does not touch, and how to tell what you are running. What happens if Crads AI goes awayThe honest answer to "what if you pick up another job", and why the self-hosted shape makes it survivable.

Reference5 pages

Generated from the software itself, so it cannot drift.

Every skill your mineral ships withThe 11 engine skills present on every mineral, with what each one does. What you can connectThe 62 services in the curated connections catalogue, and how each one signs in. The jobs your mineral runs by itselfThe 15 machinery jobs Crads AI maintains on every mineral, and what each one is for. The wordsA plain glossary of the terms these docs use, with the page where each one first matters. Where these ideas come fromThe four people whose thinking shaped how I use my assistant, what each one gave, and which pages carry it.

Legal3 pages

The written detail. Version-stamped, and it changes only with the version.

Privacy policyWhat is stored, where it runs, what leaves your mineral, and why almost none of this page is about us any more. Terms of serviceWhat you get, what it costs, what we each promise, and how either of us ends it. Acceptable useThe short list of things you must not do with a mineral, and what enforcement honestly means when the machine is yours.