Breaking
Advertisement

AI

AI

Google Releases TPU Sync: Open-Source KV Cache Transfer for TPUs

Google Cloud has released TPU Sync, an open-source C++ library for moving KV caches and model weights on Cloud TPUs. The Google TPU Sync KV cache transfer library treats TPU HBM, host DRAM, shared storage and the data center network as one memory hierarchy. It targets a growing bottleneck: moving model state, not computing it. Google reports over 90% lower KV transfer latency on 235B to 480B parameter MoE models. TL;DR Library: Native C++ core with Python wheels for PyTorch and JAX. Tested on 235B to 480B MoE models. Runs on: Cloud TPU v7x (Ironwood) and v6e per the README. Benchmarks used TPU v7x (2x2x1), PCIe Gen5 and 200 Gbps NICs. Performance: Large cuts to KV transfer latency and time to first token (TTFT) in Google’s internal lab tests. Best: Up to 90% lower average TTFT (480B P/D serving at low concurrency, and 64K-context prefix caching). Worst: No RL numbers published. The README says it is not yet recommended for general use. Bottom line: Best: Qwen3 235B KV transfer drops from several seconds to ~230 ms. Worst: every number is self-reported and early-stage. What is TPU Sync? TPU Sync is an open-source C++ library from Google that moves TPU-tiled tensors across memory tiers with asynchronous DMA. It handles 2 jobs: KV cache state during inference, and trainer-to-sampler weight broadcast in reinforcement learning (RL). The repository is licensed Apache-2.0. How does TPU Sync work? The library spans TPU HBM, pinned host DRAM, shared storage and multi-host DCN. Storage uses experimental POSIX backends, including local SSDs and Google Cloud Managed Lustre. Google lists 4 design choices: Layout-preserving direct DMA: It reads JAX PJRT buffers or PyTorch tensors in place. Data keeps its native TPU tile layout, with no Python serialization or bounce buffers. Compute-overlapped transfers: Raw PJRT buffer aliases let transfers run during computation. Built-in DMA pacing stops large copies from delaying kernel launches. No XLA compilation in the data path: Transfers and resharding run in native C++ outside the XLA graph. High-bandwidth PCIe and DCN: It reaches up to 223 GB/s per Ironwood host, against a 256 GB/s PCIe Gen5 ceiling. DCN streaming hits ~192 Gbps on 1 NIC, or ~350 Gbps across 2. Above this sit a global KV store for prefix lookups, a transfer controller and a KV cache manager. How does disaggregated prefill/decode serving use it? The prefill node offloads KV blocks to pinned host RAM through async DMA. The controller streams them host-to-host to the assigned decode node. Arriving blocks move into decode-node HBM while decoding continues. #mtp-tpusync-embed iframe{width:100%!important;border:0!important;display:block!important;background:transparent!important}#mtp-tpusync-embed hr,#mtp-tpusync-embed p:empty,#mtp-tpusync-embed del,#mtp-tpusync-embed s{display:none!important} window.addEventListener("message",function(e){if(e.data&&e.data.mtpTpuSyncHeight){document.getElementById("mtp-tpusync-frame").style.height=e.data.mtpTpuSyncHeight+"px";}}); What do the TPU Sync benchmarks show? Google ran internal tests in July 2026 on TPU v7x (2x2x1). The stack was tpu-inference v0.24.0, JAX 0.10.2 and libtpu 0.0.42.1. Google team states that real-world results will vary. For P/D disaggregated serving: KV transfer overhead fell by over 90%. Qwen3 235B median KV transfer latency dropped from several seconds to ~230 ms. Average TTFT fell 60% for 235B and 90% for 480B at low concurrency. Token output throughput rose 30% to 70% for 235B during traffic spikes. For prefix caching: Effective cache capacity grew by an order of magnitude when MoE weights fill most of HBM. Average TTFT fell by up to 90% on 64K-context workloads. Throughput rose over 50%, and P99 inter-token latency fell 30%. Which frameworks does TPU Sync support? TPU Sync integrates with PyTorch through TorchTPU and with JAX natively. In vLLM-TorchTPU, it is the TPU KV connector behind vLLM’s KVConnector interface. In SGLang-TorchTPU, it is the P/D transfer backend and hierarchical cache I/O backend. On GKE, llm-d 1.0 uses it for prefix-cache-affinity routing and experimental spill to Managed Lustre. Inferact and RadixArk co-engineered the vLLM and SGLang integrations. Google says Meta and Wayfair are evaluating the architecture. How does TPU Sync compare with GPU-side alternatives? The bandwidth figures measure different paths. TPU Sync’s number is host PCIe DMA. Mooncake’s number is network transfer over RoCE. Key Takeaways TPU Sync is Google’s Apache-2.0 C++ library for KV cache and weight movement on TPUs. It reaches up to 223 GB/s per Ironwood host through direct, layout-preserving DMA. Qwen3 235B KV transfer fell from several seconds to ~230 ms in Google’s tests. It plugs into vLLM-TorchTPU, SGLang-TorchTPU and llm-d on GKE. RL and storage tiering are experimental, and every number is self-reported. Check out the technical blog, the GitHub repo, vLLM-TorchTPU and SGLang-TorchTPU. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Google Releases TPU Sync: Open-Source KV Cache Transfer for TPUs appeared first on MarkTechPost.

AI

Google Releases Gemini 4 Hydrogen: 2.5x Faster Than Gemini 3.8 Flash

Google has released Gemini 4 Hydrogen, a fast model for coding and agentic work. Gemini 4 Hydrogen is a proprietary model from Google DeepMind built for everyday agent loops. It sits below the frontier models Gemini 4 Carbon and Gemini 4 Argon. Google calls it its “daily driver for agentic workflows.” TL;DR Size: 1,048,576-token unified window for input, thinking and output. Runs on: Google-hosted API only. No weights, no quantized variants, no self-hosting. Serving hardware not disclosed. Performance: Scores 51 on the Artificial Analysis Intelligence Index at high, above Argon’s 50. Best: 57% on Terminal-Bench 4.1, versus 18.2% for Gemini 3.8 Flash. Worst: Ranks only #5 on Agent Arena. Costs 2x Gemini 3.8 Flash’s current introductory price. Bottom line: Best: frontier-class agent scores at $1.50/$7.50 per 1M tokens. Worst: closed, and synchronous output caps at 65,536 tokens. What is Gemini 4 Hydrogen? Hydrogen is a closed-weights model served through the Gemini API and Google products. The model card says it is adapted from Gemini 4 Carbon. Google does not disclose parameter count, architecture or training hardware. The knowledge cutoff is March 2026. Input covers text, images, audio, video, PDFs, tables and charts, per the What’s New guide. Output is text. The 1M window is shared by input, thinking and output tokens. How do the 4 thinking levels work? Developers set thinking_level inside generation_config. Values are low, medium, high and a new xhigh. The default is high, not medium as on 3.8 Flash. A minimal setting now returns an error. The model card warns that higher levels use more tokens. How does Hydrogen work with Carbon and Argon? The key design idea is role-splitting across models. In Google Antigravity, an Orchestrator option switches models inside 1 task. Carbon explores, resolves ambiguity and plans. Hydrogen edits files, updates packages and runs tests. When Hydrogen hits friction, it hands control back to Carbon. On Terminal-Bench 4.1, this pairing reached near-Carbon task success rates. It used 24% less quota and finished 19% faster than Carbon alone. The Antigravity SDK exposes the same split for custom multi-agent systems. How does Gemini 4 Hydrogen perform on benchmarks? All figures are self-reported by Google unless noted. Artificial Analysis Intelligence Index: 51 at high, 54 at xhigh. Argon scores 50 on Index v5.0. Terminal-Bench 4.1: 57%, versus 18.2% for 3.8 Flash. HLE-Diamond: 58.8%, leading its class. Vals Tax Agent Bench: 52.3%, ranked #1 overall. Vals Legal Research Bench: 55.8%, tied for #1. Multimodal Knowledge Agent: 53.4%. Agents’ Last Exam v1.1: 71.6%. Agent Arena: ranked #5. Speed is the headline claim. Hydrogen finishes tasks 2.5x faster than 3.8 Flash at the default high level. In partner tests, it ran 2x to 2.8x faster with 12% to 23% fewer tokens. Google also reports more than 5x fewer fabricated claims than 3.8 Flash. It scored 96.7% on an internal agent honesty evaluation. It was 2.3x more resilient to indirect prompt injection on Gray Swan’s benchmark. window.addEventListener('message',function(e){var d=e.data;if(d&&d.mtpEmbed==='g4h'&&d.h){var f=document.getElementById('mtp-g4h-frame');if(f)f.style.height=d.h+'px';}}); How much does Gemini 4 Hydrogen cost? The API price is $1.50 per 1M input tokens and $7.50 per 1M output tokens. Pricing is flat across the full window. Output pricing includes thinking tokens. Implicit caching cuts input to $0.075 per 1M for prompts of 4,096 tokens or more. Explicit caching is not supported. The price context matters. Gemini 3.8 Flash costs $0.75/$3.75 until December 31, 2026. From January 1, 2027, it rises to $1.50/$7.50, matching Hydrogen. Argon costs $2/$10 until November 30, 2026, then $4/$20. Where can developers use Gemini 4 Hydrogen? The model ID is gemini-4-hydrogen. It is live in the Gemini API, Google AI Studio on all tiers, and Android Studio. It also ships in Gemini for business, the Gemini app, Google Search and Sheets. Antigravity access requires Google AI Pro or Ultra. Vertex AI is not mentioned in the launch posts. Migration from 3.8 Flash needs a few changes. Remove temperature, top_p and top_k, since the server ignores them. Remove cached_content fields. Raise hardcoded max_output_tokens caps to 65,536. Gemini 4 Hydrogen vs competitors Terminal-Bench 4.0 and 4.1 are different versions, so cross-version scores are not directly comparable. Key Takeaways Hydrogen scores 51 on the AA Index, above Argon’s 50, per Google. It hits 57% on Terminal-Bench 4.1, versus 18.2% for 3.8 Flash. Pricing is $1.50/$7.50 per 1M tokens, flat across 1M context. Default thinking is now high, with a new xhigh tier. Pair it with Carbon in Antigravity for 24% lower quota use. Check out the launch post, the model card, the developer post and the What’s New guide. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Google Releases Gemini 4 Hydrogen: 2.5x Faster Than Gemini 3.8 Flash appeared first on MarkTechPost.

AI

Liquid AI Releases LiquidCodec, a 74M-Parameter Streaming Audio Codec

Liquid AI has released LiquidCodec, the audio codec behind its LFM3-Audio-2B and LFM3-Omni-2B models. The LiquidCodec audio codec is a ~74M-parameter streaming speech tokenizer. It turns speech into tokens a language model can predict, then converts those tokens back into audio. Liquid AI had 2 goals: easy-to-predict tokens and fast conversion back to speech. The weights are on Hugging Face. TL;DR Size: ~74M parameters (73.6M on the model card); 24 kHz audio, 12.5 Hz frames, 12 codebooks. Runs on: a single CPU thread (tested on an Apple M4 Max laptop, FP32); CUDA GPUs via Transformers; Q4_0, Q4_K_M and Q8_0 GGUF builds for llama.cpp. Performance: best ViSQOL and lowest mel distance on all 8 test sets versus X-Codec 2, NanoCodec and Mimi. Best: ~361x real-time encoding on 1 CPU thread (encode RTF 0.0028 vs Mimi’s 0.0361). What is LiquidCodec? LiquidCodec is a Liquid AI speech codec that compresses 24 kHz audio into 12 token streams. Each 80 ms frame becomes 12 discrete tokens, per the LFM3-Audio-2B model card. It replaces Kyutai’s Mimi, which Liquid AI used in LFM2-Audio-1.5B. Mimi has 96.2M parameters. How does LiquidCodec work? The pipeline is encode, quantize, decode. Liquid AI uses blocks from its LFM3 architecture in both the encoder and decoder. The 2 halves are symmetric, and the encoder is fully causal, which suits streaming. Quantization uses grouped finite scalar quantization (GFSQ) instead of residual vector quantization (RVQ). In RVQ, each codebook encodes what the previous one missed. GFSQ groups are independent, so all 12 codebooks can be predicted in parallel by MaskGIT-style transformers. The decoder predicts spectral coefficients directly. This avoids learned transposed-convolution upsampling, a common cost in waveform decoders. How was it trained? Training ran in 2 stages. Stage 1 used 264,000 hours of speech across 107 languages. It applied waveform and spectral losses, without adversarial losses. Stage 2 fine-tuned on 55,000 hours of full-band speech (24 kHz or higher) with adversarial critics. Liquid AI says this removed metallic artifacts left after stage 1. A final decoder-only quantization-aware training (QAT) step targets edge inference. How fast is LiquidCodec? Liquid AI measured speed in FP32 on 1 CPU thread of an Apple M4 Max MacBook Pro. LiquidCodec ran at ~361x real time for encoding and ~87x for decoding. These are self-reported figures. Real-time factor (RTF) is processing time divided by audio length, so lower is better. LiquidCodec’s encode RTF is 0.0028, against 0.0361 for Mimi, 0.2145 for NanoCodec and 0.7359 for X-Codec 2. Decode RTF is 0.0115, against 0.0329, 0.2543 and 0.0379. That is about 13x lower encode RTF and 2.9x lower decode RTF than Mimi. How does LiquidCodec compare on quality benchmarks? Liquid AI used 8 test sets. These were LibriSpeech test-clean, Seed-TTS English and Mandarin, and 5 FLEURS languages (German, French, Mandarin, Japanese, Korean). Baselines were X-Codec 2, NanoCodec and Mimi at 12 codebooks. Reconstruction: LiquidCodec had the best ViSQOL and lowest mel distance on all 8 sets. On LibriSpeech, ViSQOL was 4.319 versus 4.219 (NanoCodec), 4.119 (X-Codec 2) and 4.031 (Mimi). Text-to-speech: Liquid AI trained identical TTS models on each codec’s tokens. Data (101,000 hours, 6 languages), architecture, compute and batch order were fixed. LiquidCodec scored the highest UTMOSv2 on all 8 sets and the best WER/CER on 4 of 8. LibriSpeech WER was 3.15%, against 6.27% for Mimi. Results held with a Qwen3-1.7B backbone as well as LFM3-1.7B. Where it trails: NanoCodec scored higher PESQ (WB) on 7 of 8 sets. It also led on LibriSpeech speaker similarity (SECS 0.836 vs 0.785). (function(){var f=document.getElementById("mtp-lc-frame");window.addEventListener("message",function(e){if(e.source===f.contentWindow&&e.data&&e.data.mtpLcHeight){f.style.height=e.data.mtpLcHeight+"px";}});})(); LiquidCodec vs Mimi vs NanoCodec vs X-Codec 2 *Measured by Liquid AI in its LiquidCodec blog. Mimi measured at 12 codebooks. How can developers deploy LiquidCodec? The codec loads through Hugging Face Transformers with trust_remote_code=True. Call encode() to get audio codes and decode() to get a waveform. A native LiquidCodecStreamingCache supports chunk-by-chunk decoding, per the model card. The card’s examples use CUDA with bfloat16. For edge use, Liquid AI lists Q4_0, Q4_K_M and Q8_0 GGUF builds for llama.cpp. GGUF repos ship with LFM3-Audio-2B and LFM3-Omni-2B. Q4_0 with decoder-only QAT shrinks the decoder footprint by 3.5x. LibriSpeech ViSQOL dips only from 4.319 to 4.292. Key Takeaways ~74M-parameter streaming codec, 12.5 Hz, 12 codebooks, 24 kHz. ~361x real-time encode, ~87x decode on 1 CPU thread. Best ViSQOL, mel distance and TTS UTMOSv2 on all 8 test sets. NanoCodec still wins PESQ (WB) on 7 of 8 sets. Q4_0 decoder is 3.5x smaller with minimal quality loss. Check out the technical blog, the model weights on Hugging Face, and LFM3-Audio-2B and LFM3-Omni-2B. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Liquid AI Releases LiquidCodec, a 74M-Parameter Streaming Audio Codec appeared first on MarkTechPost.

Advertisement
AI

CopilotKit Releases OpenBot 1.0: An MIT-Licensed, Self-Hostable AI Coworker With Built-In Governance

Most AI coworker products are vendor locked. They pick the model, host the data, and write the rules. CopilotKit is taking the opposite route. OpenBot 1.0, was released November 9th, an MIT-licensed, self-hostable agent workspace. What sets it apart is, a company brings their own models, agents and infrastructure. Governance is fully baked in, and every Bot action is checked against a policy before it runs. What is OpenBot? OpenBot is a modular agent workspace from CopilotKit, the team behind the AG-UI protocol. You give a Bot a task and watch it work. You review findings, interact with results and approve next steps in the same conversation. Each Bot gets a computer of its own. That is a container with its own Chromium browser, logins and files. It reaches only the tools you grant. Answers can come back as charts, checklists, tables and cards. In the new v1.0, Bots now reply in Markdown by default and draw components when they help. How does the governance gateway work? Every browser click, file write, MCP tool call and component goes through one gateway. It evaluates a CEL policy, writes the audit row first, then acts. Deny rules run before allow rules, and a broken rule refuses rather than opens. On top of that, the business tier adds: Single sign-on and SCIM sync for users and groups. The README documents Google, Microsoft (Entra) and Okta, plus SAML and OIDC. On-behalf-of tokens, usually scoped to a subset of the person’s permissions. Tool grants per Bot, per role or per person, with access requests to an admin. Policies that block actions or route sensitive work to a human for approval. Spend visibility per Bot, role, team or person, plus daily, weekly or monthly token limits. A full audit trail with SIEM export, multi-tenancy and an admin plane. EU AI Act content labeling, retention controls and deletion on request. CopilotKit itself holds SOC 2 Type II. Which agents and models can you bring? Any agent that speaks AG-UI plugs in. The site lists 8 frameworks: Claude Agent SDK, OpenAI Agents SDK, LangChain, Google ADK, Mastra, AWS Strands, Microsoft Agent Framework, CrewAI. The repo also ships Agno, AG2, LlamaIndex and Pydantic AI examples. For models, teams can use OpenAI, Claude, Gemini or Grok through existing subscriptions or API keys. Open models such as Kimi, DeepSeek, Qwen, Nemotron and Mistral are also supported. Sandboxes, MCP hubs and browsers are swappable lanes. What is new in OpenBot 1.0? Desktop app for Mac (Apple Silicon and Intel) and Windows, with signed updates and backup before upgrade. Teach a Bot: record a task once, and Learning turns the recording into a reusable skill you review. Multiple accounts per app through Composio and Arcade, with approval rules saved per account. Composio alone brokers a few hundred apps. Orchestration: one Bot can hand work to specialist Bots, within admin-granted pairs and depth limits. Early access for iOS, Android, Slack (through OpenTag) and Microsoft Teams. How do you deploy it? Personal use runs locally, with workspace data and API keys stored on your machine. For companies, 1 Helm chart deploys into AWS (EKS), Azure (AKS), Google Cloud (GKE) or any Kubernetes cluster. Pricing is free for personal projects. OpenBot for Business costs up to $29 per active user per month. A 5% charge applies only to model spend above $5,000 per month. The Annual plan adds air-gapped deployment and 24/7 support. Forward-deployed engineers help teams roll it out. Example use cases Ticket triage: route new support tickets, then post to Slack after a person approves. Expense review: check each claim line against policy and flag overages. Ops workflows: find problems and draft fixes for a human to approve. How does OpenBot compare? Key Takeaways OpenBot 1.0 is MIT-licensed and self-hostable, from laptop to Kubernetes. Any AG-UI agent and 9 model families plug in. Every Bot action passes a policy check before it runs. Business tier: up to $29 per active user per month. Check out the GitHub repo, v1.0.0 release notes and open.bot. Thanks to the Copilotkit team for the thought leadership / resources for this article. This article is sponsored by Copilokit. The post CopilotKit Releases OpenBot 1.0: An MIT-Licensed, Self-Hostable AI Coworker With Built-In Governance appeared first on MarkTechPost.

AI

Claude Meetings lets Anthropic’s AI join your video calls

Anthropic is adding Claude directly to video calls. Claude Meetings joins Google Meet sessions and creates documents, whiteboards, and meeting notes in real time. The feature launches in beta for Team and Enterprise plans, with more platforms coming later. The article Claude Meetings lets Anthropic's AI join your video calls appeared first on The Decoder.

AI

Google’s Gemini 4 Hydrogen outscores the bigger Argon just four weeks after its launch

Google's Gemini 4 Hydrogen replaces the Flash series, but benchmarks suggest it also makes the pricier Argon obsolete. On the independent Artificial Analysis Intelligence Index, Hydrogen nearly matches Claude Sonnet 5.5 for less money but costs about 2.5 times more per task than GPT-6.1 Sol and still falls short on agentic coding. The article Google's Gemini 4 Hydrogen outscores the bigger Argon just four weeks after its launch appeared first on The Decoder.

Advertisement
AI

AWS Releases AWS Emulator: A Local Copy of 200+ AWS Services Built by AI Agents

AWS has released AWS Emulator, a local emulator of the AWS APIs. You run it on a laptop, a dev server or in CI. The AWS CLI and SDKs talk to it instead of AWS. No AWS account is needed, and there is no service fee. The unusual part: autonomous agents wrote and reviewed all of its code. For developers and coding agents, AWS Emulator gives a fast, free test loop against AWS-shaped APIs. TL;DR Size: Built from 438 AWS API models, covering 200+ services. One Rust crate per service. Runs on: Linux x86_64/aarch64 (RPM or Debian), or Docker on macOS/Windows with a 2 GiB memory limit. Source builds need 100 GB of free disk. Performance: Passes 24,243 of 42,857 scored fidelity tests (56.6%) in release v1.0.322. Best: AWS KMS at 93.9% (291 of 310 tests); Amazon SQS at 89.8%. Worst: AWS CloudFormation at 15.8% (414 of 2,612 tests). What is AWS Emulator? AWS Emulator is a headless local program from AWS that serves an AWS API endpoint. You point the CLI or an SDK at it with environment variables. Your code does not change. Resources live in memory and vanish when it stops. The docs show a DynamoDB example. A CreateTable call with a 2-character name fails with the same ValidationException text AWS returns. How did AI agents build AWS Emulator? The project began with a prompt to Kiro. It returned a passable Amazon SQS emulator in about 15 minutes. AWS then split the work across 3 teams of agents: Test writers derive scenarios from the public Smithy API models and verify each against real AWS. Issue finders replay those tests against the emulator and file failures. Fixers take 1 issue each and submit a patch. Every patch passes a merge gate covering build, code review, security and fidelity. Several security agents run adversarial reviews. Matthew Goldberg reports hundreds of concurrent agents fixing thousands of issues a day. The release pipeline runs on AWS Developer Tools, with CodeCommit as the agents’ repository. Code reaches GitHub last. window.addEventListener("message",function(e){var f=document.getElementById("mtp-awsemu-frame");if(f&&e.source===f.contentWindow&&e.data&&e.data.mtpH){f.style.height=e.data.mtpH+"px";}}); How accurate is AWS Emulator? AWS publishes a scores.json file with each release. We tallied the v1.0.322 file, scored on November 11, 2026. Overall: 24,243 of 42,857 scored tests pass (56.6%); 80 were skipped. Step level: 49,810 of 68,007 individual steps pass (73.2%). Cross-service workflows: 2,752 of 6,569 pass (41.9%). Core services: S3 79.1%, DynamoDB 77.3%, SNS 73.9%, Lambda 46.4%, EC2 41.5%. Per the fidelity docs, control-plane APIs match AWS best. Data-plane, CloudFormation, Terraform and CDK support varies by service. Unimplemented operations return HTTP 501 NotImplemented. The tests live in aws-emulator-evaluation-suite, including failing ones. How do you run AWS Emulator? There are 4 paths, per the README: Linux: install the RPM or Debian package and run aws-emulator. macOS/Windows: build a container from AWS’s Dockerfile, capped at 2 GiB memory. Rust embedded mode: add it as a dev-dependency for 1 isolated instance per test. Coding agents: aws agent-toolkit add-skill --skill-name aws-emulator, with AWS CLI 2.35.0 or later. A source build serves HTTPS on 127.0.0.1:9297 with a self-signed certificate. It needs a Rust toolchain, a C compiler and at least 100 GB of disk. Embedded mode carries the same build cost on the first cargo test. How does it compare with LocalStack, Moto and Floci? What are AWS Emulator’s limitations? AWS lists them plainly: No IAM evaluation. Identity and resource policies are not evaluated like AWS. Do not use it for security tests. 1 Region, 1 account. It accepts any IDs but does not isolate resources by them. Verified in us-west-2 only, with global services checked in us-east-1. In-memory and short-lived. It is not tested for long runs or load tests. Use --idle-timeout to stop it. Telemetry is on by default. Turn it off with --telemetry off, EMULATOR_TELEMETRY=off, config.toml or the embedded API. The release pace is fast. Versions v1.0.265 to v1.0.322 shipped between November 8 and 11. Key Takeaways AWS Emulator is a free, CC0 local copy of 200+ AWS services. Agents wrote all the code; humans built the tests and merge gates. It passes 56.6% of 42,857 published fidelity tests at launch. SQS, KMS and S3 are strong; CloudFormation and IoT lag. Use it for fast local and CI loops, not security or load testing. Check out the GitHub repo, the user guide, the fidelity tests and the engineering post. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post AWS Releases AWS Emulator: A Local Copy of 200+ AWS Services Built by AI Agents appeared first on MarkTechPost.

AI

OpenAI’s data suggests that frontier models are hiding their thoughts because developers optimize for capability and compute

OpenAI's safety team systematically investigated why the chains of thought in frontier models like GPT-6 Astra are increasingly evading oversight. Four training steps drive the erosion, including architecture choices and reinforcement learning. The analysis shows that the loss of transparency is not a law of nature but also reflects tradeoffs around capability and cost. The article OpenAI’s data suggests that frontier models are hiding their thoughts because developers optimize for capability and compute appeared first on The Decoder.

Advertisement
AI

ElevenLabs Scribe v3 Live uses conversational context to stop voice agents from cutting off callers mid-sentence

ElevenLabs has released Scribe v3 and Scribe v3 Live, two new speech recognition models designed to transcribe accurately through background noise and crosstalk. Benchmarks from Artificial Analysis confirm that Scribe v3 narrowly beats competitors like OpenAI, Google, and Microsoft on accuracy. That precision comes at a cost, though. Rivals like Microsoft and xAI run many times faster and charge roughly half the price. The article ElevenLabs Scribe v3 Live uses conversational context to stop voice agents from cutting off callers mid-sentence appeared first on The Decoder.