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

arXiv cs.CL

FinEvolveKG: Controlled and Attributable Prompt Evolution for Financial Knowledge Graph Construction

arXiv:2611.08643v1 Announce Type: new Abstract: Financial institutions construct knowledge graphs (KGs) from shared SEC 10-Ks to serve risk analysis, portfolio management, and investment research, whose analytical needs differ. Extraction must adapt without fragmenting shared grounding, typing, and temporal rules. Hand-authored persona prompts and fine-tuning add cost. Weight-free prompt optimization offers an alternative, but unconstrained evolution of a monolithic prompt can rewrite shared rules alongside persona guidance, obscuring changes and complicating review. We introduce FinEvolveKG, a KG-construction harness separating reusable general and persona-policy blocks and mechanically confining GEPA, a reflective prompt optimizer, to the designated block. During persona adaptation, the approved general block remains byte-stable and every optimizer edit is localized to a separately versioned persona policy. A dual objective balances generic temporal-KG quality with persona-relevant facts, motifs, and multi-hop connectivity. We evaluate five mutation scopes on ticker-disjoint 10-K splits, with three seeds for the persona-conditioned arms (v3-v5) across three personas. On the three-seed mean, the complete two-stage block-constrained workflow (v4) improves over the frozen prompt baseline (v1) by 19.4-30.9% and over the tested unconstrained full-prompt workflow (v5) by 2.2-6.4%, leading v5 on both objective components and winning all nine paired-seed comparisons with the lowest seed variance in every persona. Without further optimization, v4 also exceeds v5 across all evaluated out-of-distribution (OOD) shifts. An SME audit supports using the generated triplets as ground truth; a blinded two-SME audit favors v4 over v5 in 70.1% of contrast-enriched judgments. These results show that mechanically attributable evolution can coexist with strong empirical performance, without attributing the gains causally to the boundary.

Hacker News · AI热门原文

How I Fight AI Brain Fry

Article URL: https://sergeykuhne.com/blog/fighting-ai-brain-fry Comments URL: https://news.ycombinator.com/item?id=50416363 Points: 83 # Comments: 56

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

llama.cpp releases

b12208

The ggml library has been updated to make tied selections in the radix Top-K algorithm deterministic on CUDA and Metal backends by replacing atomic compaction loops with a deterministic scheme using simdgroup scans and coalesced memory accesses. This change ensures byte-identical outputs across runs, improves performance by 20-45% on M5 Ultra hardware, and enables deterministic testing for Metal and ROCm. Redundant CUDA kernel resets were removed, and Vulkan/Metal changes were reduced or skipped.

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

GitHub Copilot changelog

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.

AI Weirdness

Laser Light Cannon - a review

A laser scientist reviews the laser light cannon from the Steven Universe cartoon, including its highly unusual beam shape.

AWS Machine Learning Blog

SageMaker Inference now supports Multi-Instance GPU to maximize GPU utilization for model endpoints

Amazon SageMaker Inference now supports GPU partitioning with NVIDIA Multi-Instance GPU (MIG), which divides one GPU into hardware-isolated partitions so you can run a different model in each or take a right-sized fraction of a newer accelerator. This post shows how two optional API fields place one model per partition, and what we measured against a whole older GPU.

AWS Machine Learning Blog

Serverless MCP server for AI agent data lake access on Amazon ECS Fargate

Learn how to build a serverless Model Context Protocol (MCP) server on Amazon ECS with AWS Fargate that gives AI agents secure, metadata-driven access to an enterprise data lake. Exposing a new dataset requires only a JSON file, with no per-dataset integration code.

The Verge · AI

Why a new report on Anthropic automating AI development is alarming researchers

Anthropic is using AI to build more powerful AI. And it appears to be working remarkably well, with the company's models improving roughly twice as quickly as a year ago, with little indication of slowing down. That's according to a new report published Thursday by the AI safety research organization METR, following an 11-week investigation […]