Troubleshooting
Every fault the instrument can report, what it means, and what to do about it.
057 status
It prints the store in use, its size, its permissions, and which sources have contributed — which answers most of what follows without guessing.
057 reset deletes your local 057 telemetry permanently, and the OS-process half of it cannot be re-collected. It is the last resort on this page, not the first, and it is never the fix for a permissions problem.The browser has no WebGPU, or it failed to initialise. There is no fallback renderer and there will not be one — FIELD is the product, so 057 says this rather than showing you something that is not FIELD.
Use Chrome 113+, Edge 113+, or Safari 26+. If you are already in one, the line under the message is the browser’s own reason; a machine with GPU acceleration disabled, or a remote or virtualised display, is the usual cause.
EBADPLATFORM on Linux or Windows is deliberate: the package declares macOS only. The process sampler reads a BSD process table and the Cursor reader looks in a macOS application-support path. Neither is right elsewhere, and a 057 that silently mis-parsed your process table would be worse than one that will not start. Do not force it.
The store uses Node’s built-in SQLite, which first exists in 22.5. Node 24 is the supported version.
057 takes the next free port and prints it, trying up to ten ports from the one it started at. If it reports that no free port was found, choose one: 057 --port 5100, or O57_PORT=5100.
A second copy of 057 is the most likely occupant of 5057.
Check which state it is in first — the header, and 057 status for what has actually contributed.
NOT‑INSTALLED — 057 looked where that runtime keeps its state and there was nothing there. Not a fault, and not something to fix unless the runtime really is installed somewhere else, in which case point 057 at it with that source’s environment variable.
INSTALLED‑NO‑DATA — the runtime is here and has written nothing 057 can read yet. Use it once.
0X2F SPECIFICALLY — workspaces are found by scanning your home directory one level deep. If yours are elsewhere, set WORK_ROOTS to the workspace roots, colon-separated.
Nothing at all beyond OS processes, and the header says OS ONLY: that is the valid mode for a machine with no AI runtimes installed, not a failure. Switch the header control to SYNTHETIC if you want to see the field move.
That source is installed here and 057 cannot read it — several collection rounds in a row, not one unlucky one. The header names it and shows the error.
Usual causes: the runtime changed its on-disk format in an upgrade, or its directory is not readable by you. Check the named path is yours and readable. The rest of 057 is unaffected — other sources, captured history and the store all continue.
Some of what a source offers can be read and some cannot. The computation is still observed; some of its semantics are not. Captured history is intact. Often transient — a file being rewritten while it was read.
Some stored rows could not be read back as JSON. Those rows keep their identity and their time and lose one attribute channel; everything else is used normally, and nothing is deleted. The count and the affected column names are shown; the contents are not, because they are your paths and labels.
Run 057 compact — it rewrites the database. If the count keeps growing after that, the file is deteriorating underneath 057, and moving it aside is then reasonable; back it up first.
The file 057 opened is no longer the file at that path — deleted, or replaced while 057 was running. Anything captured since is going to a file nobody can reach.
Stop 057 and start it again. It opens whatever is actually at the path.
A restored backup, a read-only volume, a file owned by another user. The store is intact — this is a permissions problem, and deleting it would trade a permission bit for your telemetry.
Check that you own the file and its directory and that both are writable; 057 wants 0600 on the store and 0700 on its directory. Or point O57_STORE at a path you can write.
Refused rather than downgraded, because an older build reading a newer schema is the one path in this design where silent corruption is reachable. The store was not modified.
Upgrade 057, or point O57_STORE at a different file.
The file at that path exists and is not a 057 store. Move it aside — 057 starts a new one — and back it up first if it might be something you want.
057 opened a store with nothing in it. On a first run that is exactly right. On a later run it means the store it was pointed at is not the one that has your history: check O57_STORE, and check 057 status for the path actually in use.
If you ran 057 from a checkout before this release, it may also name a store from the previous layout and tell you where it is. It is not moved, adopted or deleted; point O57_STORE at it to keep using it.
057 status shows the size split between database and write-ahead log. Retention already bounds it — 7 days of process observation, 90 of session history — but deleted rows are reused, not returned, so the file plateaus rather than shrinking.
057 compact sweeps and rewrites, which is what returns disk. Lower O57_RETAIN_PROCESS_DAYS first if you want the plateau itself lower; process observation is the bulk of the file.
Frame rate depends on your machine, and 057 does not promise one. It paces in whole display refreshes and stops drawing when nothing is moving — steady rather than fast is the intent. A smaller window is the cheapest improvement: cost scales with viewport, never with how much has been observed.
Where the GPU cannot be timed, 057 leaves simulation resolution alone rather than adapting to a cost it cannot measure.
Expected. The process table is sampled for as long as 057 runs; runtime session state is read while the interface is open. Those runtimes keep their own files, so nothing is lost — open the interface and the window is re-read.
--yes skips the question, and with no terminal to ask in it refuses rather than assuming yes.