Free plan, available today
It reads the mail, drafts the reply, and edits the file. It runs on your computer, and it asks before it changes anything.
Say what you want done. It opens the files you point at and works on them where they already are.
Before it touches anything, it tells you what it will do and in what order, in words you can read.
Nothing runs until you answer. Say yes and it goes ahead; say no and it stops where it stands.
An example of the app window. It is not a live run.
One assistant, on your own computer, that works across the mail and chats you already use. You sign in once, hand it a task, and it asks before it changes anything.
You sign in at horon.ai with a passkey, Google, Apple, or email and password. Your account, session, and passkey records live on our servers.
Router, Messenger, and Mail run on your machine. Your accounts and keys for each service stay there, in Router.
Your files stay where they are. The assistant reads them on your computer, and we do not keep a copy of them on our servers. Your account lives on horon.ai: the sign-in, session, and passkey records are stored on our servers, and your files are not part of that.
When the assistant needs a model, the request goes to the account you chose and the answer comes back. Your accounts and keys for each service stay on your own computer, in Router.
You run one command on a plugin file you already have: Horon checks it, copies it into place, and loads it the next time it starts. There is no store and no one-click marketplace yet.
These are sentences you say as they are. The assistant does the work that follows, and asks before it changes anything.
September invoice — one question
Re: October schedule
Waiting on you: 2 replies
It opens the mailbox you already connected, reads the messages in the thread one by one, and writes back what is still waiting on you.
To: the client
Subject: Re: invoice
Draft saved · not sent
Drafting and sending are two separate tools. The draft stays in your drafts folder until you send it yourself.
invoice-october.xlsx
Ready to write two amounts into the sheet
Waiting for your answer
It edits the file on your computer, in place. The write waits for your answer, like every change it makes.
The windows above are illustrations of everyday work, not live runs.
Three programs, each with one job: model accounts, chat apps, and mail.
Where your model accounts live.
The chat apps you already use.
Gmail and Outlook.
Names, not logos: the chat apps, the mailboxes, and the sign-in methods you can pick from today.
A run has three parts, and the last one is your answer.
Say what you want done. It opens the files you point at and works on them where they already are.
Before it touches anything, it tells you what it will do and in what order, in words you can read.
Nothing runs until you answer. Say yes and it goes ahead; say no and it stops where it stands.
The work lands where it already lives, and every step stays readable afterwards.
Looks right. Nothing is broken.
An example run, line by line: what it read, the plan it wrote, the question it asked you, and the tools that ran.
It works with the tools you turned on, waits for your answer, and says what it is about to do.
The device helper runs file, messenger, and command work for a linked device, so you can read and write files and run commands on a machine you are not sitting at.
The web app is live. The phone shell is built and does not reach a server yet. The desktop build is a test bench with no installer to release.
This site, plus the console behind sign-in. Your account and its sessions are kept for you, so the browser and your other devices see the same account.
A phone app with four tabs and a sign-in screen. Sign-in returns to the app through its own link, and the app does not reach a server yet.
A test bench that talks to the assistant on your own computer. It is not a product client, and no installer is released.
Your account keeps your devices in step. When a connection drops, the device picks up from the last event it saw. The helper on that machine does only what its consent file allows, and it records every decision.
One server instance for now. The connection, the event log, and issued sign-ins are not shared between separate running copies, so running more than one copy is still ahead.
The apps do not hold a browser cookie, so they carry their own sign-in. A machine without a browser proves itself with a short code, and both app links are accepted.
Nine protections this repository can show, and two things it does not hide: your account and your download records are stored on our servers.
The gaps, in the words of what you cannot do yet, so you can judge the fit before you sign in.
There is no installer to download yet. What exists is a test bench, not a product client.
Installing, enabling and loading a plugin work from the command line today. There is no store or marketplace yet.
You cannot hand a plugin to anyone else yet. The step that publishes it stays off until an owner turns it on.
You cannot pay for a team plan yet. There is no checkout, and no price per person to buy.
Every answer is made by a model outside your computer, reached over the internet. Nothing runs on the machine itself yet.
New mail does not arrive on its own. You open the mailbox and refresh to see what came in.
Signing out does not yet cancel a pass that was already handed out. A device holding a copy can stay signed in.
The Kakaotalk connection exists in name only. Sending or reading a message through it fails.
The router is still catching up with the behaviour it replaces. Some requests work, some only partly, and some are not there at all.
Short answers, with the state of the product where it matters.
One assistant that reads your mail, drafts the reply, and edits the file for you. It works across the mail and chats you already use, it runs on your own computer, and it asks before it changes anything.
The part that does the work runs on your computer, next to your files. Only the model call leaves the machine, over the internet, to the provider you set up. The web app is this site and the console behind sign-in. The phone app is a shell that does not reach a server yet, and the desktop build is a test bench with no installer to download.
Nowhere. They stay where they are and are read in place. Your account is the one thing that lives on our servers: the sign-in, session, and passkey records are stored in our own storage on horon.ai, and your files are not part of it.
Writing and sending are two separate steps. It can write the reply and leave it as a draft you read first, and sending is a step it has to be asked to take. Anything that changes something waits for your answer.
Three prices are published: $0, $12 a month, and $20 a seat a month. You cannot pay yet, because checkout is not built, so today you use the free plan at no cost.
There is no desktop installer yet; what exists is a test bench. Plugins install, turn on, and load from the command line today, but there is no store or marketplace to browse. Team billing has no checkout and no seat to buy. New mail does not arrive on its own; you refresh the mailbox to see what came in.
Yes. The model runs outside your computer, on the provider account you set up, and the accounts and keys for each service stay on your machine in Router. Nothing runs on the device itself today.
Not yet. There is no seat to buy, no checkout to pay through, and nothing on our side that can take a team payment. The Team price is advertised, and nobody can pay for it yet.
Free covers the web app and the assistant on your computer. Three prices are published, and checkout is not built yet.
Prices are advertised, not billed. Checkout is not built yet.
See what each plan includesSign in, ask for one thing, and answer the permission request when it arrives. The free plan is enough to start, and that step waits until you answer.
Create your account