Where KimtOS is heading
A browser, not an extension.
KimtOS began as a new tab: a set of local-first tools that open the moment you need them. The tools kept getting better, and the shape they wanted kept getting clearer. The destination is a browser — one built around the work you do, with the tools inside it rather than bolted on.
The useful things are scattered: twenty tabs, twenty accounts, twenty subscriptions. Notes in one service, tasks in another, a PDF reader here, a transcription tool there — each behind its own login, each sending your work to its own server.
KimtOS already gathers 21 of those tools into one place, on your machine. The productivity browser is where that idea stops being an add-on and becomes the thing itself: notes, tasks, PDFs, clipboard, whiteboard, transcription and on-device AI, native to the browser you already live in.
Why a browser follows
Four steps, each leaning on the one before it — the reason the destination is a browser and not another app.
- 01
Local-first is the whole product
Nothing you write, say or scan leaves your machine, because there is no server to send it to. That is not a privacy setting bolted onto a cloud product — it is a decision about where the computation happens. A browser is where it happens most, so it is where that decision has the most to give.
- 02
An extension is a guest
An extension lives inside rules another browser sets — what it may reach, how deeply it may integrate, when it is allowed to run. KimtOS does a great deal within those rules, but they are still someone else's. Owning the browser ends the guest status: the tools stop being a layer on top of the surface and become the surface.
- 03
Apps as tools, not islands
Every KimtOS app already declares its actions as MCP-shaped tools. Today those declarations are dormant, but the shape is deliberate: the goal is to make each app addressable as a set of tools across the whole browser, so notes, tasks, PDFs and the rest stop being isolated windows and start being building blocks a piece of work can compose.
- 04
Intelligence that stays home
The AI models run on your own hardware now, and the browser is designed to carry that promise further — a Personal Intelligence Workspace, where the intelligence that helps you work runs on the machine in front of you rather than in someone else's data centre.
Said honestly
The models that would drive those tools without you are not there yet. No on-device model we ship is reliable enough to be trusted with your work unattended, and we will not pretend it is — so the tool declarations stay dormant until one is. This is the shape, described plainly: the plumbing is laid, the autonomy is future.
This is a vision page, and we mean the word. There is no date here, no waitlist, no half-built thing dressed up as shipped. KimtOS is real and on Chrome today; KimtOS Browser is where a local-first workspace leads if we keep pulling the thread. When there is something to try, you will be the first to know.