Every change to a page is logged with the dream that made it, and that dream records the notes and sessions it read. One command shows the whole chain, so a wrong line can be followed back to the note that caused it.
$ lnx trace testing.md
/testing.md: 2 changes
v1 2026-11-18 16:44 create: first page
by hand
v2 2026-11-18 16:44 write: needs DATABASE_URL since the Postgres move; flaky ui rerun
dream p_mwmcqffwbb2543 (agent)
note n_mwmcqfft848316: Tests now need DATABASE_URL=postgres://localhost/app_test
in .env.test since the Postgres move
note n_mwmcqffu5e8ba4: UI snapshot tests are flaky on CI: rerun with
make test-ui RETRY=2
Saving, searching and the digest never touch the network. The only call Lynx can make is a dream you start with your own key, and each one is written to a ledger: when, which model, how many characters. Dreams through your agent add nothing.
$ lnx outbound
nothing has left this machine for space shop-api
$ lnx status
space shop-api
notes 5 3 waiting for a dream
wiki 1 page
conflicts 2 possible: lnx conflicts
fading none
outbound nothing has ever left this machine