ribhuऋभु

A coding agent / a visible record

KNOW THE CODE.
SHOW THE PROOF.

A terminal coding agent built around a simple promise: know the project, make the change, show what happened.

Pull up a chair Meet Ribhu

A shokunin’s bench. A Vedic engine.
Powered by Chitragupta. Built by Srinivas.

RIBHU / WORK RECORDILLUSTRATIVE RECORD
THE REQUEST

Handle empty input.
Keep the public API.

  1. 01 / READParser + callers inspected
  2. 02 / EDITOne bounded change
  3. 03 / CHECKRegression test passed
RECEIPTWhat ran. What changed.
What remains unknown.

Illustrative walkthrough · no commands run here

TSUGITE — THE VISIBLE JOIN

The seam is the feature.

The project is the block. The change is the fitted piece. The gold is visible proof—not a way to hide the join.

ILLUSTRATIVE MODEL / PROOF SHOWNNOT AN EXECUTION RECEIPT

THE BLOCKYour project.

THE FITTED PIECEThe change.

THE GOLD SEAMThe proof.

One mark.
An operating principle.

01 / THE WORKBENCH

A calm surface.
Serious work underneath.

Read the code. Make the change. Check what happened. Ribhu brings the tools and the decisions into one terminal—without pretending that a convincing answer is a finished job.

ribhu / example-projectILLUSTRATIVE WALKTHROUGH · NO COMMANDS RUN

THE REQUEST

“Handle empty input.
Keep the public API unchanged.”

// Begin with the project, not an assumption.
read       → inspect the existing parser
grep       → find its callers and tests
code_query → ask the language server

⊐ Context before changes.
EXAMPLE, NOT A LIVE SESSIONRUST / TERMINAL-NATIVE

Focused tools. Deliberate approvals. Inspectable records.Read the field guide

02 / WHAT HOLDS THE WORK TOGETHER

What makes
the join hold.

Three distinct mechanisms make Ribhu’s work inspectable: a boundary before execution, an independent review after a change, and a record that survives the session.

01 / BOUNDARY

Permission has a boundary.

New workspaces start untrusted. Project instructions, extensions and execution-capable analysis are gated. Trust is deliberate; it doesn’t imply every shell command is sandboxed.

Explore workspace trust
02 / WITNESS

A separate set of eyes.

A fresh, read-only witness reviews the request, diff and checks. It doesn’t inherit the author’s whole conversation. An inconclusive review stays visible.

Meet the witness
03 / RECEIPT

A record you can verify.

Turn receipts record tools, outcomes and file digests. You can verify the record and compare the files. The receipt proves what happened, not whether the answer was right.

Inspect a turn receipt

03 / THE BENCH & THE ENGINE

One craft.
Clear ownership.

Ribhu is where the work happens. Chitragupta keeps the sessions, routes, memory and credentials behind it. A local socket carries each request across the seam.

SECTION 03 / A LOCAL JOINONE MACHINE · TWO PROCESSES
01 / WORKING SURFACE

Ribhu

The terminal, tools and approvals. Work stays visible here.

COMMANDSTOOLSWORKSPACE APPROVALS
REQUEST→
←REPLY
LOCAL UNIX SOCKET
02 / AUTHORITY PROCESS

Chitragupta

The durable decisions: routing, identity and memory.

ROUTINGSESSIONS & MEMORYGRANTS