iCreatAI News
Skip to content
  1. Cloudflare Blog71

    Kitesurf is now open source

    Cloudflare has open-sourced Kitesurf, its stateless browser for AI agents that runs entirely on Workers, under the Apache 2.0 license on GitHub. The repository includes the engine, PageScript, PageRenderer, and CLI, built on Rust-to-WebAssembly projects like Blitz, Stylo, Boa, and Linebender libraries, and supports the Chrome DevTools Protocol for clients such as Puppeteer. Developers can run it locally or deploy their own instance to Cloudflare Workers, which requires a Workers Paid plan because it uses Dynamic Workers.

    Why it matters: Useful for developers who want to self-host a lightweight agent-oriented browser engine and inspect or contribute to its open-source components.

  2. Claude Blog62

    Building always-on agents

    This post explains that always-on agents are stateful and proactive, running on the same core loop as other agents but surrounded by architecture built from five primitives: an event inbox, timers, memory, permissions, and an outbox. It describes how each primitive works, including inbox best practices, follow-up versus scheduled timers, memory types such as user instructions and task progress, credential proxying and deferred tool calls, and outbox delivery pacing. It concludes with how the primitives form a repeating cycle in which each brief run is triggered by an event and can set timers that wake the agent again later.

    Why it matters: Offers a concrete architectural blueprint for teams building proactive, stateful agents, with practical guidance on event handling, memory, permissions, and message pacing.

  1. Hugging Face Blog60

    llama.cpp v1.0.0 : A stronger foundation for the local AI ecosystem

    llama.cpp released libraries v1.0.0, marking a commitment to stable public APIs for downstream developers, with both llama.cpp and ggml now reflecting API and ABI incompatibilities through major-version bumps. The project states it supports more than 150 architecture variants and all mainstream speculative decoding methods, and distributes pre-release artifacts across Linux, macOS, Windows, Android and iOS plus channels including Docker, Homebrew, conda-forge, MacPorts, Winget and XCFramework. It also describes continued investment in CI infrastructure and self-hosted runners with hardware support from NVIDIA, AMD, Qualcomm, Arm, IBM and Intel.

    Why it matters: Signals a versioning milestone for a widely depended-on local inference library, useful for developers tracking API stability and platform support.

  2. vLLM Blog72

    DeepSeek-V4.1-Flash on Vera Rubin NVL72: 58x Throughput vs. GB300 NVL72 at 387 tokens/s

    On a single NVIDIA Vera Rubin NVL72 rack, vLLM serves DeepSeek-V4.1-Flash at 1.7M tokens/s per GPU with 387 tokens/s per user, 58x GB300 NVL72, reaching 2.52M at peak throughput and 1,810 tokens/s for a single user. The gains come from kernels tuned for Rubin's split memory domains and FP4 tensor cores, specialized low-latency decode kernels, and a rack-wide KV cache and Engram tables shared over NVLink. The post details four optimization groups and reports a 96.5–97% prefix hit rate at high concurrency with workload-aware routing.

    Why it matters: It offers a detailed, measurement-backed look at how Rubin-specific memory and MMA features translate into serving throughput and latency for a frontier open model.

  3. vLLM Blog60

    Inkling 2 Small on vLLM: Day-0 Support

    vLLM announces day-0 support for Thinking Machines' Inkling 2 Small, a multimodal text-and-vision MoE model with 594B total and 17B active parameters, up to 1M tokens of context, and a native DSpark speculator. The post details the architecture (48 layers, 384 experts with top-8 routing, block attention residuals, gated attention, a 23-layer ViT image encoder, and mixed NVFP4/MXFP8 expert precision) and vLLM's optimizations, including kernel fusion with PDL, fused MoE activation quantization, sequence parallelism for prefill, and a Gluon relative attention kernel, reaching up to 630 TPS/user at TP4 on GB200. It also covers LoRA and RL (via SkyRL) support, a serve command, agentic-workload benchmarks, and accuracy checks on NIAH up to 1M tokens, MMMU-Pro and HLE.

    Why it matters: Useful for engineers evaluating or deploying a large multimodal MoE model, as it pairs concrete architecture and quantization details with vLLM-specific kernels, benchmark numbers and a ready serve command.

  4. AWS Machine Learning Blog71

    Run agents securely and efficiently with the next generation AgentCore runtime

    AWS announced updates to the Amazon Bedrock AgentCore runtime that keep each session in its own hardware-isolated Firecracker MicroVM while starting sessions up to 15x faster, scaling to 4x more compute (up to 8 vCPUs and 32 GB, with container images up to 10 GB), and running up to 68% more efficiently. The runtime now reclaims memory within minutes of release and scales idle agents to zero, and agents can dynamically mount and save work to a filesystem such as an Amazon S3 bucket with FUSE support so data stays inside the trust boundary. The next generation runtime is available today in AWS Regions across North America, South America, Europe, and Asia Pacific.

    Why it matters: Announces concrete performance, scaling, billing, and data-isolation changes to a managed agent runtime, with customer metrics and availability details useful to teams planning production agent deployments.

  1. vLLM Blog63

    H3-Image Day-0 Support: 4K in 0.87s with Vera Rubin

    vLLM-Omni brought MiniMax H3-Image, an open-weight text-to-image and editing model, to NVIDIA Vera Rubin, reaching 0.87 seconds median for native 4096×4096 generation on four GPUs with SP4 and MXFP8 in a short-prompt serving benchmark. A separate SP1×DP4 throughput configuration delivers 6,115 images/hour, which the authors project to 146,755 images/day and, at an assumed USD 0.06879 per image, USD 105.16/GPU/hour gross revenue at full billable utilization before operating costs. The post also documents VAE decoding gains from CUDA Graph replay plus multiple streams (2.635 s to 0.213 s on four GB300 GPUs) and community validations on AMD, Intel, Huawei Ascend and Moore Threads hardware.

    Why it matters: Useful for readers weighing open-weight 4K image serving, since it separates latency and throughput operating points and labels its revenue projections as extrapolations before operating costs.

  2. Google Blog AI80

    Gemini Decisions API: Fast, calibrated multimodal decisions

    Google introduced the Gemini Decisions API, powered by the new Gemini Decision 1 model (gemini-decision-1) and available through the Gemini API in Google AI Studio, for closed-set decisions such as tool selection, policy checks, model routing, and context grading. It accepts one multimodal input (text, images, audio, video, PDFs up to 256K tokens) with up to 1,000 yes/no, multiple-choice, and rubric-scoring questions, scoring options in a single forward pass with confidence scores at 150-250 ms end-to-end latency and $0.10 per 1M input tokens with zero output tokens billed. Google reports that Gemini Decision 1 leads across agent routing, reasoning, ranking, and multimodal benchmarks with the lowest calibration error, and is nearly 5x cheaper than Gemini 3.5 Flash-Lite with the Interactions API across the shared benchmark suite.

    Why it matters: It documents a new Google model and API with pricing, latency, and benchmark claims, useful for teams weighing low-latency classification and routing options.

  3. ElevenLabs Blog60

    ElevenLabs and NVIDIA expand collaboration to bring voice agents to enterprises and governments globally

    ElevenLabs and NVIDIA are expanding their partnership across models, infrastructure and sovereign deployments, with NVIDIA Nemotron 3.5 Super VL now available in ElevenAgents and ElevenLabs adding 15MW of NVIDIA Blackwell Ultra and Vera Rubin compute. ElevenLabs models and NVIDIA infrastructure power a sovereign voice agent for Poland's national e-Health appointment system, and the companies are exploring on-device voice AI for robotics and physical AI.

    Why it matters: It shows how voice-agent stacks are being bundled with model and compute partnerships, and includes a concrete sovereign healthcare deployment with stated operational details.

  1. AWS Machine Learning Blog60

    UAEF: A framework-agnostic system for closed-loop evaluation of AI agents

    AWS introduces the Universal Agent Evaluation Framework (UAEF), an open-source, framework-agnostic system that uses adapters to normalize agent traces from LangGraph, LangChain, Strands Agents, Amazon Bedrock AgentCore, and Langfuse into a common AgentTrace format, then scores them with 36 built-in metrics across 7 quality dimensions. Results are stored per experiment in Amazon DynamoDB and Amazon S3, enabling comparison of agent versions, regression detection, and report and insight generation, with both a Python library and a low-code web UI sharing the same engine. The post also provides a playbook for choosing metrics and preparing datasets, plus runnable notebooks for each supported framework.

    Why it matters: It offers a detailed, practical reference for teams evaluating agents across frameworks, including metric selection guidance and a closed-loop workflow for catching regressions before release.

  2. Databricks Blog71

    Genie One: The AI cowork home for everyone

    Databricks announced that Genie One is now the enterprise home for AI cowork, combining Genie Search (hybrid AI search indexing tools like Google Drive, Jira, Confluence, Workday and SharePoint, plus over 100 MCP connectors), organizational directories, in-conversation artifacts such as slide decks and dashboards, MCP-based actions across tools, shareable skills, and native apps for browser, desktop, mobile, Slack and Microsoft Teams. Genie can now take more autonomous action on users' behalf, with Unity Gateway providing traces, MCP policies, permissions and cost management, and Genie One is free for users through January 31, 2027.

    Why it matters: It details a major enterprise AI assistant release, useful for readers tracking how agentic workplace tools are being packaged with governance and cross-tool search.

  3. Databricks Blog69

    Announcing GA of Genie Ontology

    Databricks announced the General Availability of Genie Ontology, an agentic ontology layer that agents build by learning from dashboards, SQL queries, notebooks and BI semantic models, while people govern definitions through Unity Catalog semantics. The release adds Genie Search (GA), Ontology Snippets (GA), external knowledge sources (Beta, starting with Power BI), organizational directories (GA, starting with Workday), Domains and Pages (GA), and Ontology Manager (coming soon in Beta). In a benchmark built with Turing simulating a Databricks workspace for a fictional UK energy supplier, Genie answered correctly in 91% of runs versus 45% and 58% for two frontier agents, using less than half the tokens and finishing three to four times faster.

    Why it matters: It details a major enterprise context-layer release and includes benchmark numbers comparing agents with and without the ontology.

  4. Databricks Blog74

    The new Genie: autonomous AI for complex enterprise work

    Databricks introduces the new Genie, an autonomous AI coworker that continuously handles long-running enterprise work, tracking progress, following up on missing inputs, and taking action as new information arrives, with users setting guardrails and approving where needed. It is supported by Genie Ontology for business context, Genie Search for hybrid enterprise search, Unity Gateway and Unity Catalog for governance, and new capabilities including artifacts, MCP connectors, Genie Agents, and plugins for tools such as ChatGPT and Claude. Databricks reports that in a new benchmark built with Turing, Genie answered correctly in 91% of task runs, 1.6 times the rate of the stronger frontier agent, while using less than half as many tokens.

    Why it matters: The announcement details a shift from task-level AI assistance to supervised autonomous agents, with concrete governance, context, and benchmark claims worth evaluating.

  5. OpenRouter Announcements67

    MCP vs CLI vs Skills: What Each Costs in Context

    The article measures input-token costs for giving an agent GitHub access via the GitHub MCP server, the gh CLI, or a gh skill across Claude Haiku 5.5, Claude Sonnet 5.5, GPT-6 Luna, and Gemini 3.8 Flash; on Sonnet 5.5 the CLI used 1,421 tokens, the skill 3,315, and the MCP server 59,417 with its 46 default tools. It reports that the GitHub MCP server's 46 default tools add 19,436 tokens to every request on Sonnet 5.5, and that a single tool result (GitHub's release object) cost about 20,400 tokens. It also describes the beta Tool Search server tool, which cut the up-front cost of 46 tools to under 600 tokens and halved whole-task cost on Sonnet 5.5 while raising it on Haiku 5.5.

    Why it matters: It offers concrete, model-specific token and cost measurements for choosing between MCP, CLI, and skills, plus practical mitigations like scoping tools and trimming results.

  6. Cursor Blog71

    Cursor Projects is now multiplayer

    Cursor announced that Projects, its multi-agent workspace introduced in September, now supports multiplayer so teammates can plan, build and ship together alongside their agents. Projects adds a shared context system holding requirements docs, diagrams, tech specs and mockups, plus a shared task board showing who and which agents are working on what and the PR behind each task. The feature also enables agent-to-agent communication across teammates, and is rolling out in beta to all Cursor users starting today.

    Why it matters: Useful for teams evaluating collaborative AI coding tools, as it describes a shared-context multi-agent workspace and its beta availability.

  7. Pydantic AI Articles60

    Code mode is not a sandbox

    This post distinguishes code mode, where the model writes a short Python program calling your tools as functions via a single run_code tool, from a sandbox, which is an isolated environment where code runs. It describes three places a sandbox boundary can go (the whole agent, only the tools, or only the model-written code) and how Pydantic AI workspaces let you move that boundary without rewriting tools. It also covers Monty, a Rust-written Python interpreter that runs run_code next to the agent with no filesystem, network, or environment variables.

    Why it matters: Useful for teams deciding where to place isolation boundaries when combining code mode with sandboxed tool execution.

  8. Baseten Blog69

    How Baseten and Genspark trained a deep research model to outperform Opus 5.5

    Genspark worked with Baseten Applied Research to post-train Qwen3.5-397B into a specialized Deep Research model that scores 0.759 on Genspark's quality grader, up from 0.612 for the base model and above Opus 5.5 (0.738), Sonnet 5.5 (0.742), GPT-5.6 Sol (0.637), Kimi K3 (0.724) and DeepSeek V4 Pro (0.675). The recipe splits the task into research, trained with reinforcement learning against a shaped semi-verifiable reward, and synthesis, trained mainly with supervised fine-tuning on high-quality reports written from the model's own research trajectories, followed by end-to-end RL. The model crawls 5× more sources per query than the base model and runs with NVFP4 weights on 2×B200 GPUs per replica, now serving as the default for Genspark's Deep Research agent in production.

    Why it matters: A detailed, reproducible account of post-training an open model for a judged production workload, useful for teams weighing RL versus SFT and reward shaping.

  9. ElevenLabs Blog65

    Introducing Scribe v3 and v3 Live, our most accurate speech to text models

    ElevenLabs launched Scribe v3 for recorded audio, which makes 27% fewer word errors than Scribe v2 across 102 languages and has the lowest diarization error of any model tested, and Scribe v3 Live for realtime audio, which makes 43% fewer semantic word errors than Scribe v2 Realtime and adds speaker diarization and improved turn detection. Scribe v3 Live is available today in ElevenAgents, and both models are available in ElevenAPI, where switching from Scribe v2 is a one-line change to the model ID (scribe_v3 or scribe_v3_live). Both run in the US by default with isolated EU, India, and Singapore environments, Zero Retention Mode, and SOC 2, ISO 27001, PCI DSS Level 1, and HIPAA-eligible coverage.

    Why it matters: Useful for teams choosing speech-to-text models, since it details measured accuracy, diarization, and latency trade-offs plus deployment and compliance options.

  10. Amp Chronicle60

    Boxes

    Amp introduces boxes: always-on computers starting at $18 per 30 days (billed by the minute) to which users can deploy the software they build with agents, with each application getting its own URL and no containers involved. Boxes can be shared with a workspace, can be turned on and off on a schedule, and each comes with its own runner so agents can operate directly on the box.

    Why it matters: Useful for developers weighing a cheap, simple hosting option for personal or internal agent-built software.

  11. OpenRouter Announcements64

    Best OCR Model for Scanned Documents, Measured

    The author tested 15 vision models plus Mistral OCR and Tesseract on eight synthetic scanned pages scored by character error rate and 264 key-value checks, finding Claude Opus 5.5 most accurate (262 of 264 at $16.42 per 1,000 pages) and Mistral OCR the best value (258 of 264 at $2.02). The post documents failure modes such as fabricated card digits, wifi passwords and server names on a faded receipt, and provides code for transcription, disabling reasoning, cross-checking two models from different labs, and using the mistral-ocr engine.

    Why it matters: It offers a reproducible benchmark with per-model costs and practical code for catching hallucinated values in OCR pipelines.