Google Expands Gemini in Chrome With Cross-Tab Context and Android Auto Browse

·1 views

Google has expanded its Gemini AI assistant within Chrome to offer context-aware help across open browser tabs, integrating with services like Gmail, Google Calendar, Google Maps, and YouTube. The desktop and iOS rollout reached India, New Zealand, and Canada on March 11, 2026, with an Android update following on May 12, 2026. The Android version introduces Auto Browse and agentic capabilities, enabling Gemini to assist with multi-step tasks rather than simply answering questions. Key features include chatting about the current tab, extracting highlights from videos, and comparing information spread across multiple open pages. Google describes the broader goal as turning Chrome into an active working layer between information and action, reducing the need to manually switch between tabs or apps.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

WebForms Core 2.2 Development Begins With Focus on Stateless Server-Orchestrated UI

Development of WebForms Core 2.2 has officially begun, targeting an advanced stateless server-orchestrated UI model that differs from frameworks like Blazor Server by not maintaining persistent component or DOM state per user. The server uses a WebForms class to generate commands executed by WebFormsJS directly against the browser's HTML document, keeping the server stateless and scalable. Version 2.2 aims to elevate this model by introducing higher-level operations for rendering, state management, data formatting, arithmetic, and extensibility without relying on a separate frontend framework. New features include Isole, a high-level abstraction that simplifies working with the Transient DOM by automatically handling initialization and completion of grouped operations. Additionally, snapshot and rollback capabilities are being introduced to allow developers to preserve and restore an element's HTML state during complex multi-step UI transformations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why AI Confidence Scores Need Calibration Testing Before Production Use

A technical deep dive published on DEV Community examines why confidence scores returned by AI decision systems like Jev cannot be trusted at face value without calibration testing. Calibration differs from accuracy: a system can be 95% accurate overall yet still report 90% confidence on decisions it gets right only 60% of the time. This gap is especially dangerous in confidence-gated routing systems, where high-confidence decisions are auto-approved and low-confidence ones are escalated to humans. The article explains two standard diagnostic tools — reliability diagrams and Expected Calibration Error (ECE) — that developers can implement in roughly 40 lines of Python. The core takeaway is that calibration is domain-specific and must be measured by each team on their own data, as no vendor or framework can guarantee it in advance.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds agent that distinguishes pygame from pygame-ce documentation accurately

A developer has built a documentation agent to address a persistent confusion between pygame and pygame-ce, two incompatible Python game library distributions that share the same namespace but have diverging APIs. The agent was submitted to the Sanity Challenge and uses Sanity's MCP endpoint to query the API reference pages of both libraries — 42 pages each — without blending their content. Every response explicitly names which distribution a feature belongs to, the version it appeared in, and its source entry. The agent appends machine-readable verdict lines to each answer, clearly flagging whether a function exists in pygame, pygame-ce, or both. This approach tackles a common pain point where tutorials and AI-generated code snippets rarely specify which distribution they target, leaving developers with cryptic AttributeError messages.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Kubernetes Admission Control Turns Security Policies into Enforceable Gates

Kubernetes admission controllers evaluate workload requests before objects are saved to the cluster, allowing non-compliant pods to be rejected automatically rather than caught through manual review. The built-in Pod Security Admission enforces one of three security levels — privileged, baseline, or restricted — at the namespace level, and can run in audit or warn mode before full enforcement. Policy engines like Open Policy Agent Gatekeeper and Kyverno extend these controls to cover organisation-specific rules such as required image registries, resource limits, or labels. Experts recommend starting in audit mode to collect real violations before enforcing rules, keeping policy sources in version control, and restricting who can modify admission policies since any change affects the entire cluster. Admission control is a preventive gate and does not monitor runtime behaviour or remediate workloads that are already running.

0 comments Read more at DEV Community