Codag is a compression and control layer for the tool outputs that coding agents read, targeting the repetitive lines that pile up from searches, tests, builds, logs, and API responses before native context compaction kicks in. The pitch to developers is direct: a single command attaches it to Claude Code and Codex, and it teaches the agent to read large tool results efficiently , so a multi-thousand-line test run or grep dump collapses to the failing lines and matches that actually drive the next decision, with the omitted bytes kept locally and retrievable on demand.
The launch matters now because agent sessions increasingly stall on context bloat, where a single oversized tool result can evict what the agent already learned and force another expensive lap through the same commands. Codag positions itself as a drop-in proxy that leaves the model, prompts, and provider account untouched and only intervenes on large eligible results, classifying each one, reducing what is large, and exposing exact retrieval for the rest. For teams running Claude Code or Codex at scale, the appeal is cutting token spend and turn count without changing workflow or migrating tooling.
Codag is a Y Combinator S26 company founded by Michael Zhou, who is running it as a solo founder out of San Francisco after previous engineering stints at Okta and Shopify.
Comments (8)
Sign in to join the discussion.
R
Rohit ParekhAug 18, 2026
the pivot arc from logs to searches to builds is basically every infra founder's diary. curious what your compression looks like on flaky test output where half the noise is actually signal.
M
Maksym O.Aug 18, 2026
give me the SDK details. streaming support, rate limits, and can I bring my own tokenizer or am I stuck with whatever you picked?
Y
Yuko TanakaAug 18, 2026
tool output tax is a real phrase I'm stealing for my next pitch, sorry not sorry.
P
Priya BalasubramanianAug 18, 2026
the tweet structure is doing a lot of work here. starting with 'we started with logs' then hitting the pattern reveal is chef's kiss for a launch post.
C
Caro N.Aug 18, 2026
if you're sitting in front of api responses and build logs, where does that data live and for how long? asking for every security review I'm about to run.
K
kwame b.Aug 18, 2026
how big is the team behind this? feels like the kind of thing two very tired people build in a garage between YC office hours.
L
Lena VasquezAug 18, 2026
would love to see how your compression compares to LLMLingua style approaches on structured tool traces. is there a writeup or is this all vibes and vibes?
B
Bogdan I.Aug 18, 2026
the thumbnail on that launch video is cropped weird on mobile, but the pacing in the first 8 seconds is genuinely tight. taking notes for my own launch in, uh, 3 weeks.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Codag
Cut the tool-output tax your coding agents pay
Cut the tool-output tax your coding agents pay
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Codag is a compression and control layer for the tool outputs that coding agents read, targeting the repetitive lines that pile up from searches, tests, builds, logs, and API responses before native context compaction kicks in. The pitch to developers is direct: a single command attaches it to Claude Code and Codex, and it teaches the agent to read large tool results efficiently , so a multi-thousand-line test run or grep dump collapses to the failing lines and matches that actually drive the next decision, with the omitted bytes kept locally and retrievable on demand. The launch matters now because agent sessions increasingly stall on context bloat, where a single oversized tool result can evict what the agent already learned and force another expensive lap through the same commands. Codag positions itself as a drop-in proxy that leaves the model, prompts, and provider account untouched and only intervenes on large eligible results, classifying each one, reducing what is large, and exposing exact retrieval for the rest. For teams running Claude Code or Codex at scale, the appeal is cutting token spend and turn count without changing workflow or migrating tooling. Codag is a Y Combinator S26 company founded by Michael Zhou, who is running it as a solo founder out of San Francisco after previous engineering stints at Okta and Shopify.
Comments (8)
the pivot arc from logs to searches to builds is basically every infra founder's diary. curious what your compression looks like on flaky test output where half the noise is actually signal.
give me the SDK details. streaming support, rate limits, and can I bring my own tokenizer or am I stuck with whatever you picked?
tool output tax is a real phrase I'm stealing for my next pitch, sorry not sorry.
the tweet structure is doing a lot of work here. starting with 'we started with logs' then hitting the pattern reveal is chef's kiss for a launch post.
if you're sitting in front of api responses and build logs, where does that data live and for how long? asking for every security review I'm about to run.
how big is the team behind this? feels like the kind of thing two very tired people build in a garage between YC office hours.
would love to see how your compression compares to LLMLingua style approaches on structured tool traces. is there a writeup or is this all vibes and vibes?
the thumbnail on that launch video is cropped weird on mobile, but the pacing in the first 8 seconds is genuinely tight. taking notes for my own launch in, uh, 3 weeks.