This Medium article presents a 2026 guide on connecting an AI agent to a database safely, framed as a security layer between the database and AI agents. The submission links to the article and its Hacker News discussion thread, which had 2 points and no comments.
In June 2026 Databricks and the Linux Foundation announced that Delta Sharing has evolved into OpenSharing, an open, vendor-neutral protocol under the Linux Foundation AI & Data Foundation that extends sharing beyond tables to volumes, agent skills, and AI models, and adds Apache Iceberg REST Catalog support and on-premises or private cloud reach. Existing Delta Sharing clients and integrations remain compatible, and enabling OpenSharing on a Unity Catalog metastore is a configuration step rather than a migration. Databricks also introduced capabilities on top of the protocol, including SecureConnect (generally available), Global Distribution (private preview), Genie Agent Sharing (beta), and Lakebase table and change data feed sharing (public preview).
This Databricks blog compares three data-sharing methods: OpenSharing, which gives recipients direct read-only access to live assets such as tables, views, notebooks and AI models; Clean Rooms, where up to ten parties combine data and run only mutually approved code without exposing full underlying datasets; and Marketplace, a public storefront for discovering and publishing data and AI products. It advises choosing based on the relationship with the recipient and notes the tools are not mutually exclusive.
GoDaddy's domain data platform team built Pipeline Build Agent, a conversational AI agent on their go-agent-python SDK deployed via Katana that turns a single Slack message into a complete data pipeline, reducing a task that took 2–4 hours to minutes. A manager agent routes intent to a Pipeline Creation Agent (checks S3 schemas, generates PySpark jobs, DAGs, and policy files, opens a PR) or a Column Addition Agent (finds the pipeline, propagates changes downstream, opens a PR), with both querying the Lake Naming Standards knowledge base before generating code. The team enforces one PR per run with update_pr_files as the only correction path, and plans to add Redshift and S3 CSV export destinations plus pre-PR syntax validation.
In this episode of The Pragmatic Engineer, Maude Lemaire discusses scaling large products at Slack, GitHub and Cursor, including Slack's load testing with the Go-based Koi Pond tool, thundering herds and event floods, and GitHub's Rails monolith and database sharding limits. She also covers how she uses AI in her work while keeping judgment calls in her own hands, and suggests rotation between platform and product engineering roles.
NVIDIA outlines five co-design approaches for maximizing the value of every byte in an AI factory, where high bandwidth memory (HBM) is described as the fastest, most expensive and most contested memory tier. The piece argues that bytes spent on redundant weight copies, idle sessions' KV cache or recomputed prefixes are bytes not producing tokens, shifting the question from how much memory a GPU has to how much useful work each byte delivers.
Manus's four-person data team built a data agent on Manus that more than 40 people now use weekly, with roughly 2–3 questions per person on average and heavy users asking a dozen or more a day. The agent connects directly to detailed data and relies on a knowledge base of metric definitions and table relationships, with access split by topic and approval requests automated when users need data they can't see. The team says it took about a week to reach a first working version and that Manus handles the agent infrastructure, letting them focus on data and business context.
This is the introduction to a seven-lesson series drawn from the author's notes on the London School of Economics' programme on AI Law, Policy, and Governance, written for readers who want to understand how AI is being regulated without reading the regulations themselves. The lessons cover why AI is a policy problem, how AI rules get made, six ways to govern AI, the EU AI Act, China, the UK and the US, and the international arena. The author notes the material reflects their own reading, is not endorsed by LSE, and will date quickly as AI governance moves fast.
Billino describes a self-updating expense-extraction pipeline in which user corrections are captured as labeled cases, distilled by an LLM into candidate one-line rules, validated through shadow runs and replay against existing tests, then activated per tenant and vendor so later extractions re-run with the new rules. The post walks through the full loop from upload to promotion and discusses pitfalls including personal data in invoices, narrow rules, limited bug coverage, scope, and setup, API, and stability costs.
The post argues that Vaadin Browserless Testing runs full integration tests, including UI code, in milliseconds without a browser or web server, since Vaadin Flow views are server-side Java calling services in the same JVM. It contrasts this with SPA architectures, where frontend, backend and end-to-end tests form three toolchains and the frontend-backend contract is only covered by slow, fragile e2e tests. The author says this speed and determinism suit AI coding agents and yield a single JaCoCo coverage number for UI, services and jOOQ repositories.
Debezium Server 3.7 ships an open-source Zerobus Ingest sink, built by Databricks with NVIDIA's contribution of envelope mode, that pushes change events directly into Unity Catalog Delta tables without a Kafka cluster between capture and the lakehouse. Envelope mode lands each full Debezium change event in a fixed nine-column table with source position and an idempotency key, and the sink waits for Zerobus to confirm durability before Debezium advances its offset, giving at-least-once delivery. Landed events can then be shaped into Type-1 current-state tables via AUTO CDC sequenced by source LSN, or Type-2 history tables.
This article compares computer-use agents, which operate a whole desktop from screenshots by moving the mouse and keyboard, with browser-use agents, which drive a real browser over the Chrome DevTools Protocol by reading page structure and acting on elements. It recommends browser use for web tasks because it is more precise, scriptable and parallelizable, and computer use for steps that leave the browser, such as desktop apps or OS dialogs. It also notes that many workflows need both approaches combined.
A blog post titled "Generating 2k Consistent AI Images: The House Method" presents a method for producing 2,000 consistent AI-generated images. The post is linked from Hacker News, where it has 1 point and no comments.
This guide explains that speech to text accuracy depends on audio input quality, speaker dynamics, and lexical and contextual issues, and that fixes should target the input, processing, or output stage of the pipeline. It recommends recording at 16 kHz or higher in lossless formats with microphones four to six inches from the speaker, using voice isolation, diarization or multichannel recording, and keyterm prompting, and measuring accuracy with word error rate. It also notes that ElevenAPI offers Scribe v2 with keyterm prompting, multichannel transcription, and speaker diarization.
Bansat is a blueprint-first framework and Agent Skill for Claude that has an AI agent write a full plan covering product, architecture, security, privacy law, accessibility and UI states before any production code, then wait for approval. It defines four gates (G1–G4) blocking code, real personal data and launch, plus 17 blocking launch traps and a retrofit track for apps already live. The framework is a single Markdown file (15 parts, 4 appendices, about 2,800 lines) installable via git clone into ~/.claude/skills/bansat, with text and templates under CC BY 4.0 and code samples under MIT.
NVIDIA describes how, as GPU clusters scale, site reliability engineers must examine multiple dashboards to diagnose training performance drops. NVIDIA developed the AI Factory Operations Agent to streamline operations of its own internal NVIDIA DGX SuperPOD.
The post notes that typing "hi" into an AI assistant can show 18,000 tokens of usage, with only one of them being the user's own input, and sets out to explain where the rest went. It closes by saying it hopes the explanation demystified how agents work and why tokens are used so fast, and invites questions in the comments.
This roundup lists ten platforms for taking AI-generated or AI-focused courses that end in a verifiable certificate, including Coursera, DeepLearning.AI, edX, Udacity, Google Cloud Skill Boost, Microsoft Learn, LinkedIn Learning, Pluralsight Skills, Teachable and Nokku.ai. The author's criteria are employer-verifiable certificates, current content, and real assessments such as quizzes or projects rather than a progress bar. It closes with guidance on choosing by goal, noting that none of these certificates gets you hired on its own.
This post explains how to connect decision models—Jev from TypeSafe and the open-source Strands Decider 2B—to Amazon Bedrock AgentCore Evaluations through code-based evaluators running in AWS Lambda, converting evaluator input into decision model requests and probabilities back into evaluation results. It describes noul, choice, and score question types, positions decision models as a calibrated screening layer alongside rather than a replacement for built-in LLM-as-a-judge evaluators, and outlines a five-step process for validating a decision-model evaluator against labeled traffic. A full code sample in the AgentCore samples GitHub repository deploys an HR Assistant agent evaluated by deterministic checks, built-in evaluators, and decision-model evaluators.
A blogger with right foot pain pointed Claude Code (Opus 4.8, high reasoning) at a folder of 164 DICOM MRI images and a prompt asking for an independent, gold-standard PDF analysis with annotated images for both experts and laypeople. Over about 45 minutes Claude installed Python imaging and PDF packages, read DICOM metadata, rendered and annotated key slices, corrected misplaced arrows using coordinate grids, and generated a 272-line reportlab script for a ten-page report, which it then checked by converting the PDF pages to images. The resulting report largely concurred with the medical provider's findings but was more thorough and included annotated images the provider's report lacked.
AI voice agent pricing combines three line items: the platform that runs the agent, the LLM that powers each conversation, and the telephony provider that connects calls. Using ElevenAgents pricing as an example, every paid tier works out to $0.08 per platform minute, with LLM and telephony billed separately at cost, and plans ranging from a free tier with 15 minutes per month to custom Enterprise pricing. The guide also covers concurrency limits, ROI calculation against staffing costs, hidden costs, and ways to reduce spend.
Indegene built an LLM-powered Data Quality Agent within its NEXT Unified Data Platform on AWS, using Amazon Bedrock, Strands Agents, and Amazon Bedrock AgentCore to generate context-aware data quality rules, validate them, and produce SQL and Python code under human-in-the-loop governance. The agent draws on internal enterprise and external reference knowledge bases via RAG to recommend technical and life sciences-specific business rules. Indegene reports the agent reduced rule definition and implementation effort from about 30 hours to about 4 hours per dataset and cut new table onboarding from 2–5 working days to 2–4 hours.
This post presents a four-layer context engineering approach for production AI agents—architectural isolation via multi-agent design, prompt-based output control, filesystem-based context externalization, and independent verification with safeguards—illustrated through Deep Insight, an open source multi-agent data analysis solution built on the Strands Agents SDK and Amazon Bedrock AgentCore. Reported results include roughly 95 percent fewer tokens added to context per script from a combined write-and-execute tool and roughly 97 percent smaller system prompts from on-demand skill loading. It is Part 2 of a three-part series.
The author describes three small changes to an open-source eBPF agent (between commits 9c521bd and cfc7538): skipping the LPM cache lookup when a path tail is shorter than 128 bytes, checking the inode cache before building the file path in lsm_file_open, and loading only lsm_inode_permission, tp_exit_openat and tp_exit_openat2 when ptrace blocking is enabled. In a benchmark opening one file 200,000 times and 20,000 new files, repeated opens dropped from 4.68 µs to 2.15 µs (about 54%) and cold opens from 6.33 µs to 5.36 µs (about 15%), with repeated-open p99 falling from 8.3 µs to 3.46 µs. The author notes he runs the perf test after each commit and gives the results to an LLM to find inefficiencies to fix.
A Hacker News submission links to a codingplans.dev article titled "What AI Model Effort to Use for Coding," with a discussion thread on Hacker News. The supplied material contains only the article and comments URLs, the point count (1), and the comment count (1), with no article text.
U Mobile's Information Systems Division, working with AWS and AWS Partner Axrail, built AiDaH, an AI-Driven Agentic Helpdesk on Amazon Bedrock AgentCore, which now handles over 150 documented operational scenarios across six business divisions. According to U Mobile's internal measurements, monthly trouble ticket volumes fell by up to 84.5 percent in provisioning and network tickets, 81.6 percent in general inquiries, and 48.7 percent in billing and charging between January and September 2026. The post details AiDaH's six-layer architecture, its security foundation including a Well-Architected Security Review of the Landing Zone, and the spec-driven development approach using Kiro.
NVIDIA describes using NeMo to convert production evidence into prioritized issues and custom evaluations for improving agent prompts, tools, models, memory, skills, and harness code. The post notes that generic benchmark scores may not explain domain agent failures, such as choosing the wrong tool, following the wrong workflow branch, missing relevant context, or using an unnecessarily expensive model.
Aman Sardana argues that AI components should be treated as dependencies that can fail, and that classic reliability patterns—timeouts, circuit breakers, bulkheads, retries, fallbacks, and graceful degradation—must be extended to cover AI's quiet failures, where a model returns a fast, well-formed, confident but wrong answer. He proposes a semantic circuit breaker that trips on validation failures and low confidence, layered response validation, a deliberately designed fallback chain, and a pre-agreed degradation table specifying fail-open or fail-closed behavior for each use case.
The article argues that scientific data archives are poorly suited to AI use because data is locked in opaque files, and proposes a four-step architecture: place data in scalable object storage, index chunks rather than filenames, co-locate dataset-level metadata with the data in object storage, and catalog repositories rather than individual files. It says this approach lets agents and humans quickly find and fetch only the chunks a query needs, citing a 576x reduction in data fetched for a GOES-16 timeseries and a 100x speedup in common NASA queries. The piece describes this as how Earthmover's Arraylake works, built on Icechunk and Zarr, and notes the same recommendations apply to humans and AI alike.
This post argues that an MCP server should be the first choice for making a web app agent-friendly, because MCP standardizes both server and client behavior, lets the client handle OAuth so the model never sees the token, and can route destructive-action confirmations directly to the human via elicitation. REST APIs remain better for scripts, bulk jobs, data exports and integrations that run without an agent, while CLIs suit agents with a shell working with local files. The author recommends putting business logic in operations and exposing them as thin adapters over MCP, REST and optionally a CLI, using the open-source Linkly link shortener as the example.
A practitioner tested Snowflake's new AGENTIC mode for AI_PARSE_DOCUMENT on a SharePoint-fed Cortex Search pipeline, finding it costs a flat 8.18 credits per 1,000 pages versus 0.68 for OCR (about 12x) and only paid off on slide decks, where it returned chart, diagram, table and infographic summaries absent from OCR text. Two undocumented behaviors surfaced: image summaries live in each page's images array rather than the page content, and the mode parameter must be a literal, since a CASE expression silently returns NULL. The author settled on AGENTIC for PPTX and OCR for everything else, appending only the four useful image types to page text.
Lovable's founder recounts how the platform evolved from the 2023 GPT Engineer project into a product where users have created more than 70 million projects, repeatedly reinventing its agent design—from complex async subagents back to a predictable tool chain, then to "knowledge files" with retrieval instead of fine-tuning. He describes stateful sandboxes that keep development servers running for faster edit-check cycles and a framework called Camille for forking and merging entire running computers. He closes with three open problems: automating the full software lifecycle, making all types of software seamless to build, and building a better software stack.
Rezi.ai describes moving its ~515-page site off Webflow to an Astro 7, React 19 and Tailwind CSS 4 stack hosted on Netlify, with Claude Opus 5.5 doing the heavy lifting, after Webflow quoted $2,500 a year to add a single language on top of a roughly $30,000-per-year enterprise contract. The team first tested the approach on two smaller brands, then kept the Rezi.ai rebuild visually identical using a script that compares every page to the Webflow original, and reports desktop PageSpeed rising from 38 to 99 and mobile from 57 to 95.
The author describes using AI extensively for systems programming and explains how they approach long-horizon work. The post also links to a 35-minute keynote from IDA Driving IT 2026 (30 October 2026) and to the original two-hour talk, with slides available to browse or open in a popup.
Conn3x now has circuits for Ollama and Qdrant, and its Ollama repo includes an example that builds a private retrieval-augmented generation box on a DigitalOcean droplet with a single conn3x apply. The setup runs Ollama and Qdrant on loopback only, with SSH as the sole open port, and the post walks through storing a note, querying it by meaning, and having qwen2.5:0.5b answer. The author reports 101 resources applied in 2 minutes 36 seconds, a clean second plan, and a 41-second destroy.
NVIDIA's technical blog describes three stacked optimizations for running Ant Group inclusionAI's 124B-parameter Ling-3.0-flash (5.1B active) on a single DGX Spark at batch size one: Humming MXFP4 MoE kernels, an FP8 LM head, and built-in NEXTN speculative decoding. Across all 1,319 GSM8K questions, decode throughput rose 42.5% (37.81 to 53.89 tokens/s) and mean latency fell 24.5%, with accuracy essentially flat (96.89% to 96.82%). NVIDIA notes that combining the FP8 LM head with MTP requires a shared LM-head module, otherwise the framework silently falls back and throughput drops below the unoptimized baseline.
An Affirm tech blog post, shared on Hacker News, describes composing fraud rules at the speed of the attack using classical machine learning and AI-assisted review. The post is linked from tech.affirm.com and has drawn 1 point and no comments on Hacker News.
Solène introduces braindead-local-intelligence, a project that runs podman containers for an OpenAI-compatible LLM server, an image generation server, SearXNG web search and Open WebUI behind a single token-protected address, loading only one model at a time and unloading it after a few minutes idle. It requires a Linux system with rootless podman 5.0 or newer, targets AMD GPUs (tested up to 12 GB VRAM), and offers a documented list of ready-to-use text, vision and image models. Setup involves adding the user to the render and video groups, running bin/ia install and ia doctor, then ia start, with the web interface at http://127.0.0.1:3000.
Call transcription converts phone or video calls into written text, typically via AI speech-to-text models, either after recording or in real time. Businesses use transcripts for searchable records, quality assurance and coaching, compliance documentation, and CRM logging. Legality depends on jurisdiction, with some regions requiring one-party consent and others all-party consent.
Velu describes building a help center generator that needs only a web address and a login, not source code access, by having agents use the product the way a new employee would. The system evolved from a single agent into a seven-phase pipeline—research, planning, writing, editing, mock data, screenshots and videos, and publishing—splitting work whenever an agent grew too large. Haiku handles high-volume simple browser work while Sonnet handles planning, writing and editing, with an editor's rules stored in a customizable SKILL.md.