Skip to content
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

Korea Advances Physical AI Across Industries With NVIDIA

Tapping into the country’s strengths in manufacturing and engineering, NVIDIA is helping advance Korea’s physical AI ecosystem. The country’s industry leaders are applying accelerated computing, AI and simulation to everything from semiconductor manufacturing to robotics and autonomous vehicles. These efforts are helping bring physical AI from development into real-world production. Samsung Advances Semiconductor Engineering With […]

Show HN: Control Layer Demo for AI Coding Agents

Letting coding agents (such as Claude Code) work autonomously on repos on a daily-basis, brings a high level of uncertainty. For those who won't let the agent decide alone whether it can create/modify or delete any folder on their repos; I wanted to be able to trace actions performed and being able to let the agent continue his work autonomously, or ask him to request a human approval according to some criteria defined. After investigations, the cleanest way to do it was according to me to develop a deterministic control layer between the LLM and the work of the agent that would track and catch potential non-respect of pre-defined rules. How? by first setting up approval rules (Pass/requires approval/refused) before the work of the agent, and afterwards controlling cryptographic SHA 256 verifications, etc. This allows to compare the before-after work of the agent. I have put in my public GitHub repo a demo that you can launch easily and observe different scenarios behaviors like applied authorized modification, protected file waiting for Human approval, or outside perimeter authorization modification refused. The demo is offline, does not involve the official runtime, in native node.js and without dependencies. It should still allow you to understand the core principles. I would like to know: how do you implement and handle safety boundaries? Especially if you let agents work on critical data/sensitive codebases? With which guardrails? Comments URL: https://news.ycombinator.com/item?id=50422833 Points: 1 # Comments: 0

Show HN: FELF – AppImage-like single binaries without FUSE, root, or a runtime

Hello HN!I've always had a bad time redistributing programs that use shared libraries, AppImage in my opinion does too much, and a container is an overkill - not always integrates smoothly.I've moved to nix since long ago, but redistributing between nix and other distros or vice versa it's still a pain in the ass, more so if you want to run an alien app in nix or a nix app without the package manger in any other distro.For that, with the help of Claude, I've implemented a format that deduces at pack-time all the shared libraries a program needs, puts them, together with its own glibc and a patched dynamic linker into a single executable.This means that you don't actually need a runtime nor any special capability, it can run inside a FROM SCRATCH docker, alpine linux etc... And it also supports coreutils-like multiple programs accessible via symlinks, so it is a good fit for that purpose.You can just use:> felf pack $(which git) --output git.felfand you'll have already a git binary that works everywhere, no matter which distro you are building this from. This only packs the binary and their dependencies.Essentially, the effect is similar as if you LD_PRELOAD's all the libraries that it requires.In the end, we have been fighting these demons since long long ago, chroots/docker/appimage/flatpack/nix etc...So this xkcd applies: https://xkcd.com/927/I'm happy to share the project, I hope it inspires new discoveries/tools in this regard! Comments URL: https://news.ycombinator.com/item?id=50415219 Points: 2 # Comments: 0

Show HN: Open-source customer-facing agents

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

Show HN: Pgxio – a tiny PostgreSQL layer inside Nginx

I built the first version of this stuff a decade ago as ethanolus (c2h5oh). And I've used it for most of my projects as a backend layer since then.The main motive is to eliminate unnecessary complexity from backend layers.How it works: a rust nginx module calls postgresql functions via non-blocking libpq io. There is an optional patch for libpq. It provides zero-copy for nginx-chained memory buffers - to avoid request body copies between nginx and libpq.Pgxio supports http2 and websockets. Realtime listen/notify updates from postgres without polling.How to try - code on github. Tested on Debian - FreeBSD validation in progress.It's alpha - so any feedback is welcome. Comments URL: https://news.ycombinator.com/item?id=50425203 Points: 1 # Comments: 0

Show HN: Record, branch, and compare command runs in stdlib-only Python

Hi, this is a package I developed for keeping track of short toy-model development cycles and explaining what changed between runs.The core idea: commands run through the package, and their declared parameters (or injected parameters with --substitute) and outcomes go into a dependency-free ledger stored in the project. Because that ledger lives in the project directory, it has worked well for passing context between different agents. I’ve also found some use for it in CI work. Comments URL: https://news.ycombinator.com/item?id=50417782 Points: 3 # Comments: 0

Your Experts Have Partners. There's HOPE for Keeping Them Together

HOPE, a second-order expert pruning method for Mixture-of-Experts (MoE) language models, accounts for pairwise expert interactions by optimizing a quadratic program based on an interaction matrix derived from calibration data. Unlike first-order methods that prune experts independently, HOPE preserves cooperative expert groups, leading to better performance—especially at high pruning rates like 50%. On benchmarks such as SWE-Bench Pro, HOPE outperforms state-of-the-art first-order methods like REAP by up to +6.1%, maintaining model quality while significantly reducing memory footprint. The method requires only a single calibration pass and efficient quadratic programming, with negligible overhead. It has been validated on Qwen3.5 and GLM-4.5 models, showing consistent improvements across diverse tasks and calibration sets.

Show HN: Neural Network Formal Verification

Article URL: https://github.com/giovanni-norbedo/awesome-nn-formal-verification Comments URL: https://news.ycombinator.com/item?id=50412710 Points: 1 # Comments: 0

Show HN: Nino – Fastest C# serializer, safe on untrusted input, also TS/Go/Rust

Nino is a source-generated binary serializer for C#, and as far as we know the fastest one. In the same BenchmarkDotNet run on GitHub runners against MemoryPack 1.21.4, it serializes classes and polymorphic types 3.5–7.2x faster and deserializes them 1.7–2.1x faster (arrays of unmanaged structs are on par). Deserializing into existing objects allocates nothing. Reproduce: https://nino.xgamedev.net/en/docs/v4/benchmarksIt is built to read bytes you do not trust: lengths are checked before allocating, depth is bounded, hash flooding is limited, and the read paths are fuzzed in CI.The bytes are a spec, not a memory dump, so CoreCLR, Mono, IL2CPP and 32-bit hosts write the same bytes, and runtimes for TypeScript, Go and Rust pass the same conformance corpus.Trade-offs: positional by default (VersionTolerant or Keyed for stored data), a 4-byte type id on polymorphic values, no System.Type, needs C# 9 and Roslyn 4.3+.Docs: https://nino.xgamedev.net Comments URL: https://news.ycombinator.com/item?id=50413601 Points: 1 # Comments: 0

Copilot impact dashboard adds chat and VS Code agent usage

The Agent adoption chart in the Copilot impact dashboard now includes Copilot Chat and the VS Code Agents window, so you can see engagement across nine Copilot experiences. The adoption… The post Copilot impact dashboard adds chat and VS Code agent usage appeared first on The GitHub Blog.