niobe v0.13.0

niobe 0.13.0

The transcript now shows what the agent did in the detail you would check it in: the lines it changed, what each call cost, the tests it ran and what every turn spent. And you can stop it, point it at files and run commands of your own without leaving the shell.

What the agent did

• File changes are drawn as the lines that changed, under the call that made them. A long diff is cut at twenty rows; Ctrl+T opens every cut diff in place.
• Each tool call is a row of a table: its name, what it did, which sub-agent made it, and on the right what it cost and how long it took. A run of calls to one tool folds into one group with Ctrl+O. A call a standing rule allowed says so on its row.
• Test runs are read. When the agent runs cargo test, the counts appear under the call, including the names of failing tests, and a run the CLI cut short or saved to a file is counted from what survived or from that file. A run whose output was cut and shows no count is still marked failed when it failed.
• Sub-agents are named on every call and message they made, and a sub-agent's own calls, edits, model and tokens are part of the session, including in a session read back from Claude Code's own files. A permission prompt from a sub-agent says which one is asking.
• The Working tree section lists files git does not track yet, marked new, rather than showing +0 −0 beside them. Per-file +/− counts agree with git diff --numstat, including for line endings, final newlines and binary files.

What it cost

• Every finished turn is ruled off with its tokens, how far it moved the five-hour window and how long it took.
• A context meter shows how full the context window is, where that can be measured, and is left out where it cannot.
• Where the account is billed by use, the Usage pane leads with money and shows what the session spends per hour worked. On a subscription plan, a cost figure is labelled API-equivalent; where niobe cannot tell how the account is billed, it shows no cost at all rather than guess.
• Many figures are now right that were not: a resumed session's first turn no longer bills the whole earlier session again; the 1M context window, fast mode and /clear are priced as the CLI reports them; a turn with no reported usage shows a dash, not 0 tok; and very large counters draw as figures instead of overflowing.

Steering the session

• Esc or Ctrl+C stops a running turn and keeps the session. A second Ctrl+C quits.
• @ names a file in your prompt, completed from the files git lists. A path with a space goes in quoted, as Claude Code reads it.
• / searches the transcript; // offers the backend's own slash commands.
• ! runs a command of your own from the ask bar. It runs in a session of its own, so it cannot draw over the shell, and Ctrl+G stops it without ending the session.
• Shift+Enter opens a new line on terminals that can report it, including under tmux; Ctrl+J does on every terminal. A multi-line paste is one prompt, and an Enter inside a paste is a line break, never a send.
• Esc and a digit press the F-key the bar names, and the bar's badge names the mode.
• One pane has the keyboard at a time, and a transcript you have scrolled back in offers the way down.

Looks

• Designed themes draw in their own colours on a truecolor terminal; NO_COLOR draws the sixteen ANSI colours.
• While a turn runs, the desktop behind the panes moves: rain, drifting words or a radar, depending on the theme. effects = false in your config keeps it still.
• The session pane is captioned with what the session is about, and markdown links, images and footnotes in replies are drawn.

Safer and sturdier

• A repository's config that you have not trusted can no longer decide how the account is billed, answer permission prompts, or be read through a link that leads outside the repository. A trusted config stays trusted only for the exact text you trusted.
• A * rule no longer covers a command chained after the one it allows, and a rule for a command does not cover running it outside the sandbox.
• Nothing a session starts outlives it, even if niobe is killed outright. The terminal is handed back on SIGINT, SIGQUIT and Ctrl+Z, and redrawn when you continue.
• Quitting no longer hangs on something the CLI started, and a CLI that is not reading its input no longer freezes the screen.
• The session store is readable by you alone, and two niobe processes cannot record the same session at once.
• The installer fails and says why when it could not install a working niobe.