-
8추천Every framework becomes a debugging nightmare past 500 lines. Plain code + function calling has been better for us.
-
6추천Big claim. If real, this changes agent UX a lot. Anyone benchmarked it yet?
-
6추천Long agent sessions blow up tokens. Do you use summarization, sliding windows, or something else?
-
5추천Visual node editor for agent pipelines with live tracing. MIT licensed, would love feedback.
-
5추천I keep coming back to plain code + function calling. Frameworks add too much magic for debugging.
-
6추천이미지 링크Just got the email. Cache writes are 50% cheaper and cache reads dropped too. For anyone running long agent loops this is basically free money. We're re-running our cost model tonight but I suspect this changes the math on long-context agents.
-
5추천The agent handles maybe 60% of tickets but the 40% it hands to humans are the messy ones, so support load barely dropped. Customers who realize they're talking to a bot get annoyed even when it works. Not sure this was a win.
-
4추천I keep seeing MCP everywhere but every real deployment I've touched still uses plain REST under the hood. Is anyone running MCP servers in production with multiple clients? What's the actual win?
-
6추천Scrapes my git commits and PRs, summarizes them into 3 bullet points, emails them before standup. Takes 30 seconds of my morning. My manager thinks I'm extremely organized. I'm just lazy with extra steps.