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: Recap Studio – A Mac screen recorder for clean, polished demos

Hi HN, I made Recap Studio, a Mac app for recording demos and tutorials that look good without a video editor.You record your screen, camera and mic. Then you can zoom in on parts of the video, smooth the cursor, add a background, show the keys you press, and cut out mistakes. The newest feature keeps your face centered in the camera as you move. Comments URL: https://news.ycombinator.com/item?id=50415185 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Digdeep.fyi – A DNS Debug Tool for DNSSEC, Mail, HTTP

A fully client side, fast DNS debug tool. Queries DNS via DoH resolvers and analyzes DNSSEC configs (inspired by DNSViz), mail records (MX, SRF, DKIM, DMARC, etc), SRC, HTTPS records and runs multiple compliance checks. Comments URL: https://news.ycombinator.com/item?id=50406439 Points: 1 # Comments: 0

Hacker News Show HN

Show HN: Throng, a project first, terminal 2nd IDE for command line people

I've been beavering away at this since July, and its finally getting to a point where its stabilising.It started Windows only, but I recently converted over to Linux, so I've been ironing out the kinks in the last week. You can install it via apt or rpm, or .exe or .msi on Windows.Many more features to come, including native agent support and more preview features (images, PDF, document formats). Claude works pretty well in it, but I've not tried many other agents yet.I rarely leave throng now - 99% of my work happens inside it. I stopped using Visual Studio around 10 months ago (in favour of VSCode), and now I don't even use VSCode. Comments URL: https://news.ycombinator.com/item?id=50412226 Points: 1 # Comments: 0