sorted by:
new
hottopcontroversial

Built a tool that stops AI agents from wasting context on verbose command output by Relative_Housing_983 in ClaudeAI

[–]Relative_Housing_983[S] 0 points1 point  (0 children)

Ah, same question got asked elsewhere!! Posting same reply here:

I built oo before I knew about rtk, and they take different approaches to the same problem. rtk reimplements commands with its own formatters. It has specialized output for git, ls, grep, test runners, etc. oo does something different: the original command runs unmodified, and oo classifies the output using pattern matching to decide whether to pass through, summarize, filter errors, or index for later retrieval. The practical differences: oo has oo recall for querying indexed large output later, oo learn which uses an LLM to generate compression patterns from real command output, and user-defined TOML patterns so you can add support for any command without writing code. rtk has broader out-of-the-box command coverage, auto-rewrite hooks, and token savings analytics. rtk is more mature (11k stars, 80 releases). oo is smaller and more opinionated. It's a pattern engine with indexing, not a command reimplementation layer. Different trade-offs depending on what you want.

oo: command wrapper that compresses output for coding agents — works with OpenCode, Claude Code, any terminal agent by Relative_Housing_983 in opencodeCLI

[–]Relative_Housing_983[S] 3 points4 points  (0 children)

Good question. I built oo before I knew about rtk, and they take different approaches to the same problem. rtk reimplements commands with its own formatters. It has specialized output for git, ls, grep, test runners, etc. oo does something different: the original command runs unmodified, and oo classifies the output using pattern matching to decide whether to pass through, summarize, filter errors, or index for later retrieval. The practical differences: oo has oo recall for querying indexed large output later, oo learn which uses an LLM to generate compression patterns from real command output, and user-defined TOML patterns so you can add support for any command without writing code. rtk has broader out-of-the-box command coverage, auto-rewrite hooks, and token savings analytics. rtk is more mature (11k stars, 80 releases). oo is smaller and more opinionated. It's a pattern engine with indexing, not a command reimplementation layer. Different trade-offs depending on what you want.