←Search results

By relevance · Total 51 results Clear search

Tuesday

  1. AWS Machine Learning

    AWS explains prompt caching patterns for using OpenAI models on Amazon Bedrock

    AWS has published a tutorial explaining how to use prompt caching to reduce the cost of agents repeatedly reading context when calling OpenAI models on Amazon Bedrock, distinguishing between two approaches—implicit caching and explicit prompt_cache_breakpoint—and recommending their combined use. The article provides code examples for tool and instruction caching, rolling breakpoints across multi-turn history, adding tools mid-session, and shared prefixes across sub-agents, and states that in a six-turn workload on GPT-6 Astra, implicit caching reduces input costs by about 62%, while explicit rolling breakpoints reduce them by about 61%. Cacheable prefixes must be at least 1024 tokens, and cache writes are billed at 1.25 times the normal input price.

    Five growing agent requests, with tools, instructions, and earlier history marked in red and each new turn in yellow.

    AWS has published a tutorial explaining how to use prompt caching to reduce the cost of agents repeatedly reading context when calling OpenAI models on Amazon Bedrock, distinguishing between two approaches—implicit caching and explicit prompt cache breakpoint—and recommending their combined use. The article provides code examples for tool and instruction caching, rolling breakpoints across multi-turn history, adding tools mid-session, and shared prefixes across sub-agents, and states that in a s

    Matched fieldsTitle、Summary、Body

Thursday

  1. AWS Machine Learning

    AWS team open-sources multi-agent system Deep Insight, breaking down five major challenges in production environments

    The AWS Solutions Architecture team built and open-sourced the multi-agent system Deep Insight, which can transform CSV data and natural language prompts into cited .docx analysis reports. The system consists of eight agents—Coordinator, Planner, Supervisor, Coder, Validator, Reporter, Tracker, and others—collaborating in layers, controlling execution flow based on the Graph and Agents-as-Tools patterns of the Strands Agents SDK, and selecting Claude Haiku, Opus, and Sonnet by role. Production deployment relies on the Amazon Bedrock AgentCore runtime; LLM-generated code is executed in isolation within per-session ephemeral containers on AWS Fargate, accompanied by a Web UI and an Ops dashboard.

    Deep Insight architecture: the Strands Agents multi-agent layer on Amazon Bedrock AgentCore, with an Application Load Balancer routing code execution to AWS Fargate containers in a private VPC

    The AWS Solutions Architecture team built and open-sourced the multi-agent system Deep Insight, which can transform CSV data and natural language prompts into cited .docx analysis reports. The system consists of eight agents—Coordinator, Planner, Supervisor, Coder, Validator, Reporter, Tracker, and others—collaborating in layers, controlling execution flow based on the Graph and Agents-as-Tools patterns of the Strands Agents SDK, and selecting Claude Haiku, Opus, and Sonnet by role. Production d

    Matched fieldsTitle、Summary、Body

  2. Story1 reports · 1 facts

    AWS Solutions Architecture team builds multi-agent system Deep Insight

    The AWS Solutions Architecture team built and open-sourced the multi-agent system Deep Insight, which can transform CSV data and natural language prompts into cited .docx analysis reports. The system consists of eight agents—Coordinator, Planner, Supervisor, Coder, Validator, Reporter, Tracker, and others—collaborating in layers, controlling execution flow based on the Graph and Agents-as-Tools patterns of the Strands Agents SDK, and selecting Claude Haiku, Opus, and Sonnet respectively by role. Production deployment relies on the Amazon Bedrock AgentCore runtime; LLM-generated code is executed in isolation in per-session temporary containers on AWS Fargate, accompanied by a Web UI and Ops dashboard. Currently this fact is reported only by a single source, AWS Machine Learning, and there are no subsequent developments.

    The AWS Solutions Architecture team built and open-sourced the multi-agent system Deep Insight, which can transform CSV data and natural language prompts into cited .docx analysis reports. The system consists of eight agents—Coordinator, Planner, Supervisor, Coder, Validator, Reporter, Tracker, and others—collaborating in layers, controlling execution flow based on the Graph and Agents-as-Tools patterns of the Strands Agents SDK, and selecting Claude Haiku, Opus, and Sonnet respectively by role.

    Matched fieldsTitle

  3. FactRelated story

    AWS Solutions Architecture team builds multi-agent system Deep Insight

    The AWS Solutions Architecture team built and open-sourced the multi-agent system Deep Insight, which can transform CSV data and natural language prompts into cited .docx analysis reports. The system consists of eight agents—Coordinator, Planner, Supervisor, Coder, Validator, Reporter, Tracker, and others—collaborating in layers, controlling execution flow based on the Graph and Agents-as-Tools patterns of the Strands Agents SDK, and selecting Claude Haiku, Opus, and Sonnet respectively by role. Production deployment relies on the Amazon Bedrock AgentCore runtime; LLM-generated code is executed in isolation in per-session temporary containers on AWS Fargate, accompanied by a Web UI and Ops dashboard. Currently this fact is reported only by a single source, AWS Machine Learning, and there are no subsequent developments.

    Matched fieldsTitle

    View story:AWS Solutions Architecture team builds multi-agent system Deep Insight

Wednesday

  1. AWS Machine Learning

    i14 Trains and Deploys the Laplace 3B Linear Attention Model on AWS Trainium2 Using Native PyTorch

    i14 partnered with AWS to train and deploy Laplace 3B, based on Gated Linear Attention, on AWS Trainium2 using TorchNeuron Native. A single trn2.48xlarge achieves a training throughput of about 120,000 tokens/s. The model's recurrent state per sequence is fixed at 29.5 MB and does not grow with context length; inference reaches 11,544 output tokens/s at 1,280 concurrent sequences. The team also reworked Muon's all_to_all communication to cut per-GPU communication volume by 24x and raise training throughput by 1.63x.

    NeuronCore-v3 internal architecture

    i14 partnered with AWS to train and deploy Laplace 3B, based on Gated Linear Attention, on AWS Trainium2 using TorchNeuron Native. A single trn2.48xlarge achieves a training throughput of about 120,000 tokens/s. The model's recurrent state per sequence is fixed at 29.5 MB and does not grow with context length; inference reaches 11,544 output tokens/s at 1,280 concurrent sequences. The team also reworked Muon's all to all communication to cut per-GPU communication volume by 24x and raise training

    Matched fieldsTitle、Summary、Body

  2. AWS Machine Learning

    AWS Publishes Agent Registry Runtime Tool Discovery Practice

    AWS introduces the Agent Registry runtime tool discovery approach: agents use hybrid semantic and keyword search to find approved MCP servers and A2A agents, then instantly build clients from descriptors to execute requests. The sample code is based on Amazon Bedrock AgentCore Gateway and runtime, integrates an order management MCP server and two A2A agents for pricing and customer service, and demonstrates a return and refund scenario using pure semantic matching. The registry returns only connection metadata; invocation credentials must be obtained separately through Cognito OAuth or IAM, and new capabilities require no changes to orchestrator code.

    Comparison of hardcoded tool endpoints versus runtime discovery with AWS Agent Registry

    AWS introduces the Agent Registry runtime tool discovery approach: agents use hybrid semantic and keyword search to find approved MCP servers and A2A agents, then instantly build clients from descriptors to execute requests. The sample code is based on Amazon Bedrock AgentCore Gateway and runtime, integrates an order management MCP server and two A2A agents for pricing and customer service, and demonstrates a return and refund scenario using pure semantic matching. The registry returns only conn

    Matched fieldsTitle、Summary、Body

  3. FactRelated story

    i14 migrates its custom architecture to AWS Trainium2

    i14 migrated its custom architecture to AWS Trainium2. According to information released by AWS Machine Learning on October 21, 2026, i14 collaborated with AWS to train and deploy the Gated Linear Attention-based Laplace 3B model on AWS Trainium2 using TorchNeuron Native. Training throughput on a single trn2.48xlarge is approximately 120,000 tokens/s; the model's recurrent state is fixed at 29.5 MB per sequence and does not grow with context length; inference reaches 11,544 output tokens/s at 1,280 concurrent sequences. The team also reworked Muon's all_to_all communication, reducing per-card communication volume by 24x and increasing training throughput by 1.63x. There are currently no subsequent developments.

    Matched fieldsTitle

    View story:i14 migrates its custom architecture to AWS Trainium2

Sunday

  1. Databricks Blog

    Databricks uses Lakebase branching to create an independent database per PR: a CI/CD practice

    Databricks describes Snorkel AI's CI/CD solution that uses Lakebase branching to create an independent read-write database for each open PR, reducing branch readiness time from over 30 minutes to under 60 seconds. Branches use copy-on-write; on a production dataset of about 2.5 TB, 100 concurrent PR branches store only 5 to 10 GB of data each for their own changes, and TTL automatically cleans them up after the PR ends. Production data is continuously synchronized to the main branch via AWS DMS; developers log in with Okta SSO, and the CI pipeline authenticates with a service principal and short-lived OAuth tokens.

    image1.png

    for each open PR, reducing branch readiness time from over 30 minutes to under 60 seconds. Branches use copy-on-write; on a production dataset of about 2.5 TB, 100 concurrent PR branches store only 5 to 10 GB of data each for their own changes, and TTL automatically cleans them up after the PR ends. Production data is continuously synchronized to the main branch via AWS DMS; developers log in with Okta SSO, and the CI pipeline authenticates with a service principal and short-lived OAuth tokens.

    Matched fieldsSummary、Body

  2. Story1 reports · 1 facts

    Databricks describes how Snorkel AI uses Lakebase branches to support CI/CD

    On November 1, 2026, Databricks published a post describing how Snorkel AI uses Lakebase branches to create an independent, read-write database for each open PR in its CI/CD practice. According to the Databricks blog, this approach reduces branch readiness time from over 30 minutes to under 60 seconds; branches use copy-on-write, and on a production dataset of about 2.5 TB, 100 concurrent PR branches store only an additional 5 to 10 GB of data for their respective changes, with automatic cleanup via TTL after the PR ends. Production data is continuously synchronized to the main branch via AWS DMS, developers log in with Okta SSO, and the CI pipeline authenticates with a service principal and short-lived OAuth tokens. There are currently no further developments.

    30 minutes to under 60 seconds; branches use copy-on-write, and on a production dataset of about 2.5 TB, 100 concurrent PR branches store only an additional 5 to 10 GB of data for their respective changes, with automatic cleanup via TTL after the PR ends. Production data is continuously synchronized to the main branch via AWS DMS, developers log in with Okta SSO, and the CI pipeline authenticates with a service principal and short-lived OAuth tokens. There are currently no further developments.

    Matched fieldsSummary

Saturday

  1. AWS Machine Learning

    Amazon SageMaker AI Multi-Turn Reinforcement Learning Practical Guide: Training gpt-oss-20b with a Wordle Example

    AWS has published a practical guide for multi-turn reinforcement learning (MTRL) on Amazon SageMaker AI. Using Wordle as an example, it deploys the agent and reward function to Amazon Bedrock AgentCore, and the training job updates LoRA adapters via GRPO. In the example, gpt-oss-20b at default reasoning effort improved its solve rate on held-out words from 61% to 84%, at a training token cost of about $339 and an AgentCore runtime cost of about $79. The article also details failures such as two inverted reward design errors, token invalidation under concurrency, and tool calls degrading into plain text, and recommends evaluating under the decoding settings used in final serving.

    SageMaker AI training job connected to the AgentCore-hosted agent, Wordle environment, and reward function

    AWS has published a practical guide for multi-turn reinforcement learning (MTRL) on Amazon SageMaker AI. Using Wordle as an example, it deploys the agent and reward function to Amazon Bedrock AgentCore, and the training job updates LoRA adapters via GRPO. In the example, gpt-oss-20b at default reasoning effort improved its solve rate on held-out words from 61% to 84%, at a training token cost of about $339 and an AgentCore runtime cost of about $79. The article also details failures such as two

    Matched fieldsSummary、Body

Wednesday

Friday

Wednesday

Friday

Wednesday

Monday

  1. Story1 reports · 1 facts

    i14 migrates its custom architecture to AWS Trainium2

    i14 migrated its custom architecture to AWS Trainium2. According to information released by AWS Machine Learning on October 21, 2026, i14 collaborated with AWS to train and deploy the Gated Linear Attention-based Laplace 3B model on AWS Trainium2 using TorchNeuron Native. Training throughput on a single trn2.48xlarge is approximately 120,000 tokens/s; the model's recurrent state is fixed at 29.5 MB per sequence and does not grow with context length; inference reaches 11,544 output tokens/s at 1,280 concurrent sequences. The team also reworked Muon's all_to_all communication, reducing per-card communication volume by 24x and increasing training throughput by 1.63x. There are currently no subsequent developments.

    i14 migrated its custom architecture to AWS Trainium2. According to information released by AWS Machine Learning on October 21, 2026, i14 collaborated with AWS to train and deploy the Gated Linear Attention-based Laplace 3B model on AWS Trainium2 using TorchNeuron Native. Training throughput on a single trn2.48xlarge is approximately 120,000 tokens/s; the model's recurrent state is fixed at 29.5 MB per sequence and does not grow with context length; inference reaches 11,544 output tokens/s at 1,

    Matched fieldsTitle

Sunday

Thursday

  1. Google Developers BlogSelected

    Google A2UI Team and CopilotKit Explain How to Build Generative UI Applications

    The Google A2UI team and CopilotKit CEO Atai Barkai explain how to build generative UI applications using the A2UI open standard and CopilotKit. A2UI describes interfaces with declarative JSON, and the client only renders components from a trusted component catalog; the same response can be rendered to React, Angular, SwiftUI, Jetpack Compose, and Flutter. The article provides a code example for integrating CopilotKit with Google ADK, and explains the bidirectional flow, implemented via the AG-UI protocol, in which user actions are sent back and the agent regenerates the interface.

    The Google A2UI team and CopilotKit CEO Atai Barkai explain how to build generative UI applications using the A2UI open standard and CopilotKit. A2UI describes interfaces with declarative JSON, and the client only renders components from a trusted component catalog; the same response can be rendered to React, Angular, SwiftUI, Jetpack Compose, and Flutter. The article provides a code example for integrating CopilotKit with Google ADK, and explains the bidirectional flow, implemented via the AG-U

    Matched fieldsBody

Wednesday

  1. Unite.AI

    Perplexity Publishes LLM Gateway Best Practices Guide, Outlining Request Flow and Production Risks

    On October 27, 2026, Perplexity published an LLM gateway best practices guide explaining how this middleware layer routes, authenticates, caches, and logs model calls, and distinguishing four categories: API gateways, LLM gateways, MCP gateways, and AI gateways. The guide breaks down the mechanism through a six-step request lifecycle, while warning that the gateway centralizes credentials from various providers, and cites the LiteLLM gateway breach disclosed by Microsoft and two high-severity vulnerabilities, CVE-2026-35029 and CVE-2026-59823, reported by Check Point (already fixed in LiteLLM 1.83.9). The article also lists postmortems of Cloudflare AI Gateway and OpenRouter outages, four deployment paths, and paid plans starting at about $50 per month.

    On October 27, 2026, Perplexity published an LLM gateway best practices guide explaining how this middleware layer routes, authenticates, caches, and logs model calls, and distinguishing four categories: API gateways, LLM gateways, MCP gateways, and AI gateways. The guide breaks down the mechanism through a six-step request lifecycle, while warning that the gateway centralizes credentials from various providers, and cites the LiteLLM gateway breach disclosed by Microsoft and two high-severity vu

    Matched fieldsBody