                \||/
                |  @___oo
      /\  /\   / (__,,,,|
     ) /^\) ^\/ _)
     )   /^\/   _)
     )   _ /  / _)
 /\  )/\/ ||  | )_)
<  >      |(,,) )__)
 ||      /    \)___)\
 | \____(      )___) )___
  \______(_______;;; __;;;

A small terminal agent for local LLMs.

One Go binary, no runtime, no server. Point it at Ollama, LM Studio, llama.cpp, vLLM, OpenRouter — anything that speaks the OpenAI /v1/chat/completions format. It reads and writes files, runs commands, and keeps the conversation where you can see it.

curl -fsSL https://raw.githubusercontent.com/devjasha/raunen/main/install.sh | sh

macOS and Linux, Intel and ARM · verified against the release checksums · about 3 MB · free to run

~/Projects/raunen

  ──────────────────────────────────────────────────────── 10:42
  ▌ what does main.go do?

    ⏺ read  main.go
      ↳ 84 lines

  It parses flags, loads the config, and starts either the TUI or a
  single one-shot turn.

  • --continue resumes the last session for the directory
  • a prompt as an argument skips the UI entirely

  ╭────────────────────────────────────────────────────────────╮
  │ ›                                                          │
  ╰────────────────────────────────────────────────────────────╯
  auto · ⎇ main · qwen3.5-8k:latest · ██░░░░░░░░ 22% · 1.8k

What it is

An agent that works in the directory you start it in. Tools are rooted there, so raunen in a project is what gives it something to read. There is no separate window and no web UI — a running agent has nowhere else to put things.

Any endpoint

Adding a provider is a base URL, not adapter code — they all speak the same wire format.

Five tools

read, write, edit, list, bash — plus anything an MCP server brings along.

Three modes

tab cycles auto, accept edits and plan. The mode goes into the system prompt, so the model knows the rules.

Sub-agents

Investigation is delegated to a sub-agent with its own empty context, which returns only its answer. Several run at once.

Sessions

The conversation is saved per directory. raunen --continue picks it back up tomorrow.

Visible context

A bar in the status row, because running out of room is the most common cause of a bad answer.

Local first, hosted when it matters

Everything runs on the local model — free, unmetered, private — until a conversation outgrows its window, at which point it moves to a roomier one without dropping anything it has already found.

That is the whole design in one exchange: cheapest thing that works, a bigger one only when the work demands it, and no memory lost in between.

What it costs to run →

escalation

auto · ⎇ main · qwen3.5-8k:latest

    ⏺ read  README.md          ↳ 210 lines
    ⏺ read  internal/ui/ui.go  ↳ 196 lines

  The UI is a terminal user interface that takes
  the alternate screen …

    ⇅ switched to omniroute/auto/best-coding
      — context full at 8192 tokens

auto · ⎇ main · auto/best-coding · ░░░░░░░░░░ 0% · 5.9k

The dashboard is in the conversation

/status answers the questions that otherwise need guessing: whether an endpoint is actually up, which ones are missing a key, how close the context is to full, and what the agent will switch to when it runs out of room.

Everything known locally appears at once and the endpoints fill in as they answer, because a report you have to wait for is a worse report.

/status

─────────────────────────────────────────── status
  version   v0.1.0
  model     ollama/qwen3.5-8k:latest  ·  8192
  mode      auto
  context   940 of 8.2k  (11%)
  ladder    18 models
  subagents on
  providers ollama      3 models     :11434
            lmstudio    unreachable  :1234
            openrouter  411 models   needs key

                \||/
                |  @___oo
      /\  /\   / (__,,,,|
     ) /^\) ^\/ _)
     )   /^\/   _)
     )   _ /  / _)
 /\  )/\/ ||  | )_)
<  >      |(,,) )__)
 ||      /    \)___)\
 | \____(      )___) )___
  \______(_______;;; __;;;

Levels you actually earn

The dragon is not decoration: it grows on the one thing every provider charges in, which is context. Feed it enough — across every model, every session — and you climb from a quiet Hush to a roaring Thunder.

It is yours, not a model's, and it carries forward between sessions, so the work you put in shows up next time you open raunen.

How levels work →

1Hush

2Whisper

3Murmur

4Rumour

5Echo

6Chant

7Chorus

8Bellow

9Roar

10Thunder

Getting started

Three steps, and the third one is asking it something.

shell

# 1. have a model to talk to — anything speaking the OpenAI API
$ ollama pull qwen3.5

# 2. run it in the directory you want to work in
$ cd ~/Projects/my-thing
$ raunen

raunen: no default model set, using ollama/qwen3.5:latest

# 3. ask it something. /help lists everything, ctrl+c leaves.

The first run writes ~/.config/raunen/config.json and, since no model is configured yet, asks your endpoints what they have and picks one — preferring anything local. Read the docs or the full README.