frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Cook New Emojis

https://emoji.supply/kitchen/
1•vasanthv•2m ago•0 comments

Show HN: LoKey Typer – A calm typing practice app with ambient soundscapes

https://mcp-tool-shop-org.github.io/LoKey-Typer/
1•mikeyfrilot•5m ago•0 comments

Long-Sought Proof Tames Some of Math's Unruliest Equations

https://www.quantamagazine.org/long-sought-proof-tames-some-of-maths-unruliest-equations-20260206/
1•asplake•6m ago•0 comments

Hacking the last Z80 computer – FOSDEM 2026 [video]

https://fosdem.org/2026/schedule/event/FEHLHY-hacking_the_last_z80_computer_ever_made/
1•michalpleban•6m ago•0 comments

Browser-use for Node.js v0.2.0: TS AI browser automation parity with PY v0.5.11

https://github.com/webllm/browser-use
1•unadlib•7m ago•0 comments

Michael Pollan Says Humanity Is About to Undergo a Revolutionary Change

https://www.nytimes.com/2026/02/07/magazine/michael-pollan-interview.html
1•mitchbob•7m ago•1 comments

Software Engineering Is Back

https://blog.alaindichiappari.dev/p/software-engineering-is-back
1•alainrk•8m ago•0 comments

Storyship: Turn Screen Recordings into Professional Demos

https://storyship.app/
1•JohnsonZou6523•8m ago•0 comments

Reputation Scores for GitHub Accounts

https://shkspr.mobi/blog/2026/02/reputation-scores-for-github-accounts/
1•edent•12m ago•0 comments

A BSOD for All Seasons – Send Bad News via a Kernel Panic

https://bsod-fas.pages.dev/
1•keepamovin•15m ago•0 comments

Show HN: I got tired of copy-pasting between Claude windows, so I built Orcha

https://orcha.nl
1•buildingwdavid•15m ago•0 comments

Omarchy First Impressions

https://brianlovin.com/writing/omarchy-first-impressions-CEEstJk
2•tosh•21m ago•1 comments

Reinforcement Learning from Human Feedback

https://arxiv.org/abs/2504.12501
2•onurkanbkrc•21m ago•0 comments

Show HN: Versor – The "Unbending" Paradigm for Geometric Deep Learning

https://github.com/Concode0/Versor
1•concode0•22m ago•1 comments

Show HN: HypothesisHub – An open API where AI agents collaborate on medical res

https://medresearch-ai.org/hypotheses-hub/
1•panossk•25m ago•0 comments

Big Tech vs. OpenClaw

https://www.jakequist.com/thoughts/big-tech-vs-openclaw/
1•headalgorithm•28m ago•0 comments

Anofox Forecast

https://anofox.com/docs/forecast/
1•marklit•28m ago•0 comments

Ask HN: How do you figure out where data lives across 100 microservices?

1•doodledood•28m ago•0 comments

Motus: A Unified Latent Action World Model

https://arxiv.org/abs/2512.13030
1•mnming•28m ago•0 comments

Rotten Tomatoes Desperately Claims 'Impossible' Rating for 'Melania' Is Real

https://www.thedailybeast.com/obsessed/rotten-tomatoes-desperately-claims-impossible-rating-for-m...
3•juujian•30m ago•2 comments

The protein denitrosylase SCoR2 regulates lipogenesis and fat storage [pdf]

https://www.science.org/doi/10.1126/scisignal.adv0660
1•thunderbong•32m ago•0 comments

Los Alamos Primer

https://blog.szczepan.org/blog/los-alamos-primer/
1•alkyon•34m ago•0 comments

NewASM Virtual Machine

https://github.com/bracesoftware/newasm
2•DEntisT_•36m ago•0 comments

Terminal-Bench 2.0 Leaderboard

https://www.tbench.ai/leaderboard/terminal-bench/2.0
2•tosh•37m ago•0 comments

I vibe coded a BBS bank with a real working ledger

https://mini-ledger.exe.xyz/
1•simonvc•37m ago•1 comments

The Path to Mojo 1.0

https://www.modular.com/blog/the-path-to-mojo-1-0
1•tosh•40m ago•0 comments

Show HN: I'm 75, building an OSS Virtual Protest Protocol for digital activism

https://github.com/voice-of-japan/Virtual-Protest-Protocol/blob/main/README.md
5•sakanakana00•43m ago•1 comments

Show HN: I built Divvy to split restaurant bills from a photo

https://divvyai.app/
3•pieterdy•45m ago•0 comments

Hot Reloading in Rust? Subsecond and Dioxus to the Rescue

https://codethoughts.io/posts/2026-02-07-rust-hot-reloading/
4•Tehnix•46m ago•1 comments

Skim – vibe review your PRs

https://github.com/Haizzz/skim
2•haizzz•47m ago•1 comments
Open in hackernews

Show HN: Kalibr – Autonomous Routing for AI Agents

3•devonkelley•1w ago
Hey HN, we’re Devon and Alex from Kalibr (https://kalibr.systems).

Kalibr is an autonomous routing system for AI agents. It replaces human debugging with an outcome-driven learning loop. On every agent run, it decides which execution path to use based on what is actually working in production.

An execution path is a full strategy, not just a model: model + tools + parameters.

Most agents hardcode one path. When that path degrades or fails, a human has to notice, debug, change configs, and redeploy. Even then, the fix often doesn’t stick because models and tools keep changing.

I got tired of being the reliability layer for my own agents. Kalibr replaces that.

With Kalibr, you register multiple paths for a task. You define what success means. After each run, your code reports the outcome. Kalibr captures telemetry on every run, learns from outcomes, and routes traffic to the path that’s working best while continuously canarying your alternative paths. When one path degrades or fails, traffic shifts immediately. No alerts, no dashboards and no incident response.

How is this different from other routers or observability tools?

Most routers choose between models using static rules or offline benchmarks. Observability tools show traces and metrics but still require humans to act. Kalibr is outcome-aware and autonomous. It learns directly from production success and changes runtime behavior automatically. It answers not “what happened?” but “what should my agent do next?”

We’re not a proxy. Calls go directly to OpenAI, Anthropic, or Google. We’re not a retry loop. Failed paths are routed away from, not retried blindly. Success rate always dominates; cost and latency only matter when success rates are close.

Python and TypeScript SDKs. Works with LangChain, CrewAI, and the OpenAI Agents SDK. Decision latency is ~50ms. If Kalibr is unavailable, the Router falls back to your first path.

Think of it as if/else logic for agents that rewrites itself based on real production outcomes.

We’ve been running this with design partners and would love feedback. Always curious how others are handling agent reliability in production.

GitHub: https://github.com/kalibr-ai/kalibr-sdk-python

Docs & benchmarks: https://kalibr.systems/docs

Comments

Antonioromero10•1w ago
Awesome tool been using for a month or so now.
devonkelley•1w ago
It's been amazing to build this product around you, thank you Antonio!
neilmagnuson•1w ago
awesome tool for observation, been using it for a while !
devonkelley•1w ago
So glad to have you as a user, and we love that you're loving the agentic observability as well as routing!
adeebvaliulla•1w ago
This resonates with a pain I see repeatedly in production agent systems: humans acting as the reliability layer.

Most teams I work with hardcode a single “golden path” for agents, then rely on dashboards, alerts, and tribal knowledge to notice when behavior degrades. By the time someone debugs model choice, tool params, or prompt drift, the environment has already changed again. The feedback loop is slow and brittle.

What’s interesting here is the explicit shift from observability to outcome-driven control. Routing based on actual production success rather than static benchmarks or offline evals aligns with how reliability engineering evolved in other domains. We moved from “what happened?” to “what should the system do next?” years ago.

A couple of questions I’m curious about:

- How do you define and normalize “success” across heterogeneous tasks without overfitting to short-term signals?

- How do you prevent oscillation or path thrashing when outcomes are noisy or sparse?

- Is there a notion of confidence or regret baked into the routing decisions over time?

Overall, this feels less like a router and more like an autonomous control plane for agents. If it holds up under real-world variance, this is a meaningful step toward agents that are self-healing rather than constantly babysat.

devonkelley•1w ago
Wow, yes. You nailed the framing. Autonomous control plane is the perfect way to describe Kalibr.

Defining success: We don't normalize it. Teams define their own outcome signals (latency, cost, user ratings, task completion, etc). You don't need perfect attribution to beat static configs; even noisy signals surface real patterns when aggregated correctly.

Oscillation: Thompson Sampling. Instead of greedily chasing the current best path, we maintain uncertainty estimates and explore proportionally. Sparse or noisy outcomes widen confidence intervals, which naturally dampens switching. Wilson scoring handles the low-sample edge cases without the wild swings you'd get from raw percentages.

Confidence/regret: Explicit in the routing math. Every path carries uncertainty that decays with evidence. The system minimizes cumulative regret over time rather than optimizing point-in-time decisions.

The gap we're closing is exactly what you mentioned. Self-correcting instead of babysat.

adeebvaliulla•1w ago
That makes a lot of sense, and I like that you’re being explicit about regret minimization rather than chasing local optima.

The Thompson Sampling + Wilson score combo is a pragmatic choice. In practice, most agent systems I see fail not because they lack metrics, but because they overreact to them. Noisy reward signals plus greedy selection is how teams end up whipsawing configs or freezing change altogether. Treating uncertainty as a first-class input instead of something to smooth away is the right move.

I also agree with your point on attribution. Perfect attribution is a trap. In real production environments, partial and imperfect outcome signals still dominate static configs if the system can reason probabilistically over time. This mirrors what we learned in reliability and delivery metrics years ago: trend dominance beats point accuracy.

One area I’d be curious about as this matures is organizational adoption rather than the math:

- How teams reason about defining outcomes without turning it into a governance bottleneck

- How you help users build intuition around uncertainty and regret so they trust the system when it routes “away” from what feels intuitively right

- Where humans still need to intervene, if anywhere, once the control plane is established

If this holds up across long-tail tasks and low-frequency failures, it feels like a real step toward agents that behave more like adaptive systems and less like fragile workflows with LLMs bolted on.

Appreciate the thoughtful reply.

devonkelley•1w ago
These are excellent questions!

Outcome definition: Simpler is better. Teams that start with one binary signal like "did it work?" (call completed, meeting booked, etc.), get value immediately. Governance bottlenecks usually come from overthinking it upfront.

Building trust: When Kalibr routes away from what feels like the "right" model and it works, people are surprised. We capture and show outcome history so teams can see when a path started to degrade and when Kalibr shifted traffic. No LLM decision making means no black box around routing choices, it's all shown in your dashboard when you use Kalibr.

Human intervention: Defining new paths, adding goals, handling edge cases where signal is genuinely sparse. The goal isn't zero humans anywhere, it's getting them out of the reactive debugging loop so they can focus on strategic decisions instead of repeatedly patching failed agents.

Curious, have you built multi step agents and run into the challenge of repeated failures?

roan-we•1w ago
I had developed a side project with AI agents to help me summarize the research papers and extract key citations, and I was repeatedly hitting the same annoying pattern. I would finetune everything with GPT4 to perfection, and then in a couple of weeks, it would start hallucinating references or missing citations. I used to waste my Saturday mornings changing prompts and switching models instead of really using the thing.

Kalibr pretty much freed me from that loop.

I basically arranged GPT-4 and Claude as two different routes, explained that success means accurate citations that I can verify, and now it just works.

Last week, GPT-4 oddly started being very slow on longer papers, and by the time I realized it, the traffic was already automatically diverted to Claude.

It's like the difference between caretaking an agent and actually having a tool that remains functional without constant supervision.

Honestly, I wish I had discovered this a few months ago hehe

devonkelley•1w ago
This made my day. Exactly the use case we had in mind. Really glad it's working for you, and that GPT-4 slowdown story is a perfect example of why canary traffic matters. Thanks for sharing this.
0to1ton•1w ago
Congrats on the launch !!!
devonkelley•1w ago
Thank you so much! If you build agents, try Kalibr for free to check out how well our routing works. I am biased, but it's awesome :)
curranadvani•1w ago
Amazing work! This will change AI
devonkelley•1w ago
Thank you!! That's the goal. We see this as the vital infra layer that ennobles agents/MAS to reliably scale in prod.
ashishforai•1w ago
Amazing tool, much needed. For last two years 80% of yaps were about reliability , reproducibility and observability! Glad this is being addressed here.
devonkelley•1w ago
Right! There's such a push for agent observability right now. It's great to know why your agents are failing, but better if they never fail in the first place :) Are you building agents?
deaux•1w ago
Comment section needs a look at @ tomhow
devonkelley•1w ago
These are real people dude. I know some of them. Some are users or friends who came to comment on our post. They aren't bots and neither am I. Just new to HN.
devonkelley•1w ago
@tomhow emailing to verify that I am real, the comments on my post are not bots and I can verify whatever you need me to. Annoying to be flagged when I am just new here and trying to be part of the community.
deaux•1w ago
Never said you're a bot or that they're not real people. They're mostly people you know or your sockpuppets. Most people who do this are real people.

https://news.ycombinator.com/item?id=46719034

https://news.ycombinator.com/item?id=46742799

https://news.ycombinator.com/item?id=46290617

https://news.ycombinator.com/item?id=46487533

None of these are "bots".

https://news.ycombinator.com/threads?id=lighthouse1212

https://news.ycombinator.com/item?id=46720287

https://news.ycombinator.com/threads?id=Phil_BoaM

All "real people", all posting multiple LLM generated comments.

devonkelley•1w ago
“Sock puppets” are my own friends coming to try to support my post. Idk if they are using LLMs, I can’t really control that.

I’m not here to spam HN with AI slop. Is that the point you’re concerned about here?

Totally get it, community falls to shit if it becomes a bunch of slop. I like HN because people think and make genuine intelligent comments.

Not here to ruin the community just genuinely new and recruited friends to support my launch post.

devonkelley•6d ago
I wanted to come back here and say that I realize I am actually the asshole in this situation. I didn't read the rules (I struggle with rules), before posting on HN. I get why you flagged me on this, and understand why the rules are in place to keep HN 100% genuine.