Not to a company. Not to a subscription. To you, on the machine in front of you.
Free forever. No account. iOS is close behind.
Everything that knows you
lives somewhere else.
Your work. Your habits. Your half‑finished thoughts.
All of it a guest in someone else's building.
They set the rent. They read the mail.
They can ask you to leave.
We think that is the wrong way round.
How
Bloks runs entirely on your Mac. Your agents, your conversations and your keys sit in ~/.bloks on your disk. There is no Bloks account, because there is no Bloks server to hold one.
The only thing that leaves this machine is the engine you picked, talking to the provider you already pay. Bloks is not in the middle.
Bloks never asks who you are. No sign-up, no email, nothing to make.
When an agent wants to do something that matters, it stops and waits for you.
A skill is just markdown. You read all of it before it goes near an agent.
Read every line, build it yourself, run it at any company size. The one thing you cannot do is sell Bloks itself.
Who
Pick a role and it is made on the spot, named for the job, carrying that role’s skills. Or describe the job in a sentence and Bloks proposes the name, yours to change. Either way the agent opens with one question about how you want to work together, then gets on with it.
What
Give one a job and it starts. Add another when the work outgrows it: one on the launch, one on research, one holding the inbox at zero. They run at the same time, pull each other into a room when the work overlaps, and the one you made most senior has the last word.
Everything they do lands in a thread you can read: the files they made, the commands they ran, and the one decision they need from you. Answer it at your desk, or from your pocket.
Engines
Bring the agent you already run, or the key you already pay for. Connect the apps your work lives in. Bloks is the room they all work in.
Models and CLIs bring the one you already use
Apps and tools connect them from the chat
Switch an agent’s engine mid‑conversation and it keeps the thread. Ask it to use an app it cannot reach yet and a sign‑in card appears in the chat.
Install
Download it, drag it in, say hello. Free forever, and no account to make.
iOS is close behind; it pairs with your Mac from source today and the App Store build is next. Prefer arm64 or a .deb on Linux? Every build is on the releases page. New here? Start with the docs.
Pricing
The desktop app costs nothing because it costs us nothing: it runs on your Mac, with your keys. The one thing we charge for is the one thing we actually run, a relay that lets your phone reach that Mac from outside the house.
Bloks
Bloks Cloud
Bloks Teams
A person reads this list and writes back. There is no drip campaign behind it.
FAQ
Yes. Your own API keys, unlimited agents, no seat count, no expiry. It is not a trial and never turns into one. The source is public under FSL‑1.1‑MIT, so this is checkable rather than promised.
In ~/.bloks on your Mac: conversations, agent memory, keys, all of it. Back the folder up, move it to another machine, or delete it and be genuinely rid of the app. There is no Bloks account and no Bloks server holding a copy.
You need at least one engine. If Claude Code, Codex or another agent CLI is already installed and signed in, that counts and no key is needed. Otherwise paste any provider key, sign into OpenRouter from Settings, or run Ollama.
On a tool-running engine: read and write files, run commands, browse, use apps you have connected, and keep notes in their own memory. Anything consequential stops and asks you first, on the Mac or on your phone.
Yes. Put them in a room and address one with @name or just talk. Juniors answer first, the most senior speaks last, and they can hand work to each other mid-thread. Teams you like can be saved and rehired.
Three ways. Connect apps like Slack or Gmail through the built-in connector cards, register any MCP server you already use, or let an agent request an API key with a secure field in the chat. Keys are stored on your Mac and never appear in the conversation.
They pause with it, and scheduled runs skip rather than pile up. Bloks Cloud does not change that and is not sold as though it did: it carries your phone to your Mac and buzzes you when an agent wants an answer, but the Mac is still the thing doing the work. Shut the lid and the work stops.
Two things. Reach: the iPhone app works away from your own network instead of only on the same wifi. Push: an approval can buzz a phone in your pocket rather than waiting for you to open the app. That is the whole product, for $15 a month. It is not hosting, and the relay in the middle carries ciphertext it cannot read, which is why a push says an agent needs you and never says what about.
No. The engine you picked talks to the provider you pay, directly. Bloks orchestrates on your machine and resells nothing, marks up nothing, and cannot read what it does not carry.
Bloks Cloud
On your own network the iPhone app already talks to your Mac directly. Bloks Cloud is the part that keeps working from a train: a relay both ends dial into, and a push that can wake the phone in your pocket the moment an agent needs an answer.
The relay carries ciphertext. Your phone and your Mac agreed on a key while you were standing at both of them reading a six digit code off the screen, and the relay never saw it. It learns that a blob moved, how big it was and which space it belongs to. It does not learn what it said, which is why a push reads “An agent needs your approval” and nothing more.
What you are buying is reach and push, and only that. Your agents still run on your Mac with your own keys, and shutting the lid still stops them. Hosting them somewhere else would be a different and much larger product, and this is not it.
$15 a month, billed by Stripe, on the Mac that owns the space. Or watch releases on GitHub; every version lands there first.