Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Caveman

why use many token when few do trick

One command wraps Claude Code, Codex, Hermes, and more with a local proxy that compresses logs, tool output, and files before every provider call. In a pinned 54-run benchmark: 33.2% fewer input tokens with 18/18 correctness checks. Caveman can also run any existing agent skill with ~70% fewer tokens by loading text as images. Built on an open-source ecosystem with 97K+ GitHub stars.

Top comment

A few months ago, I was a uni student spending more on AI than on groceries. Naturally to solve that, I made a skill that makes Claude Code answer like a caveman. "New object ref each render. Wrap in useMemo." 19 tokens instead of 69. People kept it installed because nothing broke and bills got smaller. 97,000 Github stars later plus a #1 post on Hacker News. Then I read what was actually crossing the wire, and the answers were a rounding error. Every turn re-sends tool schemas, file contents, old history, and 300 lines of npm install noise. My agent talked like a caveman and read like a lawyer. v2 is a local proxy between your agent and the provider. caveman claude wraps Claude Code; same for Codex, Gemini CLI, Aider, opencode, Hermes, OpenClaw. It never touches your config, and subscription OAuth passes through byte-exact. The engine sniffs each payload type and routes it to a different compressor: logs keep errors and stack traces and lose the progress spam, code keeps imports and signatures via tree-sitter, JSON keeps structure plus error subtrees. Lossy transforms are landmines, so originals get written to a content-addressed store on your disk before anything goes upstream, and the agent can pull the real bytes back with one tool call. Parse failure or a larger result means the bytes pass through untouched. Numbers, since that's the obvious question: pinned 54-run Claude Code benchmark, 33.2% fewer provider-reported input tokens, 18/18 exact-answer checks, method and per-case results committed to the repo. Local measurements are labeled "inferred" because a local tokenizer is an estimate. There are no "up to 90%!" claims anywhere and no verified production numbers yet. The dumbest thing in here that works: pixel mode. Dense text rendered to PNG costs image tokens instead of text tokens. A 63.7k-char minified tool catalog plus a 93k-char log went from ~55k estimated text tokens to ~11k image tokens. On sparse code the PNG costs more than the text, so the gate refuses and prints why. Skill is MIT and stays MIT. Engine is BSL-1.1, flips to Apache-2.0 within four years, self-hosting free including production. Runs local, no account. If a gate declines something you think should compress, the reason is printed. Argue with it in an issue. It's not perfect yet, and there are many many more optimizations to be built. This is the first release in a long line of products to reduce the cost of AI per task (not just the tokens).

About Caveman on Product Hunt

why use many token when few do trick

Caveman launched on Product Hunt on August 13th, 2026 and earned 127 upvotes and 7 comments, placing #8 on the daily leaderboard. One command wraps Claude Code, Codex, Hermes, and more with a local proxy that compresses logs, tool output, and files before every provider call. In a pinned 54-run benchmark: 33.2% fewer input tokens with 18/18 correctness checks. Caveman can also run any existing agent skill with ~70% fewer tokens by loading text as images. Built on an open-source ecosystem with 97K+ GitHub stars.

On the analytics side, Caveman competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Caveman performed against the three products that launched closest to it on the same day.

Who hunted Caveman?

Caveman was hunted by Julius Brussee. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.

For a complete overview of Caveman including community comment highlights and product details, visit the product overview.