Every post, summarised

Aug 26, 2026

• AWS

  Gallup scales real-time coaching for thousands with Amazon Bedrock

  Gallup needed to centralize decades of proprietary workplace performance research to provide proactive, real-time coaching for organizational leaders directly within their daily workflows. To solve this challenge, Gallup developed Gallup AI inside its Gallup Access platform using Amazon Bedrock and Anthropic Claude models. The multi-tenant serverless architecture leverages Amazon Bedrock Knowledge Bases and Amazon Kendra for retrieval-augmented generation, while AWS Lambda with FastAPI powers real-time streaming responses. Amazon ElastiCache Serverless caches recent conversation history for sub-millisecond session retrieval, Amazon RDS for MySQL provides durable transactional storage, and Amazon Bedrock Guardrails enforce content safety. Since its June 2024 launch, the system has achieved sub-second time-to-first-byte streaming latency while prompt volume grew approximately sevenfold across thousands of organizations.

• AWS

  Closing the AI agent trust gap with graduated autonomy

  Operating AI agents under binary full-access or read-only permissions creates an operational trust gap due to unpredictable model behavior across updates. The graduated autonomy architectural pattern closes this gap by dynamically granting or revoking tool permissions through sustained reliability scoring. A scoring engine computes a composite score across five weighted dimensions over a rolling 50-action window, mapping agents across four tiers from probation to full autonomy. In-process pre-execution filters check for prompt injection and sensitive targets, while Amazon Bedrock AgentCore Gateway and Cedar policies strictly enforce deny-by-default access at the infrastructure level. Post-execution state capture in Amazon DynamoDB supports reversibility, and AWS CodePipeline delivery gates block releases failing adversarial evaluation benchmarks.

• Jetbrains

  How Much Code Do Developers Really Let Agents Write?

  JetBrains surveyed over 15,000 professional developers globally in 2026 to measure how much production code is generated by AI agents versus manual authoring. On average, respondents report that agents fully write approximately 47% of their code, while 38% involves AI assistance and 27% is written manually. Adoption varies across ecosystems, with Go, JavaScript, and TypeScript developers reporting the highest agentic code generation at 54% to 55%, while C and C++ developers retain the highest manual share. Senior developers lead adoption over juniors, with about a quarter delegating more than 80% of code generation to agents. Cluster analysis categorizes the developer population into agentic coders (31%), AI-assisted coders (47%), and manual coders (23%).

• amazon.science

  When LLM judges agree, should we believe them?

  Multijudge panels in LLM-as-a-judge evaluations often suffer from correlated errors when models share prompt templates, training lineages, or evaluation rubrics. To account for these interdependencies without human reference labels, a method presented at ICML uses Ising models to simultaneously infer judge reliability and pairwise correlation. The unsupervised algorithm iteratively updates the soft probability of each item's true latent label while estimating both individual judge skill and pairwise dependence structures. Evaluated across retrieval relevance, toxicity classification, and summarization benchmarks with ten zero-temperature judges, the approach achieved test accuracies of 0.912, 0.792, and 0.806. These dependence-aware aggregation scores consistently outperformed weighted majority voting baselines by 9% to 14% on standard metrics across all three tasks.

• NVIDIA

  Experiment with Qwen3.8-Flash-Next on NVIDIA GB300 NVL72 for Agentic Coding

  Alibaba released the model weights for Qwen3.8-Flash-Next as a preview of the upcoming Qwen4 architecture, enabling developers to experiment with a multimodal mixture-of-experts model with a 125B-parameter main model, 51B N-gram embeddings, and 6B parameters activated per token. It supports a native 262,144-token context window, extensible to 1M tokens with YaRN. To reduce long-context attention compute and KV-cache growth, its hybrid design uses Gated DeltaNet in three of every four layers and Qwen Sparse Attention in the remaining layer, where micro-block importance guides retrieval. On NVIDIA GB300 NVL72, it delivers more than 16K tokens per second per GPU and more than 200 tokens per second per user; QSA achieved up to 7.6x prefill and 4.9x decoding speedups versus full attention. Fine-tuning is available through NVIDIA NeMo AutoModel with SFT or LoRA, and reinforcement learning through NVIDIA NeMo RL.

• Pinterest

  Scaling Conditional Learned Retrieval for Pinterest Home Feed

  Pinterest home feed candidate generation relies on large-scale retrieval, but standard two-tower models produce single embeddings that struggle to capture diverse concurrent user intentions. To solve this, Pinterest expanded Conditional Learned Retrieval (CLR) to generate condition-aware embeddings conditioned on explicit interest, Pin, and Board contexts. The team evolved model representations by appending condition tokens to user sequences in transformers, integrating the PinFM foundation model, and introducing hierarchical semantic IDs to improve cold-start coverage. On the serving side, engineers consolidated duplicate feature requests and shifted inference to GPU instances using NVEmbed under a one-query-to-many-documents paradigm. These infrastructure and modeling changes unlocked new condition types, achieved seven-figure cost savings, and reduced p90 model retrieval latency from 80ms down to 12ms.

• Jetbrains

  Compose Multiplatform 1.12.0 Released

  JetBrains has announced the release of Compose Multiplatform 1.12.0 with targeted capabilities for artificial intelligence integrations, web rendering, and desktop application layouts. The update incorporates an experimental Model Context Protocol server inside Compose Hot Reload, allowing AI agents to trigger reloads, capture screenshots, inspect the semantic tree, and simulate user interactions directly. For web deployments, the framework now provides automatic font fallback by downloading necessary Noto font subsets on demand when unresolved characters occur during rendering. Desktop developers receive an experimental v2 window and dialog application programming interface in the androidx.compose.ui.window.v2 package, which distinguishes requested states from actual window states and permits precise control over positioning, sizing constraints, and multi-screen placement. These combined enhancements improve developer workflows and runtime flexibility across multiple target platforms.

• Jetbrains

  How Ubuntu Is Using Rust to Rebuild Core System Tools

  Canonical is selectively adopting Rust to rewrite core system utilities across Ubuntu releases to improve memory safety, security, and long-term resilience. Starting in Ubuntu 26.04 LTS, uutils coreutils shipped as the default implementation targeting complete GNU compatibility, alongside sudo-rs, which introduced intentional behavior changes like asterisk display on password entry. Canonical is also funding ntpd-rs to consolidate NTP, NTS, and PTP into a single utility, while collaborating on UPKI to bring certificate revocation to system utilities. To manage Rust packaging at distribution scale, Canonical vendors dependencies per package rather than creating individual Debian packages for crates and embeds software bills of materials into binaries using cargo auditable. Future plans include exploring Rust implementations of compression libraries like bzip2-rs, zlib-rs, and zstd-rs.

• Red Hat

  How AI observability works with MLflow

  Traditional application monitoring treats AI workflows as black boxes, leaving engineering teams unable to determine whether incorrect responses result from model hallucinations or erroneous upstream tool data. MLflow provides AI observability by capturing distributed traces containing model calls, prompts, retrieved context, execution latencies, and tool interactions. In an example mortgage lending application, trace inspection revealed that an AI assistant accurately summarized raw JSON data returned by an internal pipeline tool rather than hallucinating conflicting metrics. Beyond latency attribution and tool debugging, MLflow is compatible with OpenTelemetry and provides automatic tracing integrations for frameworks such as LangChain and Claude Code. Capturing these traces enables teams to evaluate subsequent application versions, detect model provider shifts, and identify tool regressions before reaching users.

• Sentry

  How to evaluate session replay software: a developer's guide

  Session replay software varies fundamentally based on architecture, distinguishing tools designed for product analytics from those built for developer debugging. Recording approaches split into DOM snapshot and mutation capture, which optimizes for compression and structured debugging, versus pixel capture, which favors visual fidelity for complex animations. Privacy depends heavily on masking location, where client-side masking redacts data before network transmission, whereas server-side scrubbing acts after transmission. For engineering teams, integration depth connects replays natively to traces, console errors, and backend issues rather than requiring timestamp lookups across separate products. Performance costs across CPU, memory, and network require benchmarking on target applications alongside strategies like error-based sampling.

• Jetbrains

  OpenTelemetry Comes to IntelliJ IDEA, GoLand, PyCharm, and WebStorm

  With the 2026.2 release, JetBrains expanded its OpenTelemetry plugin from Rider to IntelliJ IDEA, GoLand, PyCharm, and WebStorm. The tool captures logs, metrics, traces, and service maps locally without requiring an external observability backend. Developers can search structured log records, plot metric values over time, inspect distributed spans, and verify communication paths across databases and message queues during local runs. To ingest telemetry, the plugin automatically configures OpenTelemetry Protocol environment variables for supported run configurations and terminal sessions, or accepts forwarded data from existing collectors. Additionally, experimental Model Context Protocol support allows AI coding agents to query gathered logs, spans, and service topology.

• Red Hat

  Try the Ansible playbook generation lab with Gemini and OpenAI

  The official Visual Studio Code extension for Red Hat Ansible Automation Platform includes an automation coding assistant, formerly called Ansible Lightspeed. Initially integrated with IBM watsonx, the extension now supports Google Gemini and OpenAI-compatible endpoints through Red Hat AI. An updated interactive lab demonstrates these capabilities through an end-to-end scenario involving database installation and HTML landing page deployment across two nodes. Learners write natural language prompts to generate Ansible playbooks and roles, evaluate output, and utilize real-time automated linting and integrated documentation. By serving an open-source model through a preconfigured OpenAI-compatible endpoint, the refreshed environment removes external credential setup steps.

• Red Hat

  Automating Red Hat OpenShift AI installations with Helm and GitOps

  Deploying Red Hat OpenShift AI manually across multiple environments is error-prone due to the numerous required dependencies, including certificate managers, job queuing systems, and GPU operators. To streamline this lifecycle, the odh-gitops repository introduces the rhai-on-openshift-chart Helm chart. The chart automates operator provisioning through Operator Lifecycle Manager and configures custom resources such as DataScienceCluster. Dependency resolution is controlled via a tri-state model that automatically installs prerequisites like cert-manager and Red Hat Connectivity Link when dependent components are enabled. Using this chart, teams can deploy full platform installations or minimal inference stacks through standard Helm CLI commands or Argo CD GitOps pipelines.

• Databricks

  Introducing Governance Hub: Intelligent, account-level governance over your Databricks estate

  Databricks introduces Governance Hub, a beta account-level interface for platform and governance teams overseeing estates spanning hundreds of workspaces and multiple regions. It consolidates data health, access, AI usage, and cost information across AWS, Azure, and GCP, replacing scattered system tables, workspace views, and third-party tools with drill-downs for metadata gaps, principal access, token and model activity, and untagged spend. The hub also integrates with Genie, allowing users to ask governance questions in natural language and receive answers and recommendations grounded in governance data; future actions such as configuring policies and alerts are described as planned. Account admins enable it from the Account Console, with access varying by role and existing permissions respected, while upcoming features include performance and security insights and delegated recommendations.

• Red Hat

  GRPO fine-tuning on Red Hat OpenShift AI: Reinforcement learning from verifiable rewards with Training Hub

  Supervised fine-tuning for structured reasoning tasks like tool calling often demands expensive, labor-intensive dataset curation. Group Relative Policy Optimization (GRPO) resolves this by using programmatic reward functions to score multiple candidate responses without requiring human labels or a dedicated reward model. On Red Hat OpenShift AI, developers can implement GRPO using Training Hub, Kubeflow Trainer, and the Kubeflow SDK to fine-tune models like Qwen3-4B. The setup utilizes vLLM for candidate generation alongside LoRA weight updates, sharing storage via ReadWriteMany persistent volume claims. In a practical tool-calling test, five training iterations raised task accuracy from 33% to 67%, teaching the model to emit parseable function invocations rather than fabricated conversational text.

• MongoDB

  MongoDB Atlas Joins Google Cloud Foundation Fabric (FAST): Secure Private Data Infrastructure in Minutes

  Many organizations lack cloud fundamentals, making foundational setup complex and time-consuming; Google Cloud Foundation Fabric (FAST) is a GitOps-driven landing zone toolkit that accelerates establishing a production-ready Google Cloud organization. A new MongoDB Atlas module within FAST enables provisioning MongoDB Atlas clusters with Private Service Connect (PSC) for secure, private connectivity. PSC avoids VPC peering issues like CIDR conflicts and transitive routing, using a unidirectional consumer-producer model that respects project boundaries and routes traffic over Google’s private fiber network. The module automates cluster creation, PSC endpoint registration with Service Directory, and internal DNS resolution, integrating with Google Cloud KMS for customer-managed encryption keys. This integration reduces foundational setup from weeks to minutes, providing a secure data foundation that connects to BigQuery for real-time analytics and Vertex AI for GenAI workloads.

• Google

  Enterprise-Grade Precision for Long-Context Multimodal Embedding Inference on Cloud TPU

  Embedding models convert text, images, and audio into dense vectors used for semantic search, recommendation, intent classification, content discovery, and clustering. The post describes production support for long-context Qwen3 Embedding models on Cloud TPUs through native vLLM TPU integration and GKE Custom Compute Classes, allowing prioritized autoscaling across TPU and GPU capacity pools. Its implementation pads vocabulary tensors for hardware-safe sharding, hardens lazy loading, pre-warms sharding-aware JAX/XLA compilation caches, and uses a hybrid StepPool with CachedRequestState to preserve pooling state during chunked prefill and preemption. Parity evaluations target cosine similarity of at least 0.999 for text and 0.995 for multimodal inputs; on TPU Ironwood, Qwen3-Embedding-8B reached 83,996 total tokens per second and 5.13 requests per second at 16K+ sequence length with bf16 and TP=4.

• Twilio

  Build a Video Chat Application with Python, JavaScript and Twilio Programmable Video

  This tutorial builds a browser-based video chat application using Python, Flask, vanilla JavaScript, HTML, CSS, and Twilio Programmable Video. It adds text chat through Twilio Conversations and screen sharing, allowing participation on modern desktop and mobile browsers without installed software. The implementation covers Twilio account and API-key setup, environment variables, a Python virtual environment, client-side event handlers, and ngrok, which exposes the local Flask server through an HTTPS public URL for testing on other devices. The refreshed project targets Flask 3.x, twilio-python 9.x, Twilio Video JS 2.35.x, and Twilio Conversations classic JS 2.x, and the completed flow supports live calls, screen sharing, and text chat. Participants must use unique names because Twilio identifies them by token identity.

• Twilio

  8 top conversational AI platforms in 2026

  Published in August 2026, this guide compares eight conversational AI platforms amid rapid market consolidation and acquisitions including NiCE’s roughly $955 million purchase of Cognigy. It defines the category as software for building, deploying, and operating agents across voice and messaging, then distinguishes vendor-managed services that own reasoning from infrastructure providers that carry conversations while teams own the reasoning. The evaluation criteria include model flexibility, voice and messaging parity, deployment control, cross-channel context, human handoff, pricing, and integration depth. Twilio is presented as an infrastructure layer for teams choosing their own models, with ConversationRelay, Agent Connect, Conversation Orchestrator, Conversation Memory, and Flex supporting channels, continuity, and escalation; other entries include Google Conversational Agents, Kore.ai, and NiCE Cognigy. The guide argues that portable models and conversation data will matter as the conversation layer separates from agent reasoning.

• Databricks

  Leveraging Databricks to Support FISC Security Guidelines

  The FISC Security Guidelines define control objectives for Japanese financial institutions, while the post addresses the challenge of translating them into auditable controls on Databricks data and AI workloads. The Databricks Data + AI Platform, Unity Catalog, and optional Enhanced Security Monitoring and Compliance Security Profile features are presented for identity and network controls, encryption, fine-grained access, audit logs, lineage, and hardened runtimes. For AI workloads, Unity Catalog’s Model Registry links training data, code versions, and evaluation metrics to model versions, while a separate framework maps 97 AI-specific risks to 73 controls. The FISC Customer Capabilities Mapping Matrix connects guideline units to platform capabilities and customer responsibilities, including configuration, SIEM integration, backup, recovery, and evidence; the Security Analysis Tool is suggested for finding workspace gaps, and the material is identified as educational guidance requiring expert review.