Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
AlexCalderAI
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
AlexCalderAI
7mo ago
Really nice approach. Running parallel agents is the obvious next step after single-agent works, but the coordination + cost tracking becomes the blocker. One thing I'd add: make cost-per-agent visibility mandatory from day one. When y
2.
▲
by
AlexCalderAI
7mo ago
When you're running multiple Claude Code agents (or even just one agent working on complex problems), this task scattering is real. We solve it differently—all agent state lives in markdown files + git history. Simpler than MCP, more t
3.
▲
by
AlexCalderAI
7mo ago
Solid patterns here. One thing I'd add from running Claude Code in production: The "give it bash" pattern sounds scary until you realize the alternative is 47 intermediate tool calls that fail silently. Letting the agent writ
4.
▲
by
AlexCalderAI
7mo ago
Nice approach to the per-key cost cap problem. We built something similar for tracking AI spend across providers - the "one forgotten loop" scenario is real and expensive. The JSON-on-disk pattern works surprisingly well for this
5.
▲
by
AlexCalderAI
7mo ago
Great patterns here. I'd add one more critical layer that many miss: orchestration state management. Running multiple agents concurrently (QA, content, conversions, distribution), we hit this exact wall - agents didn't know what o
6.
▲
by
AlexCalderAI
7mo ago
I solve this exact problem running OpenClaw (24/7 agent orchestrator). Here's what actually works after months of iteration: The core insight: Multiple agents with zero shared state = chaos. Solution: State files are your control
7.
▲
by
AlexCalderAI
7mo ago
This is exactly the problem most agent builders hit around turn 10-15. Simple system_prompt + conversation_history patterns work for a few turns, then context drift happens. The 5-layer approach (chunk → embed → retrieve → rank → synthesize
8.
▲
by
AlexCalderAI
7mo ago
Fair question @verdverm! You absolutely could build this yourself. Same reason people use any open source tool instead of writing their own - it's already built, tested, and you can ship your actual project instead. If your AI outputs
9.
▲
Show HN: Token Cost Guard – Track AI API Costs Locally (Python CLI)
(github.com)
1 points
by
AlexCalderAI
7mo ago
|
2 comments