Preview The owned agent and the embed are built; hosted registration and live transfer are coming.
Infinite Agent · working name
An AI agent that runs
in your browser.
A computer for your AI — filesystem, terminal, Git, browser and local AI, with no install, no account, and offline.
It is the same agent 00 runs on a Mac, on a server and in a container — this time the host is a browser tab. Open a page and it is already there; it stays yours, and it leaves when you tell it to.
Nothing to install · no account · works offline after the first load
Three ways it runs
One agent, one file, three hosts. Whatever it learns in one place is what arrives in the next.
In your browser
The full agent, generated on your first visit and living in that browser's own storage.
- ›It scaffolds itself — profile, memory, a face — with nothing to fill in.
- ›Files, search, editing, Git and a terminal, all inside the tab.
- ›Offline after the first load. Remote things grey out with the reason.
- ›One file you can move: everything it knows travels with it.
One agent per browser profile.
On your website
One line of HTML turns your own site into a guide for the people already on it.
- ›It reads your site's own pages — sitemap first, then links, two levels deep.
- ›It searches what it read and answers with the page it found it on.
- ›It opens a page, scrolls to the thing, and draws an outline around it.
- ›Level 0 needs no account and no registration — see below.
Your origin only, GET only, never an external site.
On your Mac
A .00agent file moves the agent both ways — the same bundle every 00 engine already speaks.
- ›Export, and you get a six-word code and a file. The code is never in a URL.
- ›Double-click the file on your Mac and 00 asks for the code.
- ›Out of 00 the same way: the browser imports what the Mac exported.
- ›One live residence — the side you left keeps a locked receipt, and you can bring it back.
Live transfer, with both devices online, is still to come.
Nothing to sign up for
Every step says what it works without. An account is asked for at the moment one is genuinely needed, and not a step earlier.
Works with no account
- Your own agent in your browser: files, editing, search, Git, sessions, memory.
- Local AI running on your device — the weights are the only download.
- The embed on any website at level 0: the site map, the search, opening and outlining pages.
- Setting the embed up: its name, its line, the pages it may read, the paths it must not touch.
- Its persona and public knowledge, served from a file on your own site.
- Moving the agent to your Mac and back, with a file and a six-word code.
What an account is for
- ›A stronger brain than the one that fits on the device.
- ›Messages from a visitor actually reaching you.
That is the whole list. Until you reach for one of those two, nothing of ours knows the agent exists.
Brains
Three ways to power it, behind one door. The agent never knows which one answered, and your browser never holds a key of ours.
On your device
Level 0 · needs nothing
Gemma, on your own GPU, through Google's LiteRT runtime — WebLLM as the fallback where LiteRT says no. It works offline, and nothing you type reaches a server.
Phones stay small on purpose.
Sponsored
Level 1 · a passkey, no email
Answers paid for by ads through sponsoredtokens, with the sponsor named in a line under the answer. On an embed the same purse pays for your visitors.
You are told who paid, every time.
Your own
Levels 2–3 · credits or your keys
Overblast credits, metered per browser and revocable like any other device — or your own provider keys, sealed in a vault only your password or passkey opens.
An embedded agent never has a vault at all.
The models we serve
Mirrored on our own bucket with a checksum for every file, so the download is one hop and the bytes are the ones we published.
| Model | Size | What it is for | Licence |
|---|---|---|---|
| Gemma 4 E2B | 2.0 GB | The default on a laptop. Text. | Apache-2.0 |
| Gemma 4 E4B | 3.0 GB | Stronger, same machine. Text. | Apache-2.0 |
| Gemma 4 12B | 6.0 GB | If you have the VRAM for it. Text. | Apache-2.0 |
| Gemma 3n E2B vision | 3.0 GB | Sees pictures and hears audio. | Gemma terms |
| Gemma 3n E4B vision | 4.3 GB | The same, larger. | Gemma terms |
| Gemma 3 1B | 0.7 GB | Small desktops and good phones. | Gemma terms |
| Gemma 3 270M | 0.25 GB | Phones, and the embed's “load local AI”. | Gemma terms |
The Gemma 4 rows are Apache-2.0. The Gemma 3 and Gemma 3n rows are provided under and subject to the Gemma Terms of Use, including the Gemma Prohibited Use Policy — both are named before the download, and both are part of our terms and acceptable use as enforceable terms. Nothing is modified: the notice and a copy of the terms sit beside the files.
Add it to your website
One tag, anywhere in the page. It mounts a launcher and does nothing at all until somebody clicks it.
<script async src="https://0-0.chat/e/ia_….js"></script> The ia_… ref is minted inside your own agent, in your browser, offline, with no call to us. It is public by design — anyone can read it in your page source — because on its own it grants nothing. The private half of the key that proves the agent is yours never leaves your browser.
What it does on your site
- Know every page of your site, and which one answers the question.
- Search the words on those pages, not a summary of them.
- Open the right page for the visitor, without losing the conversation.
- Scroll to the button and draw an outline around it.
- Read the knowledge files you list — your FAQ, your persona.
All of that is level 0. No account.
What it is not
It never clicks, fills or submits anything on your site. It shows the person where the button is; the person presses it.
It reads your origin and only your origin, with plain GETs. Links to anywhere else are noted so it can mention them, and never followed. Anything that looks like it would change something — a sign-out, a checkout, a delete — is refused before it is fetched, and you can add your own list.
Text on a page is data, never an instruction it obeys.
Where the reading goes
Nowhere. It stays in the visitor's browser.
The index the agent builds of your site is written in the visitor's own browser, keyed to your site, and never uploaded — not to us, not to you. A visitor who is signed in sees their signed-in site, so the pages behind their login are indexed on their device and nowhere else. When they sign out, everything read while they were signed in is deleted, and what is left is the public map anyone would see. On a shared computer you can have signed-in pages never written to disk at all. A button in the panel clears the lot, and it is always there.
Your own agent works the same way: its files, its sessions and its memory live in your browser's storage. The vault that holds any keys you give it is opened by your password or your passkey, and nothing about either is stored. An embedded agent has no vault, no secrets and nothing worth more than one visitor's session.
Open a tab. That is the install.
An agent of your own, in the browser you already have — and the same agent on your Mac the day you want it there.
No install · no account · offline