frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Poddley.com – Follow people, not podcasts

https://poddley.com/guests/ana-kasparian/episodes
1•onesandofgrain•57s ago•0 comments

Layoffs Surge 118% in January – The Highest Since 2009

https://www.cnbc.com/2026/02/05/layoff-and-hiring-announcements-hit-their-worst-january-levels-si...
2•karakoram•1m ago•0 comments

Papyrus 114: Homer's Iliad

https://p114.homemade.systems/
1•mwenge•1m ago•1 comments

DicePit – Real-time multiplayer Knucklebones in the browser

https://dicepit.pages.dev/
1•r1z4•1m ago•1 comments

Turn-Based Structural Triggers: Prompt-Free Backdoors in Multi-Turn LLMs

https://arxiv.org/abs/2601.14340
2•PaulHoule•2m ago•0 comments

Show HN: AI Agent Tool That Keeps You in the Loop

https://github.com/dshearer/misatay
2•dshearer•4m ago•0 comments

Why Every R Package Wrapping External Tools Needs a Sitrep() Function

https://drmowinckels.io/blog/2026/sitrep-functions/
1•todsacerdoti•4m ago•0 comments

Achieving Ultra-Fast AI Chat Widgets

https://www.cjroth.com/blog/2026-02-06-chat-widgets
1•thoughtfulchris•6m ago•0 comments

Show HN: Runtime Fence – Kill switch for AI agents

https://github.com/RunTimeAdmin/ai-agent-killswitch
1•ccie14019•8m ago•1 comments

Researchers surprised by the brain benefits of cannabis usage in adults over 40

https://nypost.com/2026/02/07/health/cannabis-may-benefit-aging-brains-study-finds/
1•SirLJ•10m ago•0 comments

Peter Thiel warns the Antichrist, apocalypse linked to the 'end of modernity'

https://fortune.com/2026/02/04/peter-thiel-antichrist-greta-thunberg-end-of-modernity-billionaires/
1•randycupertino•11m ago•2 comments

USS Preble Used Helios Laser to Zap Four Drones in Expanding Testing

https://www.twz.com/sea/uss-preble-used-helios-laser-to-zap-four-drones-in-expanding-testing
2•breve•16m ago•0 comments

Show HN: Animated beach scene, made with CSS

https://ahmed-machine.github.io/beach-scene/
1•ahmedoo•17m ago•0 comments

An update on unredacting select Epstein files – DBC12.pdf liberated

https://neosmart.net/blog/efta00400459-has-been-cracked-dbc12-pdf-liberated/
1•ks2048•17m ago•0 comments

Was going to share my work

1•hiddenarchitect•20m ago•0 comments

Pitchfork: A devilishly good process manager for developers

https://pitchfork.jdx.dev/
1•ahamez•20m ago•0 comments

You Are Here

https://brooker.co.za/blog/2026/02/07/you-are-here.html
3•mltvc•25m ago•1 comments

Why social apps need to become proactive, not reactive

https://www.heyflare.app/blog/from-reactive-to-proactive-how-ai-agents-will-reshape-social-apps
1•JoanMDuarte•25m ago•1 comments

How patient are AI scrapers, anyway? – Random Thoughts

https://lars.ingebrigtsen.no/2026/02/07/how-patient-are-ai-scrapers-anyway/
1•samtrack2019•26m ago•0 comments

Vouch: A contributor trust management system

https://github.com/mitchellh/vouch
2•SchwKatze•26m ago•0 comments

I built a terminal monitoring app and custom firmware for a clock with Claude

https://duggan.ie/posts/i-built-a-terminal-monitoring-app-and-custom-firmware-for-a-desktop-clock...
1•duggan•27m ago•0 comments

Tiny C Compiler

https://bellard.org/tcc/
1•guerrilla•28m ago•0 comments

Y Combinator Founder Organizes 'March for Billionaires'

https://mlq.ai/news/ai-startup-founder-organizes-march-for-billionaires-protest-against-californi...
1•hidden80•29m ago•2 comments

Ask HN: Need feedback on the idea I'm working on

1•Yogender78•29m ago•0 comments

OpenClaw Addresses Security Risks

https://thebiggish.com/news/openclaw-s-security-flaws-expose-enterprise-risk-22-of-deployments-un...
2•vedantnair•30m ago•0 comments

Apple finalizes Gemini / Siri deal

https://www.engadget.com/ai/apple-reportedly-plans-to-reveal-its-gemini-powered-siri-in-february-...
1•vedantnair•30m ago•0 comments

Italy Railways Sabotaged

https://www.bbc.co.uk/news/articles/czr4rx04xjpo
9•vedantnair•31m ago•2 comments

Emacs-tramp-RPC: high-performance TRAMP back end using MsgPack-RPC

https://github.com/ArthurHeymans/emacs-tramp-rpc
1•fanf2•32m ago•0 comments

Nintendo Wii Themed Portfolio

https://akiraux.vercel.app/
2•s4074433•36m ago•2 comments

"There must be something like the opposite of suicide "

https://post.substack.com/p/there-must-be-something-like-the
1•rbanffy•39m ago•1 comments
Open in hackernews

Show HN: IncidentFox – open-source AI SRE with log sampling and RAPTOR retrieval

https://github.com/incidentfox/incidentfox
1•chiehminwei•2w ago
Hi HN, I’m Jimmy.

We open-sourced the core of IncidentFox, an AI SRE / on-call agent.

The main thing we’re working on is handling context for incident investigation. Logs, metrics, traces, runbooks, prior incidents — this data is large, fragmented, and doesn’t fit cleanly into an LLM context window.

For logs, we don’t fetch everything. We start with stats (counts, severity distribution, common patterns) and then sample intentionally (errors-only, around-anomaly, stratified). Most investigations end up with tens of logs instead of millions.

For long documents like runbooks or postmortems, flat chunk-based RAG wasn’t working well, so we implemented a RAPTOR-style hierarchical retrieval to preserve higher-level context while still allowing drill-down.

The open-source core is a tool-based agent runtime with integrations. You can run it locally via CLI (or Slack/ GitHub), which is effectively on-prem on your laptop.

We’re very early and trying to find our first users / customers. If you’ve been on call before, I’m curious:

- does “AI SRE” feel useful, or mostly hype?

- where would something like this actually help, if at all?

- what would you want it to do before you’d trust it?

If you try it and it’s not useful, that’s still helpful feedback. I’ll be around in the comments!

Comments

incidentiq•2w ago
Been on-call across several orgs. To answer your questions:

1. "AI SRE" useful or hype? Useful in specific contexts, but the trust barrier is real. Most on-call engineers are skeptical of AI suggestions during incidents because the cost of a wrong recommendation at 3am is high. That said, the pain of digging through logs and finding relevant context is also real.

2. Where it helps: The biggest wins are in "pre-work" - surfacing relevant past incidents before you start investigating, correlating alerts that are likely related, and summarizing what changed recently. Reducing the "context gathering" phase which often eats 30%+ of incident time.

3. Trust requirements: For me to trust it: - Show confidence levels and your reasoning. "Here's what I found and why" beats "do this." - Be a copilot that accelerates my investigation, not one that acts on my behalf. - Get the easy stuff 100% right before attempting the hard stuff. If log correlation is wrong on obvious patterns, I won't trust root cause suggestions.

The RAPTOR approach for runbooks is interesting - the "loss of context in chunked RAG" problem is real for long-form incident docs. How do you handle cases where relevant context spans multiple documents (runbook references an architecture doc)?