Skip to content
AI NEWS.ccAI正在发生 未来正在更新
Bookmarks
THE JOURNAL
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

Hacker News Show HN

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

Hacker News Show HN

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

Hacker News Show HN

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

Hacker News Show HN

Show HN: An open-source IDE for software architecture

Now, with this open-source tool everyone can learn,build,share,and validate the system design.This is next step, drawing design on blank page to making it a workflow .Do explore and let me know how it is... Comments URL: https://news.ycombinator.com/item?id=50412135 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Shutdown Watch – App shutdowns, export deadlines, and alternatives

My recipe app picked up users when a similar app shut down, and I kept noticing people scrambling to export their data, so I created this project to scratch my own itch.The 3 main purposes this serves are:1. Give the public a way to find how to export their data or find a replacement if one of the apps they use shuts down.2. Give app creators a way to get their apps in front of people who are actively looking for a replacement for a similar app. Sponsored spots are labeled and never change the dates or export steps.3. Provide inspiration for app creators looking for ideas for what to build next. Just because apps shut down doesn't mean they were not good ideas; many times they shut down for other reasons, like poor execution, no marketing, over-spending, etc.Every date and export step links to the company's own notice.I'm always open to ideas to make it more useful. I read all the comments and constructive criticism and input are always welcomed. Comments URL: https://news.ycombinator.com/item?id=50412639 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Realtime sync engine without any new infra

Tandem is an open-source sync engine and client-side database that plugs into your existing infrastructure. Add the Tandem library to sync data in real time across your clients and server, without deploying any new services.I started work on Tandem 6 years ago as a side project. I was frustrated by the sync engine landscape at the time, thinking I could build a better DX and require less lock-in. Even now, sync engine companies and “full-stack databases” need you to migrate to their database or provision a separate service with auth, networking, etc. This makes them annoying to maintain and also harder to adopt incrementally.Tandem is designed to just be embedded into your existing frontend and backend code. You define a schema, set up a database adapter (any SQL-like database is supported), add the new sync endpoint to your existing API, and then you're good to go.Tandem uses DST (Deterministic Simulation Testing) on every PR and nightly to ensure correctness. Our DST system Gatekeeper lets us model not only storage and network failures, but also race conditions, by gating each call between client/server/other services independently.Tandem currently supports any React-based frontend, any serverful backend (like Cloudflare Durable Objects), and any SQL-like database. New adapters are easy to build, and PRs and issues are appreciated!Open-source and MIT licensed: https://github.com/tanishqkancharla/tandem Comments URL: https://news.ycombinator.com/item?id=50398763 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Cerea – yet another self-hosted LLM chat front end

Here is Cerea, a self-hostable, open-source (Apache 2.0) chat+agent frontend for LLMs. It works alone with any OpenAI-compatible inference provider, but it's way better when coupled with the model gateway I'm also developing, Pystino (https://github.com/paoloviviani/Pystino).I came to this after struggling to find a hosted chat interface that was truly open source, that I really enjoyed to use, and that was simple enough to be shared and used by family. In particular, I was looking for something that could provide the smooth and integrated user experience of commercial products for the tasks needed by family (e.g., document editing, form filling, notes and knowledge management), but backed by open models hosted wherever I decide.Then it became richer, now supporting: remote coding agents (wrapping Opencode), delegation and coordination between agents, integration between chat/projects and code agents (this one to me is a pain point for Claude, which I use at work), projects, RAG, rich artifacts support, schedules, and more.You can try it yourself, either cloning the full repo and head to Cerea/kit, or just the deploy kit with a script (https://github.com/paoloviviani/Cerea#quick-start).It's just a docker compose with a ./configure script that helps to generate a sensible .env for the specific scenario. It works in the browser and as a PWA on mobile.I hope you'll enjoy, feel free to reach out for questions. Comments URL: https://news.ycombinator.com/item?id=50384502 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Repairer – close the breach when a Linux flaw goes public

As we've seen with the Ubuntu critical CVE-2026-98432 (CVSS 9.8), AI-dicovered zero day exploit are being reported at an exponential rate and we don't have the process for dealing with the flood of exploits in real time.What we need is an AI-based system for autopatching systems based on real time information. The vendor's fix can take days or weeks to be out (is the Ubuntu thing patched yet?) and meanwhile the grid is vulnerable to exploitation, especially AI worms.Repairer is a small program that runs on each of your servers. The day an exploit goes public it puts up a stopgap that blocks it, and once the real fix is up it takes the stopgap back off by itself.A stopgap only takes something away — drop certain packets, turn off a kernel module or service, remove a setuid bit. It never opens a port, installs or downloads anything, nor runs code. It arms an undo playbook before applying the stopgap, so the change reverts if affects any services.It only ever acts on rules you sign with a (hardware) crypto wallet.Let's go further: stopgaps are written and checked by a swarm of AI agents (gnosh.ai sessions) running on gno.land, each with bonded stake. Each stopgap is run on fresh machines, and whoever is caught lying loses their stake to whoever caught them.The agent is built and tested on Ubuntu and Debian, all open source, standard-library Go. More distros coming. Let's build repairer together.https://gno.security/repairer/ https://github.com/gnosecurity/repairer Comments URL: https://news.ycombinator.com/item?id=50388417 Points: 1 # Comments: 1