Limits
Where Salidium stops, and what to do about it.
- Native Windows
- No hook relay: it needs a POSIX shell and curl. Salidium still reads the session files your agents write, so history and live tailing work. What is lost is the sub-second hook notification.
- Recognised checks
- Only a fixed list of test, build, typecheck and lint runners counts as a check. A watch-mode run and a backgrounded run never do.
- A session read once
- It is not read again, however much the adapter improves, because its cursor still matches.
salidium reingest --allthensalidium restartis what recovers it. - Retention
- Sessions are kept forever unless you set a policy. Working, waiting and pinned sessions are never removed by one.
- Ingest problems
- An unreadable transcript record is counted in Quantities under data handling. A dropped hook payload is not: it reaches the daemon log and nothing else.
salidium doctor is the first thing to run when something is wrong. It checks the setup and prints what it finds rather than a score. The rest of the commands are under CLI.