HackerTrans
トップ新着トレンドコメント過去質問紹介求人

helsinki

no profile record

投稿

Show HN: An agent that detects YouTube brainrot and turns off my kid's TV

github.com
2 ポイント·投稿者 helsinki·3 か月前·0 コメント

Show HN: I built a pipeline that generates a comedy podcast end-to-end with AI

open.spotify.com
1 ポイント·投稿者 helsinki·4 か月前·0 コメント

Show HN: Gollem from Fugue Labs - A production-grade Go agent framework

github.com
1 ポイント·投稿者 helsinki·4 か月前·2 コメント

Show HN: Token Count – multi-agent AI comedy podcast with Temporal and GraphRAG

open.spotify.com
1 ポイント·投稿者 helsinki·6 か月前·0 コメント

Show HN: 100% Agentic AI Comedy Podcast

2 ポイント·投稿者 helsinki·6 か月前·0 コメント

コメント

helsinki
·2 か月前·議論
Some of us pay by the token.
helsinki
·4 か月前·議論
The best agent framework: https://github.com/fugue-labs/gollem
helsinki
·4 か月前·議論
That's why I added an invariant tool to my Go agent framework, fugue-labs/gollem:

https://github.com/fugue-labs/gollem/blob/main/ext/codetool/...
helsinki
·4 か月前·議論
I've been working on gollem — it's a Go agent framework with type-safe agents, structured output, multi-provider support (Anthropic, OpenAI, Gemini, Vertex AI), MCP integration, and multi-agent team swarms. The big idea is compile-time guarantees instead of runtime validation, zero core dependencies, and single-binary deploys. Think of it as what you'd want if you were building production agent systems in Go instead of Python.

To stress-test it I pointed it at a dumb task: generate an entire novel. It wrote ~40K words across 11 chapters in about 10 minutes. The "author-bot" uses gollem's agent primitives — chained agents for chapter planning, continuity checking, iterative drafting. Basically an orchestration.ChainRun pipeline where each stage feeds into the next.

The novel ("The Year Unedited" — dystopian memory-editing premise) came out surprisingly coherent. Characters kept distinct voices across chapters, the plot threads mostly held together, and it didn't just wrap everything up neatly at the end. Not saying it's good literature, but it's a decent stress test for long-running agent orchestration.

I threw it on Amazon mostly as an experiment: https://a.co/d/037EOH88

The framework itself is the actual point of this post though. It does cost tracking, guardrails, middleware chains, streaming with Go 1.23+ iterators, background process management, graph workflows, eval framework, the works. Happy to dig into any of the architecture details.
helsinki
·6 か月前·議論
Jump host with restricted commands / access. Agents SSH into a jump host and execute what they are allowed to execute.
helsinki
·7 か月前·議論
It has been in the source code for like two months. I've been using it for a while now.
helsinki
·7 か月前·議論
Can you invite me? In the off chance, my email is in my profile, but reversed.
helsinki
·8 か月前·議論
Yeah, makes perfect sense, but you really lose a lot.
helsinki
·9 か月前·議論
No, I don’t. I built it inside of my employer’s walls (hedge fund), so I’d have to rebuild it from scratch in order to acquire paying customers (not a bad idea).
helsinki
·9 か月前·議論
Social currency, I guess. I work on the AI team, so it’s just part of the job.
helsinki
·9 か月前·議論
I built a GitHub-native coding / review agent that outperforms CodeRabbit (by a lot), and it only took me like two hundred hours. There are a few of us using it at work, meanwhile CodeRabbit is valued at $550M.
helsinki
·9 か月前·議論
Would anyone at Google be willing to tell me how many people are working on this project? I’ve been building something functionally similar for my employer, but it’s a nights and weekends project with only one contributor (me).
helsinki
·10 か月前·議論
A cheese knife.
helsinki
·10 か月前·議論
How do you use two of these massive monitors? They are stacked vertically?
helsinki
·11 か月前·議論
I wonder how it’s different from using playwright MCP? The prompts and screenshots, I guess?
helsinki
·11 か月前·議論
I think that’s a decent approach, but doesn’t the performance of a Neovim terminal bother you? It simply does not feel as good as a native terminal pane. It’s not as bad as VSCode’s terminal pane, but it still leaves something to be desired.
helsinki
·11 か月前·議論
It’s more common that they lead technological advancements in IDEs, not follow. Neovim in particular.