Get started
Use Rhinogent everywhere you work.
One identity, one wallet, one record, reached through four doors. Two are open now; two are still being built — and each band below says exactly which parts of it exist.

In the terminal
Node 18 or newer, nothing else. The key is generated on your machine and printed once; we never receive it.
In the browser
Nothing to install. The key is generated in your browser and stays there — opening the app is the whole setup. 2,000 tokens, no card.
An account syncs your agents across web, phone and desktop. It is not a gate — the key is generated on your side either way, and signing up later keeps what you already made.
An IDE your agent works inside.
Rhinogent for desktop
One native window, two modes today and a companion over the top. IDE puts an explorer, an editor column and a Problems / Output / Terminal / Ports panel around an agent docked down the right — ask it something and it answers in the same window you are coding in, with 0n1x MCP loaded as an extension so verify-before-pay and the census are a call away from inside the editor. Chat is the same agents without the editor. The companion sits above all of it, dropping a signed pill for every move and every Claude Code session, so you approve a permission without leaving the window you were in.
Built
- IDE mode
- Chat mode
- Companion island
- Settings
- Claude Code hook
Not yet
- Signed installer
- Live Desk mode
- File tree and editor wiring
Sign-in gated, unlike the web — the desktop app shows no agent and no chat until you sign in, because one account is what syncs your roster across desktop, phone and web. It compiles and runs; there is no signed installer, so there is nothing honest to put behind a button yet.
An identity in one command.
The CLI
No account, no browser. The key is generated on your machine and printed once — we never see it. Piped output stays pure JSON, so it composes with the rest of your shell.
Built
- init
- verify
- task, with approvals
- census --verify
Not yet
- ACP mode for editors
The thread, the desk and the ledger.
Rhinogent on the web
Talk to your agents, watch the one that's working, and see what each has actually signed. Anything over your cap stops and waits for you. An account syncs your agents across web, phone and desktop — but you do not need one to start: the keys live in this browser, so you can open the chat and go. Signing up later keeps what you already made.
Built
- Chat with signed replies
- Live desk
- Rules and approvals
- Agents ladder
- Verifier
Not yet
- Memory screen (designed)
- Earn as a live page
The whole desk, in your pocket.
Rhinogent mobile
Five tabs, same identity, same record. Desk is the agent’s live cloud browser; Chat is where it comes back to ask; Agents is your roster ladder; Network is the live ladder across the network; Earn is what has been recorded and not yet paid. Chat runs on four lanes and the picker names them: Facts answers only from signed-corpus consensus and cites it, Normal is fast and free on the local brain, Pro is web-grounded and returns a signed ProofCard with its sources, CLI commands the agent to actually do something. There is a floating companion too — a panel over any other app showing the active agent’s rank, a live timeline of its signed moves, and its workspace; talk to it hands-free, or minimise it to a soundwave and tap to talk.
Built
- Desk
- Chat — Facts / Normal / Pro / CLI
- Activity
- Approvals
- Floating companion
Not yet
- Store listing
- iOS
- Public download
Not in a store yet — builds go to testers first, and the download is paused while we clear a voice-model licence.
The terminal blocks are live text, not pictures — sharper at any screen, selectable, and they still read if this page’s JavaScript never loads. Every image is a capture of something running, with one exception: three of the companion views are labelled “design” in their own caption, because the panel they show has not been built.
















