01 / See the work
Every read, edit and command, as it happensThe session pane is the running record: the files opened, the diffs applied, the commands run and what they exited with, the sub-agents still going. Watch it, or read it after.
Open source · Apache-2.0 · v0.4.0
AI coding at full speed.
Without the black box.
Niobe is a terminal coding agent that keeps you aware of what is being built and how: what it did, what it decided, what it touched, what it is doing right now and what it cost — visible while it happens. You stay on the loop instead of in it.
$curl -fsSL https://niobe.dev/install.sh | sh- Drives the
claudeCLI - macOS · Linux
- Single static binary
- Apache-2.0
- No telemetry
Session ─ niobe
> you · 14:02add etag support to the catalog fetcher so we stop re-downloading manifests that have not changed
◆ claude · opus-5 · 14:03 · $0.19 API-equivalentKeeping the etag per URL in the LRU the fetcher already has, sending If-None-Match, and treating a 304 as a cache hit. fetch_manifest keeps its signature.
⚙ Edit · catalog/fetch.rs · +38 −9
⚙ Bash · cargo test -p catalog · 4.2s · exit 011 passed
the turn is waiting on you
Bash wants to run
“cargo clippy --workspace --all-targets”
Yes, onceAlways Bash(cargo clippy *)Pin thisNo
y allow · n deny · a always · p this target
›now do the same for the image proxy
Cost
session$1.84
tokens in412k
tokens out18k
cache read1.3M
14 calls · 0 failed · 1 denied · 26 kB out
Parallel ─ 2 running
◆ tests for the 304 path
◆ review catalog/cache.rs
3 spawned · peak 2 · 1 done · 0 failed
Changes
Files ─ 3
▸ catalog/fetch.rs+38 −9
“etag kept in the LRU the fetcher had”
▸ catalog/cache.rs+6 −2
▸ tests/fetch.rs+41 —
Decisions ─ 3
· reused the existing LRU rather than a second map, to keep one eviction policy
· kept fetch_manifest's signature; the etag is internal
· left the image proxy alone — asked first
niobe│claude · opus-5│⎇ main│430k tokens│1 waiting on you│budget $1.84/$5.00
▸▸ ask mode · Shift+Tab cycles · F8 model · Enter send · F10 quit
1Help2Plan3Diff4Undo5Cost6Files7Tools8Model9Theme10Quitniobe v0.4.0
The shell as it draws itself. The session in it is an illustration — in a real one every figure on screen is measured, or says what it is instead.
The idea
Full speed.
Full awareness.
An agent that works out of sight asks you to take its word for everything, and the only way back into the loop is to approve every step — which costs you the speed you came for. Niobe shows the work instead: the calls, the reasons, the files, the bill. Control comes from seeing clearly, so it is built in rather than bolted on.
02 / See the why
The reasons beside the diffChanged files carry the reason they were changed, and the decisions pane keeps what was chosen and what was deliberately left alone. Review the reasoning as fast as the code.
03 / See the cost
Every figure measured, or labelledTokens in, out and read from cache, priced from a dated table bundled with the binary. A number the backend reported is marked API-equivalent; a model the table does not list reads unpriced. Nothing is guessed.
04 / Stay in charge
Permissions you answer onceStop for every call, stop for none, or plan without touching anything. An “always” answer becomes a rule in the repository's config, and answers the same prompt in every session after.
Read and reason, change nothing
planThe backend works through the problem and proposes. Nothing is applied.
Shift+Tab cycles
askEvery call no rule already allows stops for you. y, n, a for always, p for this target.
When you trust the run
autoThe backend decides. The session pane still shows every call it made.
Bridge-first
Your subscription, untouched.
Niobe drives the official claude CLI as a subprocess, with your repository as its working directory. Whatever that binary is signed in as is what the session runs on — there is no key to paste and no second place your credentials live.
- Only the official binaries touch credentials.Niobe never reads their token files and never sets their user agent. No extraction, no spoofing.
- No telemetry.Network calls go to the configured provider and to the CLIs. Nothing else, ever.
- Your sessions stay yours.Every event is recorded append-only into
.niobe/sessions.dbin the repository, and a session started in plain Claude Code can be carried on here. - The codex bridge and the native agent loop do not spawn a process yet; a session under one of those profiles has nowhere to send a prompt, and says so.
Jacked in
in sixty seconds.
One static binary, no runtime, nothing to sign up for. The installer checks the archive against its published SHA-256, puts niobe in ~/.local/bin, and edits none of your shell files.
$curl -fsSL https://niobe.dev/install.sh | sh
$cd my-project
$niobe
Releases
All releases →19 September 2026niobe v0.4.0**Full Changelog**: https://github.com/niobe-dev/niobe/compare/v0.3.0...v0.4.019 September 2026niobe v0.3.0**Full Changelog**: https://github.com/niobe-dev/niobe/compare/v0.2.0...v0.3.019 September 2026niobe v0.2.0**Full Changelog**: https://github.com/niobe-dev/niobe/compare/v0.1.0...v0.2.0