Repository navigation
lossless v0.1.44
0.1.44 — 2026-10-23
- An idle watcher tick costs about an eighth of what it did. 0.1.43 stopped re-reading transcripts every tick, but a tick still statted every known transcript, lstatted every harness directory, read the whole session table and opened the Codex state database, about 30 ms of CPU every 2 s on a store with a few thousand sessions. Now a file or directory unchanged for 10 minutes is looked at about every 30 s (15 ticks at the default interval, fewer with a longer
--watch-interval) on a slot spread by its path, the session list is kept between ticks (re-read when any process adds, changes or removes a session, which a trigger-kept version number on the session table shows, or on the 5-minute full pass), the Codex state database is re-read only when it or its WAL changes, and the tick's working buffers are reused. The same tick now costs about 4 ms. Hooks still report each turn as it happens; the watcher, which catches what a hook missed, picks up a turn in a session idle for 10 minutes or more within about 30 s instead of 2 s. - Catch-ups redact about ten times faster. Every new transcript line runs through the secret patterns before it reaches the tape, and that was most of a catch-up's CPU. Each pattern now first checks for a literal it cannot match without (
AKIA,ghp_, a database URL scheme, apassword=-style key), so most lines skip most regexes. What gets redacted is unchanged: a differential test and a fuzz test compare every line against the regex-only path. - Asks and hook catch-ups stop running git on every call. Resolving a workspace to its project ran
gitonce or twice per ask and per hook catch-up. The answer is now kept per workspace: anowner/repokey for 10 minutes, a key for a workspace with no remote yet for 30 seconds, so records move toowner/reposoon after you add one. - Session lookups use an index. Looking a session up by id (every remember, every ask that carries one) and listing a project's sessions (an ask without one) read the whole session table; both now go through an index created on startup.
- A catch-up that changes nothing writes nothing. Re-recording an unchanged session row was a database write on every hook catch-up.
- A slow ask leaves a line in serve.log. An ask over a second logs where the time went: the ask-time catch-up and how many sessions it copied from, the project lookup, the rest, and the daemon's CPU over the same window. The line names no goal, path, project or session.
Install
curl -fsSL https://github.com/jbgh/lossless/releases/latest/download/install.sh | sh
lossless setup
Already installed: lossless update