rind
中GitHub Get rind

Light by design.
Open by nature.

A local coding agent with room for your ideas. Automate it, delegate to it, extend it. Make it yours.

Start buildingSee it in action
$npm i -g @rind-ai/cli
A small core. An open world.
LOCAL FIRST. OPEN SOURCE.
On your machineWith your modelsOn your terms
01 / THE RIND WAY

Less between you
and your next idea.

A capable agent doesn’t need to be a heavy one. Rind keeps the core small and the possibilities open — so the way you work stays yours.

A CLI that shows you how.

Explore guided, simulated workflows inside the terminal. Learn commands, shortcuts, and teams before making a single model call.

Built-in user guide

A team that keeps its work.

Give each specialist a role and a stateful directory. Instructions, memory notes, working files, and deliverables persist across assignments.

Persistent teams

A good citizen of your shell.

Use one-shot runs in hooks, CI, or scheduled reviews. Let a test watcher send failures into a live session. Ordinary commands, useful automation.

Programmable sessions
02 / INSIDE THE TERMINALCLI simulation · automatic loop · no model calls

A proper CLI.
A warmer welcome.

See Rind at work in your terminal. Explore the built-in guide, create a team, or put an agent in your scripts.

rind — Terminal
~/demo $ rind
┌────────────────────────────────┐
│ Rind v0.8.0 │
│ model zai/glm-4.7 · session... │
│ ~/demo │
└────────────────────────────────┘
zai/glm-4.7 · high · ~/demo
enter send · ↑↓ history · /...
──────────────────────────────────
▷ Ask Rind to do anything

Your project. Your terminal. Rind.

Describe what you need and follow the work as it happens: reading files, making edits, and running tests. Keep the conversation going from the same command line.

Follow a task from the first prompt to a passing test run. Check the changed file, read the result, and keep working in the same session.

Rind CLI · simulated tasks · Mocha theme
Try it in your terminalrindTour is available from source on main.
03 / A SMALL, REUSABLE CORE

An engine,
not an empire.

Keep the design restrained. Make the essentials robust. The interface handles interaction; a small, reusable worker handles execution across a clear process boundary.

  1. 01

    Load when needed.

    A turn opens its session and creates the execution objects it needs.

  2. 02

    Let go when idle.

    When active and queued work is done, the session’s execution container is released.

  3. 03

    Keep the work.

    Session history lives on disk. The next turn picks it up again.

Explore the architecture
CHOOSE A SURFACE
Node.js surface · JSONL
requests ↓   ↑ events

One lean worker

Models · tools · delegation

Session historyOn disk. Ready for the next turn.
INTERFACES CHANGE. THE CORE STAYS.
04 / MORE THAN ONE WAY IN

Your work.
Your way in.

The same execution core, through the interface that suits the moment.

01

CLI

A guided terminal experience, persistent teams, and scriptable commands.

02

Desktop

A visual workspace for working across multiple projects.

03

Web

Connect through a browser. Close the tab; the worker keeps running.

04

Gateway

Reach the agent through Telegram, Discord, Slack, Feishu, and other messaging adapters.

05 / YOUR NEXT IDEA STARTS HERE

Make room
for possibility.

Bring a project. Pick your model. Go from there.

Node.js 18+ · Windows, macOS & Linux

npm install -g @rind-ai/cli
cd your-project
rind

Inside Rind, use /login to connect a provider, then /model to choose a model.