Tester Agreement

What the testing team is

Akili Code OS is not open for public registration. Instead we let people in a group at a time, read every application by hand, and give each person who gets in a real budget and a direct line to the people building it.

We do it this way for one reason: a launch that lets everybody in gets you a thousand accounts and no idea whether the product is good. A hundred and fifty people using it on real work, who will tell us the truth, is worth more.

A cohort runs six weeks.

Your tokens, exactly

We would rather be precise here than generous-sounding, because the difference matters once you are halfway through a migration.

"Rolling thirty days" means the window moves with you. It is not a single pot of twenty million that runs out and is gone — as older days fall out of the window, that room comes back. Over a six-week programme you will therefore have more than twenty million tokens available in total. We are telling you this because the honest description and the marketing-friendly one are different, and you should have the honest one.

The daily cap is a safety net, not a budget. It exists so that one agent stuck in a retry loop cannot empty your account before lunch. If you are doing something big and it is in your way, ask and we will lift it — for testers the answer is usually yes, and there is a button on your testing page that puts the request in front of a person.

Your dashboard shows what you have used in the last thirty days and what is left. That number comes from the same counter the service enforces, so the dashboard and a refusal can never disagree.

What we ask of you

Four things, none of them onerous:

• Use it on something real. A demo repository tells us nothing. The bugs worth finding only appear on a codebase with history in it.
• Tell us when it is wrong. There is a Report button on every page and it takes about thirty seconds. Bad news is more useful than good, and vague news is no use at all — "it hung" is worth less than "it hung on a repo with submodules".
• Try the things we ask about. Your testing page lists two or three a week. Left to ourselves we all test what we already do, which is how the weak parts stay untested.
• Reply if we write to you. Not to every message — but when a person asks you a direct question, an answer is the thing that makes this programme work.

None of this is enforceable and we are not going to chase you. If life gets in the way, say so and we will hold your place or give it to someone else, whichever you prefer.

Pre-release software, and what that costs you

Being clear about this is the point of the page.

• It will have bugs, including ones we have not seen.
• An agent edits files on your machine. It can edit them badly.
• Data loss is possible. Every run takes a git checkpoint before it starts, which makes Revert one click — but use version control, keep backups, and do not point it at the only copy of something that matters.
• Things will change under you. Features may be reworked or removed during the programme. We will tell you when that is coming.
• There is no uptime promise. If the service is down we will say so.

You are testing software. The limits of liability in our Terms apply here with particular force, and the programme is free precisely because of this section.

What we can and cannot see

Nothing changes about this because you are a tester. The Privacy Policy applies in full, and the part that matters most:

• We see a token count per day. Not your prompts, not your files, not your transcripts.
• A report you file carries what you typed plus four fixed fields: app version, operating system, which model was active, and the last command name. Anything else the client sends is dropped before it is stored — enforced in code, not policy.
• We can see whether you have been using it, and roughly how much. That is how the programme is run: if forty people go quiet in week two we need to know, because it is almost always our fault.
• We do not train models on anything of yours.

Keeping unreleased things unreleased

You will see features before anybody else, and some of them will not survive to launch. We ask you not to publish screenshots, recordings or descriptions of anything unreleased until it ships.

This is a request stated plainly rather than a non-disclosure agreement, because the kind of person we want on this team honours the first and resents the second. You are free to say that you are testing Akili OS, and free to say publicly what you think of it — including that it is bad. We would rather hear it first, but we are not asking you to be quiet.

If you publish something unreleased after being asked not to, we may end your place on the programme. That is the only consequence, and it is the last thing we want to use.

Your feedback, and being credited

When you tell us something, we may act on it, build it, and ship it, without owing you anything for it. That is the ordinary bargain of a test programme and we would rather say it than leave it implied.

In return: if we ship a fix for something you reported, we credit you by name in the release notes, and we email you to say so. If you would rather not be named, say the word and we take it out — before or after publication.

Your place on the team

Your invitation is yours. The link is single-use and tied to your address; please do not pass it on. If you know somebody who should be here, tell us and we will look at them properly rather than routing them through your invitation.

We may end a place if an account is shared, if the acceptable-use section of our Terms is broken, or if the programme has to be cut short. We will tell you which, and you keep the right to your data either way.

You can leave whenever you like — delete your account from your profile, or just reply to any email and say so. No exit interview.

When the programme ends

Nothing switches off overnight. A week before the end we will email you and say exactly what is about to happen. Then:

• You keep whatever tokens are left. Work in progress does not stop dead on a Friday.
• You get a founding-tester price — a permanent discount on whichever plan matches what you were actually using — and your organization keeps that marker for good, through any later plan change.
• Billing comes back in your account. No card is needed until you decide you want one.
• If we shipped a fix you reported, you are in the release notes.

The programme ends in an offer, not a lockout. A paywall that appears overnight on a tool somebody has wired into their working day is not something we are willing to do.

If something is wrong

Reply to any email we send you; they go to people, not to a queue. For anything urgent or awkward — a bill you did not expect, an account you cannot get into, something the agent did that it should not have — write to hello@akilios.dev and say so plainly. We would much rather hear it early.