057 PROBNAYA MANUAL · 057 v0.1.0
CONTENTS
00START

Getting started

From nothing to FIELD on screen.

01

Before you start

OS
macOS. The package declares "os": ["darwin"], so npm refuses to install elsewhere.
NODE
24.x is the supported version. The package declares >=22.5.0, which is where the built-in SQLite the store needs first exists; only 24 has been exercised.
NPM
11.x, or any npm that can run npx.
BROWSER
A WebGPU browser — Chrome 113+, Edge 113+, or Safari 26+. There is no fallback renderer.
ANYTHING ELSE
Nothing. No account, no key, no configuration file, no service to install.

Downloading the package needs the npm registry. Running it does not need a network.

02

Start it

RUN THIS
npx 057

Or keep it around:

npm install -g 057
        057

It prints a short banner — version, URL, where it stores, what it keeps, how to delete it — and then runs in the foreground. Nothing is installed into your login items and there is no background service.

03

Open the interface

Open the URL it printed, normally http://localhost:5057, in a WebGPU browser. 057 --open starts it and opens your default browser in one step; it is not the default, because the default browser is not necessarily one that has WebGPU.

If 5057 is taken, 057 takes the next free port and prints that instead, trying up to ten ports from the one it started at. Pin one with --port <n> or O57_PORT.

The first screen is FIELD. A machine with no AI runtimes installed still shows its own mass and its processes, and the header says OS ONLY. Reading FIELD is how to read what you are looking at.

04

While it runs

The process table is sampled every five seconds for as long as 057 runs, whether or not a browser is open. Runtime session state is read while the interface is open — those runtimes keep their own files, so closing the tab loses nothing: the next time you open it, the window is re-read and the day fills back in.

05

Stop it, and start it again

Ctrl-C. It checkpoints and prints 057 stopping — history is on disk.

Starting it again opens the same store at the same path and continues the same history. A second copy started while the first is running takes the next free port and writes to the same store.

06

Where your data lives

One SQLite database at ~/.057/events.db, with its -wal and -shm companions, created owner-only. Nothing is written anywhere else. O57_STORE (or --store) points it elsewhere. Data and privacy is the full account of what is in it.

07

The commands

057                 # observe, and serve the interface
        057 status          # where the store is, what it holds, what has contributed
        057 compact         # reclaim disk freed by retention
        057 reset           # delete the local store
        057 --help
057observe, and serve the interface
057 statuswhere the store is, what it holds, what has contributed
057 compactreclaim disk freed by retention
057 resetdelete the local store
057 --help

057 STATUS

Prints the store path, the schema version, the size split between database and write-ahead log, the event and claim counts, the retention in force, the file permissions, and one line per source that has contributed with the span of dates it covers. It does not sample anything — asking where the store is should not start observing.

057 COMPACT

Retention deletes rows; SQLite then reuses those pages rather than returning them, so the file plateaus instead of shrinking. compact sweeps expired history and rewrites the database, which is what actually returns disk. It needs room for a second copy while it runs, and it prints the size before and after.

Worth running after a long stretch of heavy use, or after lowering a retention window. Not something to run on a schedule.

057 RESET

DESTRUCTIVE
057 reset deletes your local 057 telemetry. There is no backup and no undo.

It lists the exact files it will delete and asks before doing it. --yes skips the question; with no terminal to ask in, it refuses rather than assuming yes.

What comes back afterwards and what does not: session and execution history is re-read from the runtimes’ own files, so most of it returns. OS process history does not — a process table only describes now, and nothing on the machine keeps yesterday’s.

Reset is for a store you want gone, or one that is genuinely not a database any more. It is not the fix for a permissions problem. See Troubleshooting.

08

Configuration

Environment variables and flags; there is no config file. A flag beats the variable, which beats the default.

O57_STORE~/.057/events.db
Store file. A relative path resolves against the working directory.
O57_PORT5057
Port. The next free one is taken if it is busy.
O57_HOST127.0.0.1
Bind address. Read Binding beyond loopback first.
O57_RETAIN_PROCESS_DAYS7
Days of process observation kept; 0 keeps them indefinitely.
O57_RETAIN_DAYS90
Days of session and execution history kept; 0 keeps them indefinitely.
WORK_ROOTShome, one level deep
Colon-separated workspace roots to look for 0x2F task state in.
DSH_HOME
CLAUDE_HOME
CODEX_HOME
GEMINI_HOME
CURSOR_GLOBAL_STORAGE
each runtime’s own default
Where to read that source from.

A value that cannot be parsed falls back to the default rather than to “off” — O57_RETAIN_DAYS=forever keeps 90 days. The failure mode of a typo should not be unbounded growth.

09

Upgrading and removing

npm install -g 057@latest replaces the package and does not touch ~/.057. Uninstalling the package does not delete it either. 057 reset — or rm -rf ~/.057 — is the only thing that deletes your telemetry.

057 PROBNAYA EVERY FIELD IN THIS MANUAL IS SYNTHETIC