HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Tura-AI
tura
Rust2026–2026
Tura-AI / tura

tura

Build agent that uses 80% less token and delivers better results.

3Distinct people
9Mentions
0Explicit recommenders
665GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Build agent that uses 80% less token and delivers better results.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:57:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day9 dated mentions

Observed mentions: 2026-07-15 15:10:14 UTC to 2026-08-11 20:39:32 UTC.

0122026-07-15 00:00:00 UTC to 2026-07-16 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJul 152026-07-16 00:00:00 UTC to 2026-07-17 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-07-17 00:00:00 UTC to 2026-07-18 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-07-18 00:00:00 UTC to 2026-07-19 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-07-19 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-20 00:00:00 UTC to 2026-07-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-21 00:00:00 UTC to 2026-07-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-22 00:00:00 UTC to 2026-07-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-23 00:00:00 UTC to 2026-07-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-24 00:00:00 UTC to 2026-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-25 00:00:00 UTC to 2026-07-26 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-07-26 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-28 00:00:00 UTC to 2026-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 282026-07-29 00:00:00 UTC to 2026-07-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-30 00:00:00 UTC to 2026-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-08-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-02 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 00:00:00 UTC to 2026-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-05 00:00:00 UTC to 2026-08-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 00:00:00 UTC to 2026-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 00:00:00 UTC to 2026-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-08 00:00:00 UTC to 2026-08-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-09 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-11 00:00:00 UTC to 2026-08-12 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 11

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 152026-07-15 00:00:00 UTC2026-07-16 00:00:00 UTC211
Jul 162026-07-16 00:00:00 UTC2026-07-17 00:00:00 UTC110
Jul 172026-07-17 00:00:00 UTC2026-07-18 00:00:00 UTC211
Jul 182026-07-18 00:00:00 UTC2026-07-19 00:00:00 UTC110
Jul 192026-07-19 00:00:00 UTC2026-07-20 00:00:00 UTC000
Jul 202026-07-20 00:00:00 UTC2026-07-21 00:00:00 UTC000
Jul 212026-07-21 00:00:00 UTC2026-07-22 00:00:00 UTC000
Jul 222026-07-22 00:00:00 UTC2026-07-23 00:00:00 UTC000
Jul 232026-07-23 00:00:00 UTC2026-07-24 00:00:00 UTC000
Jul 242026-07-24 00:00:00 UTC2026-07-25 00:00:00 UTC000
Jul 252026-07-25 00:00:00 UTC2026-07-26 00:00:00 UTC110
Jul 262026-07-26 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-07-28 00:00:00 UTC000
Jul 282026-07-28 00:00:00 UTC2026-07-29 00:00:00 UTC000
Jul 292026-07-29 00:00:00 UTC2026-07-30 00:00:00 UTC000
Jul 302026-07-30 00:00:00 UTC2026-07-31 00:00:00 UTC000
Jul 312026-07-31 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 12026-08-01 00:00:00 UTC2026-08-02 00:00:00 UTC000
Aug 22026-08-02 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-04 00:00:00 UTC000
Aug 42026-08-04 00:00:00 UTC2026-08-05 00:00:00 UTC000
Aug 52026-08-05 00:00:00 UTC2026-08-06 00:00:00 UTC000
Aug 62026-08-06 00:00:00 UTC2026-08-07 00:00:00 UTC000
Aug 72026-08-07 00:00:00 UTC2026-08-08 00:00:00 UTC000
Aug 82026-08-08 00:00:00 UTC2026-08-09 00:00:00 UTC000
Aug 92026-08-09 00:00:00 UTC2026-08-10 00:00:00 UTC110
Aug 102026-08-10 00:00:00 UTC2026-08-11 00:00:00 UTC000
Aug 112026-08-11 00:00:00 UTC2026-08-12 00:00:00 UTC110

What Hacker News says

1 sources
yohji1984·Jul 25, 2026Submission

Why My Open-Source Project Hasn't Done Better

Since the beginning of 2026, many projects such as RTK, Caveman, and Ponytail have claimed that they can reduce token usage by 80–90%. Some of them gained tens of thousands of GitHub stars in a very short time. My previous startup was building an e-commerce chatbot. In fact, the product was almost identical to the Universal Commerce Protocol (UCP). After UCP was released, I decided not to continue pursuing that direction. Earlier this year, I started turning the architecture we had built for e-commerce chatbot agents into an SDK. Put simply, its core idea is to use state machines and deterministic execution sequences to reduce the number of round trips to LLM providers by around 80% for the same task, thereby significantly reducing token consumption. Here is the problem: I understand very clearly why tools such as RTK are ineffective in g
Read the rest
enuinely long-running tasks. I published a report on July 18, and JetBrains published a report on July 20 that reached essentially the same conclusion: token-saving plugins such as RTK and Caveman have little to no effect on real-world, long-running tasks. - JetBrains: https://blog.jetbrains.com/ai/2026/07/rtk-claude-code-token-savings/ - My report: https://turaai.net/blog#token-saving-plugins-are-mostly-stupid-idea I also know how to achieve a real reduction of more than 80% in token consumption during long-running tasks. However, I have encountered significant difficulties promoting my open-source project. I would summarize the main problems as follows. 1. Most coding-agent users do not care what actually drives token consumption There is a huge gap in understanding among coding-agent users, regardless of whether they have formal software-engineering training or are self-taught "vibe coders." A long article that systematically explains the process and challenges people's existing assumptions has very little chance of spreading in forums already flooded with AI-written posts and vibe-coded plugins claiming to reduce token usage by 95%. Simple ideas are easier to spread. People are not purely rational; they tend to believe the things they can understand most easily. That is also why pseudoscientific content built on incorrect causal explanations often attracts far more attention on social media than channels that carefully explain the underlying mathematics. 2. The author's arrogance This is really a combination of two problems. From the perspective of someone who believes strongly in scientific testing methods, evaluations, and benchmarks, software-engineering claims without an eval or benchmark can feel meaningless. But perhaps my own arrogance and my contempt for, or even jealousy of, tools such as RTK has made me less willing to promote my work in ways that would actually be more effective. If you have read this far, I would genuinely appreciate your advice: how can I promote my project more effectively while continuing to respect the rigor of evaluations and benchmarks? I know that building a coding agent with Codex or Claude is relatively easy. But I also believe that there will always be people who understand the value of benchmarks and evaluation harnesses. The project was released on July 16 and currently has a little over 400 GitHub stars. For now, it is still a relatively unknown project: https://github.com/Tura-AI/tura
4 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.