Any model, your key
Point a bot at Claude, GPT, Grok, or a local model. Swap per bot — the cheap one triages, the smart one writes.
Give a bot real work. It signs in to your tools, uses them the way you do, and comes back when it needs you. Your keys, your model, your machine.
$ nothing is gated, nothing phones home
Live demo — pick a bot, open its computer, add a routine, or start a new chat.
Every bot gets a sandboxed browser and shell — running in your Docker, in your account, behind your firewall. Sessions and credentials never leave it.
Point a bot at Claude, GPT, Grok, or a local model. Swap per bot — the cheap one triages, the smart one writes.
Show a bot a workflow once and it saves a routine as plain Markdown you can read, edit, and commit.
Set what a bot may do alone and what it must ask about. Every action lands in an audit log you own.
Every bot gets a sandboxed browser and shell: in your Docker, in your account, behind your firewall. Sessions and credentials never leave it.
Forbid pressing, and the click, Enter and Space all stop. Rules are written about what an action does, not about which tool was called.
Every permitted, refused and failed action is recorded, and the database itself refuses to change a row after it is written.
A bot can create a password, have it typed into a page, and never see the value. Only you can look at it.
Run any limit in record-only mode first, read a week of real decisions, then switch it on for real.
When a bot hits something it cannot do, that is data, not a dead end. It records the gap, and the ones it can close it closes — sometimes by learning a routine, sometimes by proposing a fix to Twiko itself.
A bot can read Twiko's own source and propose a change. The patch is applied, typechecked and run against the tests in an isolated container — then handed to you as a diff. Nothing merges itself.
Every capability a bot lacked is logged and counted. The wall forty bots hit is one decision, not forty tickets — and one click hands it to a bot to work out.
A bot convenes a room, hands work and finished files to a colleague, and wakes it when it is named. The analyst delegates, the designer renders, the reviewer checks — in one place you can read.
A captcha or a login wall is recognised on sight and the screen is handed to you with a plain reason — never clicked at for minutes and filed as impossible.
Start a new bot and it interviews you — a few questions about the work, how you write, and where it lives. Then it gets going.
Researches accounts overnight, scores intent, drafts in your voice, leaves a review list.
Archives the noise, replies to routine threads, parks drafts that need your read.
Reads every applicant, shortlists against your bar, writes the intro emails.
Matches receipts to charges, files the report, asks before guessing.
Reproduces reports in a real browser and attaches steps to the ticket.
Keeps renewal context, answers known questions, escalates the rest.
Watches spend daily, pauses what is not converting, reports what moved.
Runs the week: briefings, bookings, and handoffs between your other bots.
Twiko is Apache-2.0 licensed and runs on your own machine with your own model keys. Nothing is gated, nothing phones home.
Clone the repo, add a model key, and hand it something you have been putting off.