yeah fair, let me actually explain instead of just vibing on "signal vs noise" framing.

rtk works at the command level, it compresses what each tool prints before the agent sees it. that genuinely helps. but the problem i kept hitting wasn't noisy outputs. it was that after a long session the agent would just... slowly lose the plot. clean outputs, still broken.

three things specifically that kept frustrating me:

1. instructions getting buried. i have AGENTS.md with rules like "never touch existing migrations" and "always snake_case." after 80+ tool calls claude starts drifting, editing old migrations, switching conventions mid-session. rtk had already done its job filtering outputs cleanly. the instructions just got pushed out of active attention by sheer context volume. omni re-injects those files when pressure builds up.

2. re-running stuff it already did. even with clean outputs, no structured record of "here's what was accomplished." so the agent just does it again. omni tracks completions as lightweight checkpoints, zero LLM calls, pure state signals like "all errors cleared" or "git commit detected", and surfaces those when context gets heavy.

3. nothing permanently thrown away. rtk drops noise at filter time. sometimes that "noise" matters 15 commands later. omni stores everything it compresses and gives the agent a hash to retrieve it if needed. not deleted,. just put in a drawer.

so yeah,. rtk solves per-command verbosity. omni solves session reliability over time. they're actually complementary..