Skip to content
Public CLI · local-first · filesystem-backed

The agentic dev loop, run as infrastructure.

Night Loop is a spec-first project operating system in a synthwave TUI — tasks, work sessions, specs, delivery metrics, and operational risk in one terminal surface. Every session logged, every task traceable.

Surface
Terminal UI
State
Filesystem-backed
Sessions
Logged & traceable
Risk
Scored operationally
night-loop · work session · TASK-042 IN SESSION
SESSION LOG
session.startTASK-042 · spec attached
context.loadspec + 3 linked files
work.block47m focused · 2 interruptions
insight.flagreview debt rising on module B
session.closenotes → delivery metrics updated
boardtasks · lifecycle states
specsattached to every task
metricsdelivery + review intelligence
riskoperational score per project
01 · The fragmentation tax

Agentic development scatters
across every surface you own.

Tasks in one tool, specs in another, sessions in terminal scrollback, decisions in chat. The work happens — the operational picture never exists.

01
Untracked sessions

Hours of agent-assisted work leave no record of what was attempted, decided, or abandoned.

02
Specs adrift

The spec lives in a doc; the task lives in a board; the code lives in a branch. Nothing links them.

03
Invisible risk

Review debt, stalled tasks, and scope drift accumulate silently until they become the sprint.

04
No delivery signal

"How is the project actually going?" has no honest answer without leaving the terminal to assemble one.

02 · One surface, all signal

Specs, sessions, and risk —
without leaving the terminal.

Night Loop treats the dev loop itself as a system to operate: structured tasks with specs attached, logged work sessions, and live operational health — all local, all filesystem-backed.

A.
Spec-first tasks

Every task carries its spec and context. Work starts from intent, not from a blank prompt.

B.
Logged work sessions

Sessions are first-class: started, focused, interrupted, closed — with notes that feed the metrics.

C.
Operational insight

Delivery metrics, review intelligence, and risk scoring turn activity into an honest health signal.

D.
Local and inspectable

State is files on your machine. No account, no sync service, no dashboard SaaS — grep it if you want.

— BEFORE
task in tracker →
spec in google doc →
session in scrollback →
picture in nobody's head
— WITH NIGHT LOOP
task + spec + context →
session logged →
metrics update live →
risk scored →
one TUI, whole picture
STATEFILESYSTEM · LOCAL
SESSIONSLOGGED · TRACEABLE
HEALTHSCORED IN REAL TIME
03 · The loop

Intent to insight,
in six moves.

The loop is the product: specify, work, log, measure — and let the accumulated record steer the next session.

INTENT
Spec

Capture what and why before any code moves.

PLAN
Task

Tasks on a lifecycle board, spec and context attached.

EXECUTE
Session

Open a work session; focus and interruptions are tracked.

RECORD
Log

Close with notes; the session becomes durable history.

MEASURE
Metrics

Delivery and review intelligence update from the record.

STEER
Insight

Risk scores and flags decide what tomorrow looks like.

04 · Capabilities

A project OS,
not a todo list.

Built in TypeScript with a React/Ink terminal UI — the primitives of project operations, rendered in synthwave.

Dashboard

Project health, active work, and signals on one opening screen.

Task board

Lifecycle states with specs and context attached to every card.

Work sessions

Focused blocks with interruptions and notes, logged as durable history.

Spec & context

Intent travels with the task — sessions open with the right material loaded.

Delivery metrics

Throughput and completion signals computed from the actual record.

Review intelligence

Review load and debt surfaced before they become the bottleneck.

Risk scoring

Operational risk per project, computed and visible — not felt and ignored.

Terminal-native

A synthwave Ink TUI — keyboard-driven, fast, and where the work already is.

05 · The TUI

Real screens.
Real sessions.

The actual terminal surface — dashboard, board, work session view, and delivery metrics.

night-loop · dashboard
Night Loop dashboard — project health and signals in a synthwave TUI
Dashboard — project health and active signals.
night-loop · board
Night Loop task board — lifecycle states with specs attached
Board — tasks with lifecycle states and attached specs.
night-loop · work
Night Loop work session — focused session tracking
Work — a session in progress, tracked.
night-loop · metrics
Night Loop delivery metrics — throughput and review intelligence
Metrics — delivery signals computed from the session record.
06 · Example output

One week of sessions.
An operational picture.

The record accumulates into something no tracker gives you: how the project actually behaves, measured from the work itself.

project · weekly operational picture
computed from logged sessions · not self-reported
● LIVE
SESSIONS
logged
TASKS
traceable
REVIEW DEBT
surfaced
RISK
scored
WHAT THE RECORD ANSWERS
where did the time go?
which tasks are stalling?
is review keeping up?
what's the real risk?
SYSTEM
surfaceink/react tui
languagetypescript
statefilesystem
accountnone
repopublic · nightloop-cli
THE LOOP
spec → task → session
logged record
metrics + risk → next session
07 · Positioning
Night Loop treats the dev loop as infrastructure — not a todo app, not a time tracker, not a dashboard SaaS.

It is the operating system for developers who run serious agentic work from a terminal and want the operational picture to live there too.
BUILT FOR · terminal-native developers
OPTIMIZED FOR · traceability
PROVES OUT · spec → session → record → insight