Open Source · Zero Dependencies
SAGE
Session Awareness & Guidance Engine

I don't do the work.

I judge it.

A passive, read-only judge for fleets of parallel AI coding sessions. One judge per repo.

↳ watches everything, changes nothing
View on GitHub →
⎘ $ npm install -g agentic-sage
sage — fleet judge
// problem

Eight agents,
one repo,
zero coordination.

Run a fleet of coding agents at once and they collide — same files, duplicated work, lost context across sessions, no shared source of truth. Nobody is watching the fleet as a whole.

↑ sound familiar?
fleet.log — unmonitored
ERR agent-3 & agent-7 modified src/auth/session.ts simultaneously
ERR merge conflict: 14 files — 3 sessions diverged
WRN agent-2 regenerating work already done by agent-5
WRN no shared context — each session is flying blind
?  who is watching the fleet as a whole?
// what sage is —

A judge, not a boss.

SAGE sits beside your fleet and watches every session. Ask it anything — who's touching what, where two branches diverged, what the backlog says — and it answers.

It never edits your code, never spawns agents, never blocks an action. Passive by design.

sage.d.ts
/**
* @passive — watches, never edits
* @readonly — cannot change your repo. ever.
* @zero-deps— one Node CLI, nothing else
* @default-off— nothing until sage on
* @fail-open— errors allow, never block
*/
export default SAGE;
SAGE mascot — robed sage with sunglasses and staff
// how it works

Four commands. Done.

setup
$ npm install -g agentic-sage
#1 Install globally
$ sage init
#2 Wire into ~/.claude — installs DISABLED
$ sage on
#3 Enable — nothing runs until you do this
$ sage doctor
#4 Verify your setup is valid
✓ sage is watching
SAGE easy setup: three steps — Install (npm install -g agentic-sage), Wire (sage init), Enable (sage on)
// session communication
NEW · live judge

CLI works out of the box.
Go further with a living judge.

Once configured, you already benefit from SAGE — every coding session can orient itself around the others through the CLI. That’s layer 1. Layer 2 is optional: start a passive judge pane in the background, and those same CLI answers become a real AI judge.

Layer 1 · always on after install + sage on

Sensor CLI

Deterministic facts only — who is live, who claims which paths, why branches diverged. Sessions use board, territory, merge-brief and orient around each other. No extra pane required.

worker session
$ sage territory 'src/auth/**'
clear — no other live claim
$ sage merge-brief
facts only · contested paths listed
Layer 2 · optional one background pane

Living judge

Start a passive agent session that watches the fleet and publishes short briefs into the same store. Workers keep the same CLI verbs — but answers gain narrative and per-audience advice. That’s what makes the CLI an actual AI judge.

desk · judge pane
$ sage judge run
# auto scope · watches in the background
⚖ live · briefs layer onto territory / merge-brief
the easy convention
// out of the box
$ sage on
Sessions already orient around each other via the CLI. Collision awareness works. You already benefit.
// go further
$ sage judge run
One passive watcher. Same store, same verbs — now with a living AI judge behind the answers.
Facts stay authoritative · briefs layer when fresh · no second protocol Live judge recipe →
↳ install once · elevate when the desk gets busy
// six pillars —

Built on six hard rules.

sage doctor — principles check
✓ passive by design — watches; never edits
✓ read-only & safe — cannot change your repo. ever.
✓ zero-dependency — one Node CLI, no bloat
✓ default-off — nothing until `sage on`
✓ fail-open — errors allow, never block
✓ hot-path-cheap — idle = instant exit
all checks passed ✓
↑ real output from sage doctor
// 01
Passive by design

Watches and answers. Never edits, spawns, or blocks. Your fleet keeps moving; SAGE keeps score.

// 02
Read-only & safe

It cannot change your repo. Ever. No hooks that write, no side effects, no surprises.

sworn to read
// 03
Zero-dependency

One Node CLI, no install bloat. Clone and run. Your package.json stays untouched.

// 04
Default-off

Installing changes nothing until sage on. Try it without committing to it.

// 05
Fail-open

Any error in the optional guard allows the action through. SAGE is never in your way — even broken.

// 06
Hot-path-cheap

When idle the hook short-circuits instantly. Zero cost on the commits that matter most.

literally free when idle
// a peek —

Ask anything about your fleet.

sage — commands
$ sage — live demo
$
// the judge
SAGE mascot — a robed sage with sunglasses and a staff, with the motto: I DON'T DO THE WORK. I JUDGE IT.

the sage sees all  ·  the sage judges all

// bring a judge to your fleet

Bring a judge
to your fleet.

MIT · zero dependencies · one judge per repo

View on GitHub →
⎘ $ npm install -g agentic-sage
A note from the creator

SAGE is in beta — early, active development. It works (I run it daily), but expect rough edges, and expect things to change as it finds its shape.

I'm building it in the open, and I'd genuinely love to hear from you. A bug, a question, a half-formed idea, or just hello — any form of contact is welcome. Nothing is too small.

✉ kontakt@muslewski.com ⎘
↗ open an issue on GitHub
~ Mateusz