The rhema framework is still in active development. Expect things to break.
download · rhema code

Get Rhema Code

The rhema binary: a full terminal coding agent, a pipeable one-shot, and an Agent Client Protocol server. No registries, no plugins.

sh
$ curl -fsSL https://get.rhema.rs/code | sh

Then run rhema inside any project directory.

01 · what you get

One binary, three ways to run it

Whatever you point it at, the agent underneath is the same approval-gated, session-saving coding agent.

terminal

rhema opens the full-screen TUI. Replies stream in as rendered markdown, every tool call is a shell command shown with its exit code, and sessions save under the cache dir for /resume.

your editor

rhema acp speaks the Agent Client Protocol: T3 Code, Zed, JetBrains, Neovim, Emacs, and VS Code launch it as a subprocess. No plugin per editor.

one-shot

rhema run "summarize this diff" for scripts. Prompt on stdin, plain text on stdout, tool events on stderr, non-zero exit on failure.

02 · from source

Build it yourself

The workspace is 18 crates, but the binary only needs crates/rhema-code. A current stable Rust toolchain (1.85+) and git are all it takes.

sh
$ git clone https://github.com/vhaudiquet/rhema
$ cd rhema
$ cargo install --locked --path crates/rhema-code

This installs the rhema binary into ~/.cargo/bin.

03 · after install

First run

Rhema Code ships with two default profiles, work and personal, each holding any number of provider instances. Login keys are stored in your system keychain whenever one is reachable: macOS Keychain, Windows Credential Manager, or the freedesktop Secret Service. Environment variables still outrank everything stored.

The system prompt the agent works from is editable in your $EDITOR: rhema system edit.

Rhema Claw, the resident agent daemon, is still work in progress. The workspace graph shows how all the crates fit together.