Performance and memory use

Content search scans saved transcripts in a background worker without loading every archived conversation into the main history cache. A new query cancels the old scan. Skill inventory scans yield between chunks, reuse parsed files across symlink aliases and avoid repeating the full scan just to open the catalog. Memory diagnostics load their full details only when requested.

Recently opened transcripts use an eight-entry cache with an 8 MiB estimated payload budget. Recent threads still appear immediately; evicted ones load again when selected. A larger selected transcript remains visible but is not retained in that cache after leaving it. These are cache bounds, not a promise about total application RAM.

Work logs are saved per thread, so activity in one thread no longer rewrites all historical logs. The optional export to shared memory has a separate cap of 256 pending entries and a 4 MiB estimated payload, including requests in flight. Under pressure that optional mirror may omit entries; the local conversation history remains intact. Removing a project also retires its idle agent sessions, and quitting cleans up detached agent processes.