This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
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
Terse
Build React UIs with 75% fewer agent tokens
Terse is a tiny, presentation-only UI language for coding agents. A Vite plugin compilesterse views at build time into the same React + shadcn/ui + Tailwind your agent writes today: ~76% fewer tokens (755 vs 3,130 across five benchmark screens), zero runtime. Typos fail the build with file:line:col and the fix, so agents self-correct. State and data stay in TSX, and the output is plain TSX you can keep. Works with Claude Code, Cursor and Codex. Open source, MIT.
Hi Product Hunt 👋 I'm Divyansh from Avyukt Tech Labs.
Most of the React UI I ship now is written by an agent, and most of what the agent writes isn't the UI. When I measured five common screens, 57% of the TSX tokens were class names, imports, prop types and closing tags.
Terse is a small language for the part agents write most: what a screen shows.
• One node per line. Styles are tokens like gap=md, so gap-[13px] can't even be written.
• Data and handlers come in as props from normal TSX. State, effects and fetching stay where they are.
• A Vite plugin compiles it at build time to plain shadcn/ui + Tailwind TSX. No runtime, nothing to eject.
• Typos fail the build with file:line:col and "did you mean 'button'?", so the agent fixes it in one edit.
On the five benchmark screens it's 755 tokens vs 3,130 (75.9% fewer). The weather demo on the site goes from 1,727 to 478. Method and files are in the repo; pnpm bench reproduces them.
Try it in two minutes: npm create terse-app@latest my-app. The starter ships an AGENTS.md / CLAUDE.md so Claude Code, Cursor or Codex can pick up the language straight away.
It's v0 and the vocabulary is small on purpose. What I'd most like to hear is where it breaks: a screen you couldn't express, an error message that didn't help your agent, or the adapter you want next (Material UI is the obvious first one).
About Terse on Product Hunt
“Build React UIs with 75% fewer agent tokens”
Terse was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #123 on the daily leaderboard. Terse is a tiny, presentation-only UI language for coding agents. A Vite plugin compilesterse views at build time into the same React + shadcn/ui + Tailwind your agent writes today: ~76% fewer tokens (755 vs 3,130 across five benchmark screens), zero runtime. Typos fail the build with file:line:col and the fix, so agents self-correct. State and data stay in TSX, and the output is plain TSX you can keep. Works with Claude Code, Cursor and Codex. Open source, MIT.
On the analytics side, Terse 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 Terse performed against the three products that launched closest to it on the same day.
Who hunted Terse?
Terse was hunted by Divyansh Gupta. 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 Terse including community comment highlights and product details, visit the product overview.
Divyansh Gupta