How Stripe Built Kai on Deep Agents in 1 Week
Learn how Stripe built Kai, a company-wide AI agent on LangChain, LangGraph, and Deep Agents, reaching 5,000 users in roughly 4 weeks.
Search headlines, summaries and articles to connect the dots.
Learn how Stripe built Kai, a company-wide AI agent on LangChain, LangGraph, and Deep Agents, reaching 5,000 users in roughly 4 weeks.
Article URL: https://www.sandromaglione.com/articles/indie-game-development-with-ai Comments URL: https://news.ycombinator.com/item?id=50432523 Points: 22 # Comments: 16
Article URL: https://github.com/tombaldwin/agentlink Comments URL: https://news.ycombinator.com/item?id=50439846 Points: 1 # Comments: 0
Hello thereI built a little Chrome extension that analyzes the content elements on a page, scores their "usefulness" and labels them based on that score. What counts as useful can be customized to your preferences and interests, and it learns from your feedback on the scores.Each element gets a badge with its score; hover it for more details.I'm using Jev, so the basic analysis is very fast and very cheap. You need to add your Jev key and run the small local bridge (it's in the repo).For deeper analysis (e.g. a pareto summary) you bring your preferred AI key.Chrome Web Store: https://chromewebstore.google.com/detail/emjbfdcigbfojhdipap... Comments URL: https://news.ycombinator.com/item?id=50435166 Points: 1 # Comments: 1
Article URL: https://github.com/XahidEx/DayBreak Comments URL: https://news.ycombinator.com/item?id=50438403 Points: 2 # Comments: 0
Article URL: https://github.com/s-nish/desk Comments URL: https://news.ycombinator.com/item?id=50430522 Points: 1 # Comments: 0
Article URL: https://github.com/alt-f6/pg-interleave Comments URL: https://news.ycombinator.com/item?id=50437720 Points: 1 # Comments: 0
Article URL: https://github.com/Yuix-Networks/claude-orchestrator Comments URL: https://news.ycombinator.com/item?id=50437743 Points: 1 # Comments: 0
8 Months ago I made this post https://news.ycombinator.com/item?id=47123894Since then we've done stuff, the software is much more mature, we've done some basic field testing on small dev platforms.We've moved from ESP32 for the microcontroller to a STM32.Volunteers have come, gone again, new ones arrived.We're getting ready for full scale field trials now.Been putting some videos of sim up on https://www.youtube.com/@rosmo-robot/videosPlease critique again, and come join us! Comments URL: https://news.ycombinator.com/item?id=50437978 Points: 1 # Comments: 1
Article URL: https://github.com/willderai/willder-core Comments URL: https://news.ycombinator.com/item?id=50436876 Points: 2 # Comments: 0
arXiv:2611.08644v1 Announce Type: new Abstract: LLM agents do not learn from corrections across sessions. A user fixes the same mistake at the start of every conversation. Existing agent memory systems primarily handle facts, such as preferences, entities, and conversational history, rather than procedural knowledge. We present Forge Decision Context (forge_dc), a system that captures behavioral signals from human corrections and self-assessed tool-call failures, compiles them into imperative RULE directives, and injects them at the decision points where they apply. We evaluate forge_dc alongside four predecessor approaches on DC-Bench, a new benchmark of 71 scenarios across nine behavioral dimensions, built from real executed agent traces in a deterministic mocked-tool environment. forge_dc reaches 95% compliance, up from 55% with naive retrieval, while injecting approximately 10 times fewer tokens per query. Across the five-stage progression, the strongest systems represent behavioral memory as explicit directives and deliver it at the decision points where it applies. The results identify representation, activation, and placement as central design choices for persistent behavioral learning.
arXiv:2611.08902v1 Announce Type: new Abstract: Prefix caching lets an LLM agent's follow-up turns reuse cached KV, but a burst can tip an engine into a trap in which every turn misses and the backlog does not drain, at a load it served before. In registered paired tests on two engines, two GPUs and two models (passed at 9 of 10 rates), a 200-session burst left the engine at zero hits to the end in all 30 runs, while every matched no-burst run stayed good and a session cap prevented the trap in all 30 capped runs. We analyse an idealization of the trapped state exactly: for a fluid FIFO server on which every turn misses, we prove that along FIFO orbits its cycles obey a linear renewal recursion. As is classical, the trap drains if and only if arrivals are below the all-miss capacity; above it, a Perron root fixes the dynamics: every trapped state converges to a known self-similar regime in which the gap between turns grows linearly and the turns served are young and short. For our workload the backlog grows at 0.6 to 0.8 of the excess load and sessions complete faster than the all-miss capacity, a youth premium with turn-count and cost-growth factors, so in the model a trap's measured throughput overstates the recovery threshold. Retrospectively, with nothing fitted to trap data, the theory matches 57 stuck runs: the mean served prompt within 3% in 50 runs, completions above the all-miss capacity in every run, and the pooled gap growth. Blind in outcome, 4 runs trapped by a tool slowdown met 4 of 5 pre-set scores, cut traps persisted, and with a 20-step budget, trapped runs completed below the all-miss capacity, as predicted. Of two exits, refusing arrivals sheds sessions; a session cap restores reuse: in registered tests it rescued 9 of 9 established traps at the same load without shedding, and the engine stayed good after release. We do not prove that the engine converges to the model.
Article URL: https://orbtile.com/tools/claude-code-statusline-builder Comments URL: https://news.ycombinator.com/item?id=50415399 Points: 1 # Comments: 0
Hi, Dmitri from Radioso here, an open-source platform to design AI agents for customers and visitors in any channel, in the style of Fin/Ada/Decagon. The repo is https://github.com/radioso-ai/radioso and our website is https://radioso.aiToday, your choices are:1. Buy a very expensive service for your vertical (usually starting with $$ five figures monthly) 2. Get a cheap off-the-shelf chatbot that mostly answers FAQs 3. Build your own, and then also build the inbox, human handoff, audit trail and integrations around itAt Radioso we wanted an open-source option that combines the best of all 3. You can integrate it with your own software via API/SDK or your CRM, or run it standalone, either self-hosted or in our cloud.The engine runs multi-step interactions and takes actions: calling your APIs, updating records, booking things. Maybe you’ve tried Parlant; Radioso is the alternative “with batteries included”: RAG, audit trail, customer service inbox, and integrations like Slack and email.Under the hood it’s plain TypeScript + PostgreSQL, works with OpenAI/Anthropic/other models, and is licensed under Apache 2.0 which includes all features (The only thing we keep under EE license is the multi-tenant layer we use to run our own cloud).We have existing customers running it for technical Q&A, course booking, online product recommendations and goods returns, among others, some reaching 92% of conversations automated. We’re currently working on voice support so we can offer a call center.Our ambition is to be “the WordPress of customer-facing AI” :), where people can contribute their favorite plugins and benefit from the ecosystem.Longer term, we think browsing the web will mostly mean talking to your own agent, and when you need a service or a purchase, your agent will talk to the vendor’s agent to get things done. For this, Radioso already publishes an A2A Agent Card and we’re working on the rest. Your Radioso services are also callable over MCP, for customers who already use it.Thanks for your attention. We’d especially love to hear which integrations you’d want, whether you’d self-host it, and what’s stopped you from deploying a customer-facing AI agent so far. Tell us what you think. Comments URL: https://news.ycombinator.com/item?id=50423820 Points: 1 # Comments: 0
Article URL: https://github.com/dooly6276/claude-bulkhead Comments URL: https://news.ycombinator.com/item?id=50419582 Points: 2 # Comments: 0
Article URL: https://www.sketchycraft.com/ Comments URL: https://news.ycombinator.com/item?id=50426495 Points: 2 # Comments: 0
Article URL: https://github.com/wainmann/agent-manager Comments URL: https://news.ycombinator.com/item?id=50406983 Points: 3 # Comments: 0
Article URL: https://github.com/volcengine/OpenViking Comments URL: https://news.ycombinator.com/item?id=50410477 Points: 1 # Comments: 1
Article URL: https://github.com/alielmorsy/ywza Comments URL: https://news.ycombinator.com/item?id=50408730 Points: 1 # Comments: 0
You can now manage GitHub Copilot code review settings through the REST and GraphQL APIs, from enterprise policy down to individual repositories. Copilot’s review overview comment is now more compact,… The post Copilot code review: API management and review overview updates appeared first on The GitHub Blog.