logo

Show HN: Context Gateway – Compress agent context before it hits the LLM

Posted by ivzak |3 hours ago |23 comments

sethcronin 21 minutes ago[1 more]

I guess I'm skeptical that this actually improves performance. I'm worried that the middle man, the tool outputs, can strip useful context that the agent actually needs to diagnose.

kuboble an hour ago[1 more]

I wonder what is the business model.

It seems like the tool to solve the problem that won't last longer than couple of months and is something that e.g. claude code can and probably will tackle themselves soon.

tontinton an hour ago[2 more]

Is it similar to rtk? Where the output of tool calls is compressed? Or does it actively compress your history once in a while?

If it's the latter, then users will pay for the entire history of tokens since the change uncached: https://platform.claude.com/docs/en/build-with-claude/prompt...

How is this better?

root_axis an hour ago[2 more]

Funny enough, Anthropic just went GA with 1m context claude that has supposedly solved the lost-in-the-middle problem.

thesiti92 2 hours ago

do you guys have any stats on how much faster this is than claude or codex's compression? claudes is super super slow, but codex feels like an acceptable amount of time? looks cool tho, ill have to try it out and see if it messes with outputs or not.

esafak 2 hours ago

I can already prevent context pollution with subagents. How is this better?

lambdaone 44 minutes ago

This company sounds like it has months to live, or until the VC money runs out at most. If this idea is good, Anthropic et. al. will roll it into their own product, eliminating any purpose for it to exist as an independent product. And if it isn't any good, the company won't get traction.

uaghazade 2 hours ago

ok, its great

verdverm 2 hours ago

I don't want some other tooling messing with my context. It's too important to leave to something that needs to optimize across many users, there by not being the best for my specifics.

The framework I use (ADK) already handles this, very low hanging fruit that should be a part of any framework, not something external. In ADK, this is a boolean you can turn on per tool or subagent, you can even decide turn by turn or based on any context you see fit by supplying a function.

YC over indexed on AI startups too early, not realizing how trivial these startup "products" are, more of a line item in the feature list of a mature agent framework.

I've also seen dozens of this same project submitted by the claws the led to our new rule addition this week. If your project can be vibe coded by dozens of people in mere hours...

poushwell 32 minutes ago

[flagged]

BrianFHearn 2 hours ago

[flagged]

zenon_paradox 2 hours ago

Comment deleted

eegG0D an hour ago[2 more]

[flagged]

jameschaearley 2 hours ago[1 more]

[flagged]