An ops terminal that remembers the team, the spend, and the decision.

Why forked from opencode

Upstream opencode is a fine terminal shell, but it remembers nothing, knows no team, and controls no cost. We verified each gap before forking, and the fork adds exactly the missing pieces:

• Tools never reached the agent. The planning endpoint did not forward tool calls, so an agent would call a tool it does not have and stall.
• Caps cut real work. Replies were capped at 4,000 tokens with history flattened to a dozen trimmed messages.
• Hangs and waste. opencode run hangs with open stdin, and a casual turn burned about 14,000 tokens with no ledger to show for it.
• Sign-in with riif. Device keys tie every turn to a person and their credit, instead of a pasted API key in a dotfile.
• A cost ledger with routing. Every call is logged with what it cost, and cheap turns route to cheap models.
• A record the team can check. Decisions land in the immutable riif record, and standup runs on HOLDS the team pools together.
• Voice-dump intake. Speak a dump, it sorts on your confirm, briefs you back, runs, and records.

Install

The command is reflex. opencode still works as an alias. One line detects your machine (Mac, Linux, Intel with baseline fallback) and installs both:

curl -fsSL https://reflex.riif.com/install | bash

reflex --help   # prints REFLEX OPS
reflex          # opens the terminal

Prefer to build it yourself? You need Bun and the public repository:

git clone https://github.com/paragonreflex/reflex-ops.git
cd reflex-ops
bun install
cd packages/opencode
bun run script/build.ts --single --skip-install
cp dist/opencode-darwin-arm64/bin/opencode ~/.local/bin/reflex

On Linux or Intel Macs the binary name matches your platform (for example dist/opencode-linux-x64/bin/opencode).

First standup in five steps

1. Sign in once: reflex login shows a code, you approve it on account.riif.com (new users pick a username there), and Reflex Agent becomes your default model.
2. Open a folder and type reflex. The terminal opens on that folder.
3. Pick an agent: build executes with full access, plan reads and analyses without touching files.
4. Pool the team's items and run the agenda: standup runs on HOLDS, and the word is UNBLOCK.
5. Voice dump: speak, it sorts on your confirm, briefs you back, runs, and records.
6. Check the record and the cost ledger: what was decided, and what each call cost.

Keep going at riif.com/team: daily standup and agent coordination live there, with the record beside them.

Knowledge base

Short pages, each one job. The living docs stay where the team works:

• Standup and HOLDS/UNBLOCK, operating rules, and agent handoffs (build, plan, @general) live at riif.com/team.
• Person-facing workspaces and records live at riif.com.
• Experiments, A/B tests, and rollout checks live at testing.riif.com.

Ask Haven

Haven answers setup questions here. Fixed questions only; there is no open voice box on this page.

Honest limits

• Free-model tiers may train on prompts. Secrets go to paid tiers.
• It runs on your machine. We do not host your runs.
• The fork is young. Commands and record formats may change.
• Voice dump sorts on your confirm. Check before it runs and records.
• The ledger records what was spent. It does not cap spend by itself.
• Support answers here are fixed. Hard cases go to standup at riif.com/team.

Sign in and key

Sign in with riif on your device. The first device gets a $5 starter credit, and credit, usage, and devices live in your account dashboard.

NOT YET: one-command device pairing from inside reflex. Until it ships, sign in on the web, then add the device key.

More from riif

Reflex Ops runs the turn. riif keeps the record of who stood behind a change and why.

riif.com/team: daily standup and agent coordination.
riif.com: rooms, rules, the record.