MIT-licensed · runs on your machine

Trading agents you never have to trust.

OpenRush is a bot you run yourself. Your keys stay on your laptop, and every spending cap is enforced by a smart contract on Rushline — not a promise in a privacy policy.

No account. No cloud. No custody.

telegram · #agent-desk
how are we doing?
Up 4.1% on the week. Basket strategy took profit on SOL at the top of the range. Nothing pending.
buy 200 of eth if it dips under 3.1k
That trade is inside your daily cap. Reply YES to arm the order, it will fire once, on the dip, or expire in 6h.
self-hosted ·on-chain permission wall ·the model proposes, the ledger disposes ·voice & vision ·kill switch ·open source · MIT ·self-hosted ·on-chain permission wall ·the model proposes, the ledger disposes ·voice & vision ·kill switch ·open source · MIT ·self-hosted ·on-chain permission wall ·the model proposes, the ledger disposes ·voice & vision ·kill switch ·open source · MIT ·
01

Your keys, your caps

The private key never leaves your machine. Spending limits live in a smart contract, not in a terms-of-service page.

02

Bounded worst case

Before OpenRush trades a cent, you set the ceiling. The worst day it can ever have is a number you chose in advance.

03

Every trade simulated

Nothing touches a live wallet until it has run clean in paper mode. Simulated fills, simulated slippage, real math.

04

Fees only on profit

No AUM tax, no monthly seat. OpenRush takes a cut of realized gains and nothing when it's flat or down.

05

An honest scoreboard

Rejected trades show up next to winning ones. The wall blocking a bad idea is not hidden from the log.

01 · The Trust Layer

The wall is the product.

The model proposes, deterministic code disposes. Every trade has to pass a closed command set and an on-chain policy wall before it settles. Anything touching your PC directly — reading a file, running a command — needs an explicit confirmation first, every time.

Platform-run agents

You trust; it trades.

Your keys sit on someone else's server. The cap is a number in a settings screen you can't verify from the outside.

OpenRush

You verify; it trades.

The cap is a contract call anyone can read on an explorer. If OpenRush tries to exceed it, the chain rejects the transaction, not a support ticket.

Try it yourself: the public dashboard lets you fire malicious commands at a live agent and watch the wall refuse them, live, with the transaction receipt underneath.

02 · What It Is

It works the graveyard shift so you don't have to.

Self-hosted

One install command. Everything lives in ~/.openrush.

~/.openrush
├── settings.json
├── grant.json
├── openrush.db
├── strategies/
└── memory/

Remote PC control

Screenshots, an allow-listed shell, and reminders — all off by default and confirm-gated when enabled.

is the test suite still red on main?
Yes — 2 failures in payments.test.ts. Run npm test -- payments now?

Memory

Every agent keeps a small set of markdown files — IDENTITY.md, OWNER.md, JOURNAL.md — that it writes to as it trades. Name it once. A trader nicknamed "Vega" on our test fleet has been running the same basket strategy for 214 days straight.

03 · The Toolkit

Nine parts, one wall.

LLM strategist

A language model reads the market and proposes moves. It never sees your seed phrase or wallet address — only tickers and balances.

Built-in strategies

Ships with a steady-basket DCA and a weekend-gap play out of the box, both editable in plain config.

On-chain caps

Daily and per-trade limits are enforced by a contract on Rushline, the chain OpenRush settles through. Not a setting — a receipt.

Trade simulation

A shadow ledger runs every proposed trade first. If it would have lost money last month, you see that before it runs live.

Chat-based transfers

Move funds between wallets by asking in plain language. Every transfer still needs your explicit confirmation.

Honest scoreboard

Win rate, drawdown, and every trade the wall refused — all in one log you can screenshot without editing.

Proactive alerts

OpenRush pings you first when a position moves against plan, not the other way around.

Voice & vision

Send a voice note or a screenshot. OpenRush transcribes, reads the chart, and answers in the same thread.

Kill switch

One command halts every open strategy and cancels pending orders. No dashboard hunting required.

04 · Quickstart

Paper first. Live when you say so.

1

Install

One command, no Docker, Node 22.12+, cross-platform.

2

Create an agent

Starts in paper mode automatically. Trades simulated fills only.

3

Add a key

When you trust the log, add a funded wallet and set the cap.

05 · Telegram Setup

Four steps to a linked bot.

1

Open BotFather

Message @BotFather on Telegram and run /newbot to mint a bot token for your agent.

2

Paste the token

Drop the token into settings.json under telegram.token. OpenRush picks it up on next start.

3

Link your account

DM your new bot /link and it replies with a one-time code. Enter that code once in the OpenRush CLI.

4

Check status

Send /status any time for balances, open positions, and the last five decisions the wall made.

"The on-chain permission wall is good — smart."

— an early code reviewer, unprompted

MIT open source230+ testsexplorer-verifiable capszero servers

$OPENRUSH

The token that funds the wall.

$OPENRUSH is launching on Rushline through Virtuals. The contract address will be posted here the moment it deploys — verify it against the explorer before you trade, and never trust a contract address you saw anywhere else first.

Contract address

pending deployment — check back soon

Launch on Virtuals

Get to it.