bkotrys

6 ms·

1.
by bkotrys 5d ago
That’s a good example, I believe it could be similar case like with RAG. I didn’t hear for a while about any recommendations to use RAG.
2.
I wired 4 models together in Claude Code. It backfired 4 ways on Terminal-Bench(quesma.com)
7 points by bkotrys 1mo ago|1 comments
3.
Agentic coding costs in a nutshell: patterns, monitoring, metrics, optimization(github.com)
3 points by bkotrys 2mo ago|0 comments
4.
AI Tokenomics: What AI tokens cost and where they're wasted(github.com)
13 points by bkotrys 2mo ago|0 comments
5.
by bkotrys 2mo ago
Thanks, this looks useful. The subagent and tool-use breakdown is exactly the kind of visibility I was looking for. I will give it a try.
6.
by bkotrys 2mo ago
I don’t think subagents are the problem. Uncontrolled fan-out is. Separate contexts and independent analysis are extremely useful for larger tasks. In my experience, Pro is far too limited for sustained programming, although that probably d
7.
by bkotrys 2mo ago
The audit point is especially interesting. Is your Claude token-audit tool available anywhere?
8.
by bkotrys 2mo ago
Very similar experience. The review UI might actually be the most important part of the whole pipeline. Does the confidence ranking match what you end up rejecting?
9.
by bkotrys 2mo ago
At the shell level, the agent does not need to know about Bash. The contents of "$OUT" are passed to echo as one argument, then sent to claude-mem-save over stdin. Bash does not re-evaluate them as shell code. printf '%s\n&#x
10.
by bkotrys 2mo ago
That can work, especially for privacy or repetitive tasks. My experiment focused on subscriptions I already had, but local models are a natural addition to the routing layer.
11.
by bkotrys 2mo ago
Agreed. My goal is not fewer dead ends, but fewer repeated dead ends.
12.
by bkotrys 2mo ago
Thanks for sharing. That’s a very interesting direction. I will take a look.
13.
by bkotrys 2mo ago
Good point, thanks. Of course I was not able to fully eliminate hallucinations, but significantly reduce
14.
by bkotrys 2mo ago
looking promising, will give it a try! thanks for sharing
15.
by bkotrys 2mo ago
Try to mix both subscribtions and take the best from both providers. In my opinion, we should not just one over another but understand the power of both and mix them to reach the better results.
16.
by bkotrys 2mo ago
definitely something that will come sooner than later. In my view, adaption of model routing / model orchestration and mixing providers is just natural next step.
17.
by bkotrys 2mo ago
Yeah, that was pretty much my experience. The models weren’t lacking knowledge as much as discipline. Without a good workflow, they will most likely spend thousands of tokens exploring dead ends.
18.
by bkotrys 2mo ago
Thank you, glad you found the article useful!
19.
I burned all my tokens researching how to save tokens(quesma.com)
181 points by bkotrys 2mo ago|211 comments