Skip to content
Only First-party#Tutorials / practice
November 13Friday
  1. LiveKit Blog62

    LiveKit tests Gemini 4 Hydrogen vs 3.8 Flash in a voice agent with deliberately broken tools

    LiveKit ran Gemini 4 Hydrogen and Gemini 3.8 Flash through the same Google plugin in a voice travel-concierge agent with deliberately failing tools, and Hydrogen made 0 false booking reports across 54 transcripts versus 2 for 3.8 Flash. With Hydrogen at high and 3.8 Flash at default, Hydrogen's first sentence arrived 1.2 s sooner (4.0 s vs 5.2 s), and at low on both it was 1.7 s sooner (2.8 s vs 4.6 s). The author recommends medium or high thinking for voice agents, noting xhigh's median 7.8 s to first sentence and a 52 s worst case.

    Why it matters: LiveKit's hands-on test shows Gemini 4 Hydrogen reporting every deliberately broken tool call and starting replies sooner than 3.8 Flash, with per-thinking-level latency data for voice agents.

  2. ElevenLabs Blog18

    7 customer service skills every human and AI agent needs

    ElevenLabs outlines seven customer service skills — communication, problem-solving, conflict resolution, empathy, adaptability, personalization and product knowledge — that both human and AI support agents need. It cites a Zendesk study finding over 50% of customers switched to competitors after one bad experience, and a Gartner forecast that at least 70% of customers will start their journey with an AI interface by 2028. The guide stresses evaluating conversational metrics during training and after deployment, plus seamless handoff to humans for de-escalation.

  3. Databricks Blog36

    Detecting credential-driven attacks on Databricks with verbose audit logs and Genie

    Databricks details how credential-driven attacks unfold on its platform and how verbose audit logs plus Genie can detect the behavioral shift after a stolen PAT, session cookie, or service-principal credential is used. The post maps adversary activity into six stages, from initial login through environment reconnaissance, and covers response steps and controls that limit what a stolen credential can reach.

  4. Databricks Blog36

    Bright Machines uses Debezium and Iceberg to give customers live dashboards from air-gapped factories

    Bright Machines now gives customers live, governed dashboards of factory data from air-gapped plants without opening any inbound access. It captures PostgreSQL changes at the edge with Debezium, writes them as Apache Iceberg, pushes them out over one auditable outbound path, and reads them in place in Databricks via Unity Catalog federation. The first customer-visible dashboard went live about two months after kickoff, with committed rows queryable in one to two minutes and dashboards refreshing every ten minutes.

  5. OpenRouter Announcements58

    OpenRouter tests 11 rerankers on a 274-question RAG benchmark

    OpenRouter benchmarked 11 rerankers on a 274-question synthetic RAG dataset and found that reranking the top 30 vector-search candidates with voyageai/rerank-3-lite raised precision@1 from 81.0% to 97.1% at about $0.10 per 1,000 queries. The guide recommends retrieving roughly 30 chunks, reranking them, and sending only the top 3 to the LLM, which in its test lifted answer accuracy to 99.3% while cutting answering cost from $0.22 to $0.16 per 1,000 questions. It also flags failure modes: omitting the input_type parameter cost 7 to 12 points of precision@1, and cohere/rerank-v3.5 silently ignores content beyond its 4,096-token limit.

  6. GitHub Blog · AI & ML58

    GitHub guide explains how to build agent skills that run across Claude Code, Cursor and Copilot

    GitHub published a practical guide to agent skills, versioned directories centered on a SKILL.md file that describe when and how to perform a repeatable task. The guide uses two examples, Proof Agent for adversarial verification of AI-generated code and Data Forge for a multi-skill data pipeline, to show how skills share a project manifest, reuse one execution path, and place human approval at each phase. It also describes a packaging script that generates client-specific files for Claude Code, Cursor and GitHub Copilot from a single skills source.

  7. AWS Machine Learning Blog40

    How Natera built SWARM, an agentic AI system for lab ops on Amazon Bedrock AgentCore

    Natera built SWARM, an agentic AI system for lab operations, on Amazon Bedrock AgentCore, cutting first response time by about 130x and automating 96.2 percent of support tickets. The system pairs a swarm-agent that drafts diagnostic reports before engineers open a ticket with a swarm-hive for real-time engineer interaction, both sharing one skill library. It addresses over 65 daily Jira tickets across three queues that previously averaged 17.4 hours for first response.

  8. Databricks Blog30

    Databricks Debunks Four LTAP Myths About Lakebase Architecture

    Databricks responds to four common misreadings of LTAP, the Lakebase architecture that keeps one governed copy of operational data serving both Postgres and analytics without CDC. The post argues LTAP is not replication: layers in front of the lake are caches, not a second database with its own catalog. It also says heap pages and Parquet are two lossless encodings of the same rows, so point lookups and scans each read the layout fast for them.

  9. AWS Machine Learning Blog38

    Tokenomics at Scale: Tracking and Capping Amazon Bedrock Spend per IAM Principal with CUR 2.0 and AWS Budgets

    AWS shows how to track and cap Amazon Bedrock generative AI spend per IAM principal using only native features: Bedrock automatically records the IAM user or role on every inference request, and those tags become cost allocation tags readable in Cost Explorer or CUR 2.0 exports. An AWS Budget scoped to Bedrock and filtered to one identity or tag value can attach a budget action that applies a Deny IAM policy once a threshold is crossed, with no application code for the common case.

  10. AWS Machine Learning Blog36

    Four Amazon Bedrock inference choices that affect cost

    Amazon Bedrock's cache duration, service tier, reasoning effort, and maxTokens settings can change inference cost without altering the model or prompt. A 5-minute cache write on Claude Sonnet 5 and Claude Opus 5 costs 1.25x the input rate, a 1-hour write costs 2x, and cache reads cost 0.1x; Flex tier requests to unsupported models fail with a ValidationException.

  12. LangChain Blog45

    What Is Eval-Driven Development? How to Improve AI Agents

    LangChain explains eval-driven development (EDD), a three-step process for building AI agents: define what good looks like, write the eval before you build, and compare results after each change. Because agents are non-deterministic, evals score runs across a dataset of examples and can use LLM-as-a-judge, with real agent runs in LangSmith as a source of test inputs.

  13. Databricks Blog22

    How Constellation is building a governed data foundation on Databricks

    Constellation, the largest US nuclear fleet operator, is building a governed Enterprise Data Platform on Databricks to give the business one shared meaning for its data. The platform uses Unity Catalog for lineage, fine-grained access and a single permission model, plus Data Vault modeling for critical reusable entities. Early use cases include a nuclear engineering assistant built with Databricks Genie and outage planning.

  14. Databricks Blog25

    Eclipse Aerospace uses Databricks PySpark custom data sources for flight-data ingestion

    Eclipse Aerospace is using Databricks PySpark custom data sources to ingest nearly 20 years of proprietary flight data, over 3TB spanning more than a million flight hours, without always-on dedicated compute. The Rust-backed Python package delivered twice the benchmarked performance of a similar PyArrow-based pure-Python data source and nearly 20x that of a native Python implementation without Arrow. The API, introduced in Apache Spark 4.0 and available in Databricks Runtime 15.4 LTS, replaces the prior Lambda-to-Avro pipeline.

  15. AWS Machine Learning Blog34

    Building a self-service LLM gateway with Amazon Bedrock and LiteLLM

    A self-service LLM gateway built on Amazon Bedrock Application Inference Profiles and LiteLLM running on AWS Fargate exposes Bedrock foundation models behind an OpenAI-compatible API, giving developers a single base URL and per-user key. The setup adds per-user spend controls, per-model quota isolation, and CloudWatch RPM/TPM observability, with Langfuse for prompt-level telemetry. Self-service key issuance requires LiteLLM Enterprise, since the free tier is limited to five users.

  16. AWS Machine Learning Blog34

    Optimizing cost per task and proving agent ROI on Amazon Bedrock

    This AWS post argues that Amazon Bedrock spend should be judged by cost per task rather than cost per token, since tokenizer efficiency, output verbosity, agentic loop count and reasoning overhead can make a lower-priced model cost more. A worked example shows a model with 2x the list price finishing 65% cheaper per task, and the post adds caching, routing and output constraints plus a five-dimension scorecard for measuring agent ROI against human baselines.

  17. Databricks Blog22

    How H6.ai builds AI-powered financial automation with Lakebase Postgres

    H6.ai automates accounts payable on top of customers' existing ERPs, using a dedicated Lakebase Postgres database per customer as its system of record. Because invoice data keeps changing, the team uses Lakebase copy-on-write branches to freeze snapshots of customer databases and run each regression test on its own short-lived branch, so the live database is never written to. Each run is judged by deterministic assertions plus a panel of AI judges from different model providers.

  18. AWS Machine Learning Blog38

    Amazon Bedrock AgentCore Evaluations: Built-in, DeepEval and AutoEval evaluators

    Amazon Bedrock AgentCore Evaluations now lets teams run AWS built-in evaluators alongside managed DeepEval and AutoEval metrics, plus custom evaluators derived from either. The built-in catalog spans 15 evaluators across response quality, goal completion, tool use, skills and safety, with three trajectory checks for expected tool paths. DeepEval adds multi-turn metrics such as ConversationCompleteness and KnowledgeRetention, while AutoEval contributes specialized signals including security.

  19. AWS Machine Learning Blog36

    Building a Daily Dependency Watcher with LangGraph and Amazon Bedrock AgentCore Web Search

    The Web Search API in Amazon Bedrock AgentCore is now available, giving agents current web results through a single SigV4-signed API call served from a web index Amazon operates. A walkthrough builds a daily dependency watch as a LangGraph graph that researches npm, PyPI, and container base images in parallel, with date windows, blocklists, and search budgets enforced in code. In testing, the three branches finished in 36 seconds versus 99 seconds run sequentially.

  20. AWS Machine Learning Blog36

    AWS Quick AI-PDLC: Six Agents for AI-Driven Product Development

    AWS Quick introduces AI-PDLC, a framework of six specialized agents—led by an Orchestrator covering Discovery, Prioritize, Working Backwards, Spec Generator, and Designer—that turns scattered enterprise signals from Slack, Jira, Salesforce and SharePoint into a traceable prototype_spec.md. Every phase requires human approval, and the spec can be handed to coding agents like Kiro or Claude Code via the open Agent Client Protocol (ACP).

  21. AWS Machine Learning Blog40

    AWS opens catalog of 23 reusable generative AI assets from its Innovation Center

    AWS has published a catalog of 23 production-ready, open source generative AI assets from its Generative AI Innovation Center, now part of AWS Frontier AI Engineering & Services. The building blocks cover RAG pipelines, document processors, agent scaffolding and evaluation frameworks, and AWS says they can cut development from months to weeks. DoorDash reported a 50x increase in testing capacity and Ricoh a 7-fold throughput increase after building on the assets.

  22. AWS Machine Learning Blog38

    How DXC Technology built a multi-model AI substrate on Amazon Bedrock

    DXC Technology built the model substrate for its DXC OASIS IT-operations harness on Amazon Bedrock, reaching Anthropic Claude, Amazon Nova, Meta Llama and open-weight models through one managed interface. Amazon Bedrock Guardrails apply content filtering, PII redaction and denied-topic policies uniformly across every model, while AWS PrivateLink keeps inference traffic inside the customer VPC. DXC OASIS has been generally available since March 2026 and cut resolution time by 95% on average across 56 measured use cases.

  23. AWS Machine Learning Blog40

    Agent DLC: Engineering AI Agents from Prototype to Production

    AWS introduces the Agent Development Lifecycle (Agent DLC), a framework with one lifecycle, two loops, and a single explicit standard for judging every agent change. It addresses three agent properties that break conventional CI/CD: non-determinism, prompts as source code, and independently moving dependencies. A reference HR policy assistant shows chunk-level retrieval precision of 1.00 across all three test questions while fact-level precision fell to 0.09 and retrieval coverage hit 0.00 on one question.

  24. AWS Machine Learning Blog36

    Fine-grained access control for Amazon Bedrock Managed Knowledge Base tools

    AWS shows how to give a shared AI agent per-user document access on Amazon Bedrock Managed Knowledge Base by exposing search as MCP tools through AgentCore Gateway. A request interceptor injects the verified user's email from the Cognito JWT into userContext, and ACL awareness returns only documents that user may view. A Cedar policy in AgentCore and a resource-based policy on the knowledge base add secondary defenses against spoofed or unauthorized searches.

  25. AWS Machine Learning Blog58

    AWS walks through building cross-organization multi-agent systems with A2A

    AWS published a reference architecture in which a LangChain-based enterprise orchestrator on Amazon ECS calls a Strands Agents-based compliance SaaS agent on Amazon Bedrock AgentCore over the A2A protocol, with the two sides in separate AWS accounts and no shared secrets. Each side authenticates with tokens from its own Amazon Cognito user pool, and the SaaS agent calls back to an enterprise context agent for account metadata, so the agents act as peers rather than client and server. The system deploys from three Jupyter notebooks that provision five CloudFormation stacks and run an end-to-end test plus seven trust boundary checks.

  26. AWS Machine Learning Blog34

    Migrating to Amazon Bedrock Managed Knowledge Base with a coding agent

    AWS added a knowledge base migration guide to the amazon-bedrock skill in the Agent Toolkit for AWS, letting a coding agent plan a move from a customer-managed knowledge base to Amazon Bedrock Managed Knowledge Base. The agent starts with read-only discovery and a line-by-line reviewed plan, then creates the new knowledge base and data sources alongside the original or writes a migrated IaC template. Managed Knowledge Base raises default quotas to 200 data sources per knowledge base and 10,000 knowledge bases per account per Region, and adds agentic retrieval, AgentCore Gateway integration, and resource-based policies.

November 12Thursday
  1. LangChain Blog40

    How LangChain's GTM Agent builds consistent, high-quality sales artifacts

    LangChain's internal GTM Agent generated 1,540 sales artifacts over 12 weeks, saving reps 337 hours on documents like account plans and proposal decks. 47% of deals with a sent artifact advanced to a later stage, versus 16% of matched deals without one, and 46% of artifacts were followed by a customer call within 14 days. The agent runs on the Deep Agents harness, whose sandbox, skills, memory, and scheduled runs are available in Managed Deep Agents.

  2. AWS Machine Learning Blog36

    Build autonomous AI agents with Amazon Bedrock and Spring AI

    AWS shows Java teams how to build autonomous AI agents using Spring AI and Amazon Bedrock's AgentCore, with a spring-ai-agentcore integration. Two reference systems are detailed: a single-agent travel assistant with tool calling and memory, and a multi-agent intelligent document processing platform with five specialist agents, a rules engine, and alerting. The stack requires JDK 21, Spring Boot 4.1 with Spring AI 2.0, and deploys via AgentCore runtime on ARM64 containers.

  3. OpenRouter Announcements58

    OpenRouter compares self-hosted LLM and API costs with break-even load calculations

    OpenRouter published a break-even analysis showing when self-hosting an open-weight LLM costs less than calling it through an API, using per-provider prices as of October 8, 2026. At those prices, Qwen3.8 27B on one rented RTX 3090 at $0.50 an hour breaks even at 6 to 12% load, while DeepSeek V4.1 Flash on four H200s never beats the cheapest zero-data-retention endpoint. The post also notes that provider.zdr and the EU and US domains cover most privacy needs without self-hosting, and recommends running a steady base load locally while sending peaks to the API.

  4. OpenRouter Announcements58

    OpenRouter 发布教程：如何阻止 AI Agent 陷入无限循环

    OpenRouter published a guide on stopping AI agents that get stuck retrying a failing tool, using four guards tested on six current models. With doomLoop detection enabled, all six models were blocked on their third identical tool call, and across 18 runs tool calls fell from 314 to 64 while spend dropped from $0.29 to $0.05. The guide adds a loopKey to normalize arguments, stopWhen caps on steps and cost, and a credit limit on the API key that returns a 402 with limit_source openrouter_key_limit.

  5. OpenRouter Announcements28

    How to Benchmark LLMs: A Code-Graded Guide from OpenRouter

    OpenRouter published a guide for benchmarking LLMs on your own application's inputs, grading outputs with code and comparing accuracy, billed cost and request time. On its 60 synthetic tasks, GPT-6.1 Sol passed 180/180 trials across three repeats, while DeepSeek had the lowest response cost at 157/180 passes. Agreement with the public ranking was weak, with a Spearman correlation of 0.109.

  6. vLLM Blog72

    vLLM serves DeepSeek-V4.1-Flash on Vera Rubin NVL72 at 58x GB300 NVL72 throughput

    vLLM reports serving DeepSeek-V4.1-Flash on a single NVIDIA Vera Rubin NVL72 rack at 1.7M tokens/s per GPU with 387 tokens/s per user, 58x the GB300 NVL72, peaking at 2.52M tokens/s and 1,810 tokens/s for a single user. The gains come from kernels rebuilt for Rubin's split memory domains and FP4 tensor cores, a specialized TP8 decode path, and rack-wide KV and Engram pools shared over NVLink. With prefixes pooled across the rack and Dynamo workload-aware routing, the prefix hit rate holds at 96.5-97% even at high concurrency.

    Why it matters: vLLM's third DeepSeek-V4.1-Flash post details how Rubin-specific kernels and rack-wide memory pooling lift throughput 58x over GB300 NVL72, offering a concrete reference for large-scale serving optimization.

  7. Hugging Face Blog36

    Hugging Face Releases Fine-Tuning Guide and Scripts for TRELLIS.2 3D Generation

    Hugging Face published fine-tuning scripts and containers for TRELLIS.2, a 3D generation model, runnable locally or on Hugging Face Jobs. The guide uses LoRA adapters via the PEFT library on only the sparse-structure flow DiT and shape flow DiT, leaving the material stage frozen. On a 188-object footwear subset of the GSO dataset, the pretrained model often rendered incorrect soles, which the LoRA fine-tune targets.

  8. AWS Machine Learning Blog36

    Running OpenAI Codex on Amazon Bedrock: Access Paths and Rollout Guide

    This post shows how to route OpenAI Codex model requests to Amazon Bedrock while reusing existing AWS identity, IAM, Regional, and observability practices. It recommends starting with Native AWS Access for a small least-privilege pilot, with AgentCore Gateway or an LLM Gateway as alternatives, and walks through IAM Identity Center sign-in plus a direct Bedrock Runtime check using GPT-5.6 Sol.

  9. AWS Machine Learning Blog34

    Semantic diffing of formal policies with anti-unification

    An open source engine computes semantic diffs of formal policies using anti-unification over an e-graph, showing shared structure once and keeping both versions of each differing part. It targets autoformalization outputs in SMT-LIB, Cedar, Dogwood, OpenShell policies and CEL, where an LLM writes the artifact but plays no part in computing the diff.

  10. AWS Machine Learning Blog46

    Detecting and recovering from silent data corruption on Amazon SageMaker HyperPod

    A PyTorch DDP training loop on Amazon SageMaker HyperPod gains three checks that catch silent data corruption: a non-finite gradient check, a ring replay audit comparing loss bits and gradient fingerprints across nodes, and a weight fingerprint comparison after the optimizer step. Tested with software-injected faults on 4 ml.p5.48xlarge instances (32 NVIDIA H100 GPUs), the checks name a suspect rank, map it to a node, and let HyperPod replace the node and resume from a checkpoint.

  11. AWS Machine Learning Blog12

    AWS re:Invent 2026 AI/ML Track: Attendee's Guide

    AWS will hold its annual re:Invent conference from November 30 to December 4, with the AI/ML track offering more than 140 unique sessions out of over 2,000 total learning sessions. The guide maps sessions to the AWS AI stack, spanning AI chips (AWS Trainium and NVIDIA GPUs), models and inference on Amazon Bedrock and SageMaker AI, and agent development with Amazon Bedrock AgentCore. Sessions are organized from newcomer content to technical deep dives, and many can be viewed on demand.

  12. AWS Machine Learning Blog28

    Automating AWS Agent Registry updates with a push-based architecture

    AWS outlines an event-driven pipeline that keeps AWS Agent Registry records for MCP servers current without manual updates. AWS CloudTrail captures UpdateAgentRuntime API calls, Amazon EventBridge routes them across accounts, and a Lambda function queries the MCP server's tools via AgentCore Identity OAuth tokens, then diffs and updates the matching registry record. The sample updates existing records only and supports both single- and multi-account setups.

  13. Amazon Science36

    Using Mathematics to Validate Network Configurations: AWS Tiros for Segmentation Checks

    AWS is using its automated-reasoning tool Tiros to statically validate network segmentation across all modeled paths, rather than relying on packet-based sampling. Tiros converts Cloud WAN configurations from route tables, attachments, and policy documents into logical propositions, then checks that no path exists between segments the policy declares off limits, with analyses run as often as every hour.

  14. Meta Engineering Blog40

    Meta Intelligent Delivery: ML System Allocating Compute for Ads Ranking

    Meta detailed Intelligent Delivery, an ML-driven system that allocates compute across its ads serving stack toward the system-wide optimum, contributing roughly 10% incremental ranking performance on top of model and system advancements from 2017 through the first half of 2026. Its Resource Core Model uses 6B sparse and 20M dense parameters to predict each request's marginal utility, and Meta says it improved identification of high-impact ad requests by about 20% in offline benchmarks. The system also relies on multi-layered allocation mechanisms and increasingly agentic AI to adapt as models and hardware change.