Data and privacy
057 observes one Mac — yours — and keeps what it observes locally. A trusted 057 Display receives the current FIELD over your local network. This is the exact account of what that means.
npx @probnaya/057-cli and npm install -g @probnaya/057-cli use it. Installation only.057.probnaya.work/appcast.xml about once a day, carrying the app’s version. On by default; off in the app’s 057 menu.127.0.0.1, and on a paired 057 Display over an authenticated local connectionOnly this machine, and only two kinds of thing:
- The process table, sampled every five seconds while
057is running. - Files the AI coding runtimes on your machine have already written for their own purposes — their session logs and state — read while the interface is open.
057 does not attach to processes, does not use eBPF, does not read process memory, and does not watch your keyboard, screen, clipboard, network or filesystem at large. It reads nothing that those runtimes were not already keeping.
- Your hostname and machine name.
- Working-directory and workspace paths, which usually contain project names.
- Process names and command paths as the process table reports them.
- Session and execution labels as the runtime recorded them — which may include a task title or a first prompt line.
- Model names, tool names, token counts, statuses, timings, and each runtime’s own identifiers.
- A timeline of when your machine was working, which is a reasonable proxy for when you were.
- Prompt and response bodies.
- File contents and diff bodies.
- Keystrokes, screen contents, clipboard.
- Credentials, API keys, environment variables.
- Full command lines — the command name, never the argument vector.
- Network traffic.
Where 057 read a fact from, it stores a pointer to the source record — a path and an offset — never a copy of it.
057 makes no Internet request but one: the macOS app’s update check. A paired 057 Display communicates locally, directly with your Mac.
No account system, no cloud component, no synchronisation, no product analytics, no crash reporting, no phone-home. The web / CLI surface does not even check for updates. The interface fetches nothing but its own local API — not even a web font, which is why the type falls back to your system monospace if IBM Plex Mono is not installed locally.
Five precise qualifications, because the sentence is only worth having if it is exact:
npx @probnaya/057-cli and npm install -g @probnaya/057-cli download the package from the npm registry, like any package. Once installed, running it does not.https://057.probnaya.work/appcast.xml; the request carries the app’s version and nothing else — no system profile, none of your telemetry. It is on by default and off with Check for Updates Automatically in the app’s 057 menu. An update installs only when you choose, and only if it carries 057’s signature.127.0.0.1. Nothing leaves the machine over it.057.landscape states: machine, project and task labels; execution/session labels; statuses, timings and geometry. It does not receive source files, prompts, responses, telemetry history, credentials, paths, models, tools or token counts.057 reset to clear the local Display identity and trust register.The browser API is unauthenticated by design and remains bound to loopback. The mobile Display does not expose or reuse it: mobile delivery is a separate mutual-TLS interface created only while Desktop is running.
O57_HOST (or --host) binds elsewhere. Doing that publishes an unauthenticated read of your hostname, your project paths, your session labels, your models and a minute-by-minute record of when you were at your machine, to everything that can reach that address. 057 warns at startup when you do it. There is no auth to turn on, and putting 057 behind a reverse proxy has the same effect.While bound to loopback, several hardenings apply against pages you already have open in a browser: requests claiming a non-loopback Host are refused, so a hostile site cannot resolve its own domain to 127.0.0.1 and read your store; only same-origin and top-level requests are served, so a cross-site request cannot trigger a collection round; and 057 refuses to be framed at all.
One consequence worth knowing: scripting a state-changing API call with curl is refused by design.
One SQLite database:
~/.057/events.db
~/.057/events.db-wal
~/.057/events.db-shm
~/.057/events.db.display/ # Display identity and trusted-device registerThe first three carry telemetry — the write-ahead log is not a scratch file. The .display directory is created when Display delivery starts and contains the Mac’s private Display identity plus its trusted-device register; it is owner-only and is not telemetry. O57_STORE (or --store) points 057 at a different file. 057 status prints the telemetry-store path, size and permissions.
Permissions. The directory is created 0700 and the files 0600 — owner-only. A store created by a version before 0.1.0 was world-readable and is tightened in place the first time 0.1.0 opens it. On a filesystem with no POSIX modes, or a file you do not own, 057 leaves it alone and says so rather than refusing to start.
0 on either variable means keep indefinitely. A sweep runs at startup and hourly.
Retention expires whole subjects, not individual records. A process, session or execution is removed only once the last thing observed about it is past its cutoff — and then everything about it goes at once. A month-old process still running now is not partly expired. A session declared months ago whose executions ran yesterday is kept, because those executions live in it.
Deleting rows does not shrink the file: SQLite reuses the freed pages, so the store plateaus rather than shrinks. 057 compact is what returns disk to the filesystem.
How much space. It depends entirely on how busy the machine is, and one machine’s number is not a promise about yours. For calibration only: the machine 057 was built on accumulated roughly 145,000 events and 160 MB over several weeks of heavy use with no retention at all, which is the condition this release fixes. Watch your own with 057 status.
npm install -g @probnaya/057-cli@latest does not touch ~/.057.057 reset, or rm -rf ~/.057057 reset deletes your local 057 telemetry and any Display identity/trust state permanently. It lists the files first and asks before doing it; --yes skips the question.There is none of either, and no recovery beyond your own filesystem backups. The store is a plain SQLite file; that is the export, and it is readable with any SQLite client.
Two conditions that look similar and are not, kept apart deliberately.
A damaged store degrades rather than dies. If a stored row cannot be read as JSON, that row keeps its identity and its time and loses one attribute channel; everything else is used normally and nothing is deleted. The interface reports STORE DEGRADED with a count and the affected column names — never the contents, which are your paths and labels.
A store 057 cannot write is a permissions problem, not corruption. A restored backup, a read-only volume, a file owned by someone else: 057 refuses to start and explains why. It will never suggest deleting an intact store to fix a permission bit, and neither should anyone else. See Troubleshooting.
A store written by a newer 057 is refused rather than downgraded, and is not modified.
057 never shows a plausible number in place of a gap. If a source does not report something, it is absent, not estimated. Anything computed rather than read carries the assumption it rests on, and the interface will show you that assumption. There is no cost figure anywhere, because sources report tokens and CPU time and none of them reports money.