AllyshipContent Radar

News 2903

Chủ đề cộng đồng đang thảo luận

Crawl live-1795122900000 · 04:15 20 thg 11, 2026 · Xuất bản 04:31 20 thg 11, 2026

107 / 2903 chủ đề đạt ngưỡng 55 trong khoảng này.

21

Open models are moving into real enterprise workloads. Our cofounder and CEO @jmorgan’s conversations with CIOs and eng leaders at these companies have changed: from “where should I run my model” to “

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Ollama 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Open models are moving into real enterprise workloads. Our cofounder and CEO @jmorgan’s conversations with CIOs and eng leaders at these companies have changed: from “where should I run my model” to “where is my data going?” Read the piece in @FortuneMagazine: https://fortune.com/2026/11/19/ollama-ceo-open-models-ai-security-enterprise-data-jeffrey-morgan/

22

From learning to leaderboard: How Cisco upskilled 1,200 engineers in agentic AI with AWS AI League

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Rakesh Vangari 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Cisco, like many large engineering organizations, is adopting generative and agentic AI to change how its engineers build software. The hard part is no longer access to the technology. It’s helping thousands of engineers move from watching a demo to confidently building with it. Recorded sessions and slide decks rarely close that gap. Engineers learn fastest when they build something real, see it fail, fix it, and try again.</p> <p>AWS designed <a href="https://aws.amazon.com/ai/aileague/" target="_blank" rel="noopener">AWS AI League</a> for exactly that. It turns hands-on AI learning into a gamified competition, where participants customize models and build agents on AWS, get instant feedback on a live leaderboard, and compete in a game-show-style finale.</p> <p>Cisco is one of the clearest examples of what this looks like at scale. In 2025, Hemanth V, a Cisco software engineer, went from an internal Cisco event to being crowned the first AWS AI League Champion at AWS re:Invent 2025. In 2026, 1,200 Cisco engineers competed in an AWS AI League tournament at Cisco Transformation Fest 4.0. The winner, Nishanth Aluhonnu, earned a full event pass to AWS re:Invent 2026 in Las Vegas.</p> <p>In this post, we share how Cisco and AWS used Cisco Transformation Fest and AWS AI League to build a lasting culture of learning by doing. We previously covered this program in <a href="https://aws.amazon.com/blogs/machine-learning/from-theory-to-delivery-how-atos-upskilled-400-engineers-in-agentic-ai/" target="_blank" rel="noopener">From theory to delivery: How Atos upskilled 400 engineers in agentic AI</a>, and here we look at Cisco’s experience. We walk through Cisco’s journey, share technical lessons from the 2026 winning agent, and explain how your organization can host its own AWS AI League.</p> <h1>What is AWS AI League?</h1> <p>AWS AI League helps organizations build advanced AI skills through competition. Each league follows three steps:</p> <ol type="1"> <li><strong>Learn –</strong>&nbsp;A hands-on, 2-hour workshop led by AWS experts introduces the tools and the challenge.</li> <li><strong>Build –</strong>&nbsp;Participants experiment at their own pace and submit to a live leaderboard, with an automated evaluator giving real-time feedback after each submission.</li> <li><strong>Compete –</strong>&nbsp;Top finalists take the stage in a live, game-show-style grand finale.</li> </ol> <p>Although AWS AI League offers multiple use cases, at Cisco it offered the following two challenges:</p> <ul> <li><strong>Agentic AI challenge –</strong>&nbsp;Participants build agents with <a href="https://aws.amazon.com/bedrock/agentcore/" target="_blank" rel="noopener">Amazon Bedrock AgentCore</a>, a platform to build, connect, and optimize agents at scale with any framework or model. The agents move through a maze-like grid, solving challenges on the way to a treasure chest. The challenges map to real-world tasks such as handling inappropriate content, running code, retrieving information from the web, and extracting structured data. Builders can choose models for supervisor and sub-agents and add tools such as <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory.html" target="_blank" rel="noopener">AgentCore memory, a capability of Amazon Bedrock AgentCore</a>, and <a href="https://aws.amazon.com/lambda/lambda-functions/" target="_blank" rel="noopener">AWS Lambda Event Functions</a>. Builders use <a href="https://aws.amazon.com/bedrock/guardrails/" target="_blank" rel="noopener">Amazon Bedrock Guardrails</a> to apply safety controls to their agents.</li> <li><strong>Model customization challenge –</strong>&nbsp;Participants fine-tune models in <a href="https://aws.amazon.com/sagemaker/ai/studio/" target="_blank" rel="noopener">Amazon SageMaker Studio</a> using the latest training recipes. The challenge awards points when an automated evaluator rates a participant’s customized model as more accurate and comprehensive than a reference model on the specific tasks in the competition.</li> </ul> <p>Finalists are scored on time efficiency, accuracy, agent planning, and token consumption efficiency.</p> <div style="width: 810px" class="wp-caption alignnone"> <a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/03/ML-22161-1.png" target="_blank" rel="noopener"><img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/03/ML-22161-1.png" alt="AWS AI League champion on stage at AWS re:Invent 2025" width="800"></a> <p class="wp-caption-text">Figure 1: AWS AI League champion at AWS re:Invent 2025</p> </div> <div style="width: 810px" class="wp-caption alignnone"> <a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/03/ML-22161-2.png" target="_blank" rel="noopener"><img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/03/ML-22161-2.png" alt="2026 AWS AI League winner at the Cisco campus" width="800"></a> <p class="wp-caption-text">Figure 2: 2026 AWS AI League winner at Cisco campus</p> </div> <h1>The Cisco and AWS partnership</h1> <p>The AWS AI League story at Cisco grows out of a deep engineering partnership. Cisco and AWS bring together networking, cloud, security, and observability for shared customers, and many Cisco business units have chosen to build their next-generation applications natively on AWS. These include:</p> <ul> <li><strong>Cisco SD-WAN</strong>, whose controller architecture runs on AWS and serves customers globally as a software as a service (SaaS) application.</li> <li><strong>Cisco Meraki</strong>, <strong>Cisco Spaces</strong>, and Cisco’s IoT and smart buildings group.</li> <li><strong>Cisco Cloud Control</strong>, a cloud-native, AI-powered application integrated with AWS services that brings together security, networking, observability, and collaboration.</li> <li><strong>Cisco AI Defense</strong>, where Cisco

23

LangChain Raises $300M Series C at $3B Valuation

80

3 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

langchain, hwchase17 và 1 nguồn khác 1 bài viết · LangChain Blog, X
Biên tập tiếng Việt
Chi tiết nguồn

LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.

LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.

  • LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.
  • LangChain raises $300M Series C at a $3B valuation, led by CapitalG
  • to help every company own its intelligence with LangSmith, the agent engineering platform.
24

Keep inference running through regional capacity shortfalls with cross-Region inference routing in Amazon SageMaker AI

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Dmitry Soldatkin 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Serving a model from more than one AWS Region is a well-established pattern for highly available inference: when one Region runs short of GPU capacity, requests move to another. The pattern is simple to describe and hard to operate. Until now, if you served models on Amazon SageMaker AI managed endpoints, cross-Region routing was a piece you still had to build yourself.</p> <p>Today, we’re introducing cross-Region inference routing in Amazon SageMaker AI. It uses a new resource, the inference router, that gives your application one invocation path across the endpoints and inference components you already run, in one or more AWS Regions and AWS accounts. You register the destinations that serve a model, and your application invokes the router instead of a specific endpoint. The router keeps requests in its own Region while the local destination is healthy, shifts new requests to another registered destination when it isn’t, and returns traffic gradually after recovery.</p> <p>In this post, we explain how cross-Region inference routing decides where each request runs, walk through an example with one model in two Regions, and cover monitoring, limits, and what you pay. For a cross-account deployment that serves several models, see <a href="https://aws.amazon.com/blogs/machine-learning/how-salesforce-is-advancing-global-scale-model-serving-with-cross-region-inference-routing-in-amazon-sagemaker-ai/">How Salesforce is advancing global-scale model serving with cross-Region inference routing in Amazon SageMaker AI</a>.</p> <h2 id="when-one-region-runs-short-of-capacity">When one Region runs short of capacity</h2> <p>A SageMaker AI endpoint runs in one AWS Region and one account. When autoscaling can’t add instances of the type your endpoint needs, requests throttle and time out, even when the same model has spare capacity in another Region. To use that capacity, your application must detect a struggling endpoint and switch Regions, decide which errors are safe to retry without running the model twice, move traffic back after recovery without flapping, and manage access to endpoints in other accounts. That code sits on the critical path of every request, and every team serving models across Regions maintains its own version of it.</p> <h2 id="how-cross-region-inference-routing-works">How cross-Region inference routing works</h2> <p>Cross-Region inference routing is based on a few core ideas:</p> <ul> <li><strong>You decide where your model might run –</strong> For each model, you choose which endpoints and inference components the router might use.</li> <li><strong>SageMaker AI decides which destination serves each request –</strong>&nbsp;The router prefers its own Region and shifts new requests to another destination only when the local one can’t serve reliably.</li> <li><strong>Your endpoints stay the same –</strong>&nbsp;You deploy endpoints as you do today, with the same models, configurations, instance pools, and autoscaling. Direct <code>InvokeEndpoint</code> calls keep working, and the router passes <code>InferenceId</code> and <code>CustomAttributes</code> through, as <code>InvokeEndpoint</code> does.</li> <li><strong>You can see every decision –</strong>&nbsp;Each real-time response tells you which destination served the request and why.</li> </ul> <p>A few terms describe the pieces:</p> <ul> <li><strong>Inference router</strong> – A Regional SageMaker AI resource in your account that your application invokes.</li> <li><strong>Routing target</strong> – A name for one logical model on a router, such as <code>fraud-model</code>. A router can hold many routing targets, and each fails over independently of the others.</li> <li><strong>Destination</strong> – A real-time endpoint, inference component, or asynchronous endpoint registered under a routing target, identified by its full Amazon Resource Name (ARN), which tells the router its Region and account. A routing target holds either real-time destinations, which can mix endpoints and inference components across Regions and accounts, or asynchronous endpoints only.</li> <li><strong>Local destination</strong> – A destination in the router’s Region, preferred while it’s healthy.</li> <li><strong>Routing reason</strong> – A value returned with each real-time response that explains where the request went and why.</li> </ul> <p>The Region you create the router in is its local Region. To prefer a different Region, create a router there. The router doesn’t create capacity, scale your endpoints, deploy models, or copy model artifacts and container images. Each destination must already be running in its Region.</p> <div style="width: 810px" class="wp-caption alignnone"> <a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/17/ML-22377-1-1.png" target="_blank" rel="noopener"><img src="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a0b1b99f41ad8b103eff4b59/2026/11/17/ML-22377-1-1.png" alt="Inference router architecture: a client invokes a router in Region A, which sends requests to a local destination and falls back to destinations in Region B in the same account and in another account" width="800"></a> <p class="wp-caption-text">Figure 1: Each request goes to a healthy destination, with the router preferring destinations in its own Region</p> </div> <h3 id="how-routing-decisions-are-made">How routing decisions are made</h3> <p>The router considers only destinations that are registered on the routing target and that it’s authorized to invoke. Among those, it prefers destinations in its own Region, and when more than one local destination is healthy, it spreads requests across them evenly. Requests leave the Region only when local destinations can’t serve reliably. To detect that, SageMaker AI calculates a health score for each destination from its recent requests, measured in the destination’s own Region. Server errors (5xx), throttles, and timeouts lower the score. Errors from the SageMaker AI plat

25

Protect agent tool calls with Skyflow and Amazon Bedrock AgentCore Gateway

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Joe McCarron 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>In this post, we show how <a href="https://www.skyflow.com/" target="_blank" rel="noopener">Skyflow</a> and Amazon Bedrock <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway.html" target="_blank" rel="noopener">AgentCore Gateway</a> keep sensitive data out of the tools your AI agents call, and out of the model context those tools feed. We add Skyflow Detect to Amazon Bedrock AgentCore Gateway as a request and response <a href="https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-interceptors.html" target="_blank" rel="noopener">interceptor</a>. The Skyflow interceptor de-identifies data before it reaches a tool, restores it before the agent reads the result, and replaces documents with clean copies before the agent opens them. Your agents and tools don’t change.</p> <p>Skyflow is available in AWS Marketplace, and the interceptor is open source on GitHub.</p> <h2 id="agents-act-through-tools-and-tools-move-data">Agents act through tools, and tools move data</h2> <p>Agents have moved from answering questions to taking action, and they take action through tools: Model Context Protocol (MCP) servers, SaaS APIs, document stores, and web search. Every agent tool call is a data flow. Most enterprise controls cover what goes into and comes out of the model. Far fewer cover what an agent sends to its tools or what those tools send back.</p> <p>That gap shows up in three ways:</p> <ul> <li><strong>Sensitive data leaves through tool arguments.</strong> The model writes the arguments from everything in its context, including details the tool doesn’t need. Ask an agent about a customer, and the customer’s name, account number, or email goes straight into a query to a third-party server. That server sits outside your AWS account and your compliance scope.</li> <li><strong>Sensitive data comes back in tool results.</strong> Scraped web pages, CRM records, and case notes land in the model’s context, memory, traces, and logs. This happens even when the task never needed them.</li> <li><strong>Documents bypass text inspection.</strong> Document tools such as Amazon Simple Storage Service (Amazon S3), Box, and Google Drive return a signed URL, not text. A filter that inspects strings sees a link and lets it through, and the agent then opens the original file.</li> </ul> <p>Patching each agent doesn’t scale across teams and frameworks, and it can’t reach third-party tools. The controls need to sit where every tool call passes, so authorization, content safety, and data protection apply the same way to every agent and tool.</p> <p>AgentCore Gateway is that place. It fronts every tool an agent uses, whatever framework or model the agent runs on. It does more than route that traffic. With AgentCore Gateway interceptors, you can run your own code, as an AWS Lambda function, on every call that passes through it. A request interceptor sees each call before it reaches a tool, and a response interceptor sees each result before it reaches the agent. Either one can inspect the payload, rewrite it, or block the call. That makes the gateway a natural place to add data protection alongside Policy and Guardrails. This single control, attached once, covers every agent and every tool behind the gateway, without any change to agent or tool code.</p> <h3 id="example-a-dispute-resolution-agent-at-a-large-european-bank">Example: A dispute-resolution agent at a large European bank</h3> <p>Consider a large European bank with retail and corporate banking operations and strict data-residency obligations. Its operations teams are adopting agents to investigate card disputes.</p> <p>An analyst asks the agent to look into a disputed transaction. The agent searches the web for the merchant, then pulls the dispute case note from Amazon S3 to summarize it. Without protection, three things happen:</p> <ul> <li>The model builds the search query from everything in context. The search provider receives ‘Mateo Jackson dispute AnyCompany Electronics London’. That’s the customer’s name, sent to a third party, for a search that only needed the merchant.</li> <li>Scraped merchant pages bring unrelated personal data into the model’s context.</li> <li>The agent reads the original case note, with the customer’s full name, email, phone number, and card details.</li> </ul> <p>With the Skyflow interceptor on the gateway, the same workflow plays out differently:</p> <ul> <li>The search provider receives ‘[NAME_AJbrIud] dispute AnyCompany Electronics London’, where [NAME_AJbrIud] is a reversible vault token. The merchant results come back the same, the provider never learns who the customer is, and the analyst still sees the real name in the agent’s answer.</li> <li>Web content reaches the model already de-identified.</li> <li>The agent only ever receives a link to a de-identified copy of the case note.</li> </ul> <h2 id="solution-overview">Solution overview</h2> <p>The Skyflow interceptor is a single AWS Lambda function attached to both of the AgentCore Gateway interception points:</p> <ul> <li><code>REQUEST</code> runs before the gateway calls a tool.</li> <li><code>RESPONSE</code> runs after the tool answers and before the agent sees the result.</li> </ul> <p>At each point, it calls Skyflow Detect to find sensitive entities such as names, email addresses, phone numbers, government IDs, card numbers, dates of birth, and locations. It replaces them with tokens, or restores the originals. Skyflow Vault stores the original values so authorized systems can reverse the tokens.</p> <p>The Skyflow gateway configuration decides, for each tool, which of three protection modes applies: Shield the tool, Shield the model, and Shield the document.</p> <table border="1px" width="100%" cellpadding="10px"> <tbody> <tr> <td><strong>Mode</strong></td> <td><strong>What happens</strong></td> <td><strong>Who sees real data</strong></td> <td><strong>How it works</strong></td> <td><strong>Typical use</strong></td> </tr> <tr> <

26

LangSmith Tool Gateway: Secure, governed tool use for agents

63

1 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

langchain 1 bài viết · LangChain Blog, X
Nguyên văn nguồn
Chi tiết nguồn

LangSmith Tool Gateway, now in Public Beta, handles credentials, identity, and access for every agent tool call, with policies, approvals, and traces.

28

b12549

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

github-actions[bot] 1 bài viết · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>llama: fixes for Inkling 2 attention mask (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6428533227" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/32429" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/32429/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/32429">#32429</a>)</p> <ul> <li>llama : give Inkling2 its own relative-position attention input</li> </ul> <p>The Inkling2 graph built its flash attention mask from the hybrid iswa<br> input and passed it to build_attn through a new kq_mask argument. That<br> argument let a caller pair its own dense mask with the kv_rows of<br> llm_graph_input_attn_kv_iswa, whose mask follows the per-sequence cell<br> lists whenever kv_rows is enabled.</p> <p>Add llm_graph_input_attn_rel_pos instead. It owns dense KQ masks and the<br> query-to-cell distances, fills both from the same cells, and its<br> build_attn overload adds the per-head bias to its own mask and never<br> passes kv_rows. The iswa build_attn is back to its previous signature;<br> its body moves to build_attn_iswa_impl, which both overloads call.</p> <p>Inkling2 now folds the per-query sink into the bias with and without<br> flash attention, so build_attn_mha no longer needs the per-query sink<br> path.</p> <p>Assisted-By: Claude Opus 5.5 <a href="mailto:noreply@anthropic.com">noreply@anthropic.com</a></p> <ul> <li>inkling2 : make the expert weight scale and final logit softcap optional</li> </ul> <p>Load both keys as optional and skip them when they are zero, as other<br> models do, instead of rejecting zero at load.</p> <p>Assisted-By: Claude Opus 5.5 <a href="mailto:noreply@anthropic.com">noreply@anthropic.com</a></p> <ul> <li>llama : build kv_rows masks for the hybrid iswa memory</li> </ul> <p>llm_graph_input_mem_hybrid_iswa checked its masks with<br> can_reuse_attn_mask, which expects kv_rows whenever they are enabled,<br> but built them dense. With a unified cache and flash attention the<br> check always failed, and hybrid iswa models (LFM2, LFM3, Inkling2)<br> never reused a graph. Build the masks with build_attn_inp_attn_mask,<br> like the plain iswa input.</p> <p>Assisted-By: Claude Opus 5.5 <a href="mailto:noreply@anthropic.com">noreply@anthropic.com</a></p> <ul> <li>llama : make the relative-position input a hybrid iswa input</li> </ul> <p>Address review: llm_graph_input_mem_hybrid_iswa_rel derives from<br> llm_graph_input_mem_hybrid_iswa and owns the attention and recurrent<br> inputs, so Inkling2 builds one memory input instead of two. Its<br> attention input is built with dense masks, can_reuse checks them as<br> dense, and its build_attn asserts that the mask has no kv_rows (TODO:<br> a kv_rows variant). build_attn_iswa_impl is now a static helper.</p> <p>Assisted-By: Claude Opus 5.5 <a href="mailto:noreply@anthropic.com">noreply@anthropic.com</a></p> <ul> <li>llama : compose the hybrid iswa rel input, format inkling2</li> </ul> <p>Address review: llm_graph_input_mem_hybrid_iswa_rel owns its attention<br> and recurrent inputs like the other composite inputs instead of deriving<br> from llm_graph_input_mem_hybrid_iswa.</p> <p>Format src/models/inkling2.cpp like the other model sources: grouped<br> and aligned key and tensor loading, descriptive per-layer names, blank<br> lines and section comments between the steps, and cb() names for the<br> intermediate tensors. The graph is unchanged.</p> <p>Assisted-By: Claude Opus 5.5 <a href="mailto:noreply@anthropic.com">noreply@anthropic.com</a></p> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69772952">https://github.com/ggml-org/llama.cpp/attestations/69772952</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/23780/hovercard">DISABLED</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-macos-x64.tar.gz">macOS Intel (x64)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-xcframework.zip">iOS XCFramework</a></li> </ul> <p><strong>Linux:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-x64.tar.gz">Ubuntu x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-arm64.tar.gz">Ubuntu arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-s390x.tar.gz">Ubuntu 24.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-26.04-s390x.tar.gz">Ubuntu 26.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-zdnn-s390x.tar.gz">Ubuntu 26.04 s390x (zDNN)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-vulkan-x64.tar.gz">Ubuntu x64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-vulkan-arm64.tar.gz">Ubuntu arm64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/llama-b12549-bin-ubuntu-cuda-12.8-x64.tar.gz">Ubuntu x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12549/cudart-llama-b12549-bin-ubuntu-cuda-12.8-x64.tar.gz">CUDA 12.8 libraries</a>

  • b12549 ggml-org/llama.cpp releases · 20 thg 11, 2026
31

b12548

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

github-actions[bot] 1 bài viết · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>metal : fix the second argument of NSMakeRange (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6488409917" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/32602" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/32602/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/32602">#32602</a>)</p> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69767057">https://github.com/ggml-org/llama.cpp/attestations/69767057</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/23780/hovercard">DISABLED</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-macos-x64.tar.gz">macOS Intel (x64)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-xcframework.zip">iOS XCFramework</a></li> </ul> <p><strong>Linux:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-x64.tar.gz">Ubuntu x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-arm64.tar.gz">Ubuntu arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-s390x.tar.gz">Ubuntu 24.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-26.04-s390x.tar.gz">Ubuntu 26.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-zdnn-s390x.tar.gz">Ubuntu 26.04 s390x (zDNN)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-vulkan-x64.tar.gz">Ubuntu x64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-vulkan-arm64.tar.gz">Ubuntu arm64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-cuda-12.8-x64.tar.gz">Ubuntu x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/cudart-llama-b12548-bin-ubuntu-cuda-12.8-x64.tar.gz">CUDA 12.8 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-cuda-13.5-x64.tar.gz">Ubuntu x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/cudart-llama-b12548-bin-ubuntu-cuda-13.5-x64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-cuda-13.5-arm64.tar.gz">Ubuntu arm64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/cudart-llama-b12548-bin-ubuntu-cuda-13.5-arm64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-rocm-10.0-x64.tar.gz">Ubuntu x64 (ROCm 10.0)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-openvino-2026.4.1-x64.tar.gz">Ubuntu x64 (OpenVINO)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-sycl-fp32-x64.tar.gz">Ubuntu x64 (SYCL FP32)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-ubuntu-sycl-fp16-x64.tar.gz">Ubuntu x64 (SYCL FP16)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-linux-arm64-snapdragon.tar.gz">Linux arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/linux.md">setup guide</a></li> </ul> <p><strong>Android:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-android-arm64.tar.gz">Android arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-android-arm64-snapdragon.tar.gz">Android arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/README.md">setup guide</a></li> </ul> <p><strong>Windows:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-win-cpu-x64.zip">Windows x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-win-cpu-arm64.zip">Windows arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-win-opencl-adreno-arm64.zip">Windows arm64 (OpenCL Adreno)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-win-cuda-12.4-x64.zip">Windows x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/cudart-llama-bin-win-cuda-12.4-x64.zip">CUDA 12.4 DLLs</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-win-cuda-13.5-x64.zip">Windows x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/cudart-llama-bin-win-cuda-13.5-x64.zip">CUDA 13.5 DLLs</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12548/llama-b12548-bin-win-cuda-13.5-arm

  • b12548 ggml-org/llama.cpp releases · 20 thg 11, 2026
32

Read the process and how we're thinking about it here: https://www.llamaindex.ai/blog/building-toward-a-perfect-document-parsing-benchmark?utm_source=socials&utm_medium=tw_channel&utm_campaign=blogpos

64

2 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

LlamaIndex, jerryjliu0 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Read the process and how we're thinking about it here: https://www.llamaindex.ai/blog/building-toward-a-perfect-document-parsing-benchmark?utm_source=socials&utm_medium=tw_channel&utm_campaign=blogpost&utm_content=blogperfectbenchmark

33

Claude solves two open problems in the physics of black holes

88

2 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · 373 tương tác đã đo · Nguồn crawl

Handy-Man, cybermango 1 bài viết · HN: Claude, Anthropic Research (unofficial RSS mirror)
Nguyên văn nguồn
Chi tiết nguồn
34

PolyAI Dialog-RSN-1 is now on Amazon SageMaker JumpStart

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Helen Greul 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Dialog-RSN-1, a reasoning model built for real-time complex dialog, is available today on AWS Marketplace and Amazon SageMaker JumpStart. It powers frontier dialog: agents that hear a live call, reason about it, and act in real time.</p> <p>As an AWS customer, you can <a href="https://aws.amazon.com/marketplace/pp/prodview-l4qyhvfxnkq7e" target="_blank" rel="noopener">subscribe to Dialog-RSN-1 through AWS Marketplace</a> and deploy it as a SageMaker endpoint inside your own AWS environment. You can also deploy directly from Amazon SageMaker Studio following the steps in <a href="https://aws.amazon.com/blogs/machine-learning/deploy-and-evaluate-models-with-amazon-sagemaker-jumpstart/" target="_blank" rel="noopener">Deploy and evaluate models with Amazon SageMaker JumpStart</a>. That means the model designed to handle your customer conversations can be deployed like other Amazon SageMaker models with an AWS Marketplace subscription.</p> <h2 id="deploying-dialog-rsn-1-inside-aws">Deploying Dialog-RSN-1 inside AWS</h2> <p>Dialog-RSN-1 is the first PolyAI model available through <a href="https://aws.amazon.com/marketplace/pp/prodview-l4qyhvfxnkq7e" target="_blank" rel="noopener">AWS Marketplace</a>. It runs inside your own AWS environment on the same AWS cloud that powers PolyAI’s compute and model training and serving.</p> <p>All in a single pass, Dialog-RSN-1 perceives a caller’s audio directly, reasons about what they need, and responds in real time. On SageMaker, it deploys as an endpoint like other models you run there. It is reachable from your own architecture, billed through your AWS account, and covered by the same virtual private cloud (VPC), AWS Identity and Access Management (IAM) roles, and monitoring you already have in place.</p> <p>You keep ownership of orchestration, telephony integration, and business logic. Dialog-RSN-1 takes off your plate the hardest part to build yourself: understanding a live call and responding to it in real time. The endpoint speaks the OpenAI Realtime protocol, so an existing Realtime client connects through PolyAI’s <a href="https://github.com/polyai/dialog-rsn-1-sagemaker" target="_blank" rel="noopener">bridge</a> by changing its base URL. Audio in is 16-bit PCM mono at 16 or 24 kHz (transcode G.711 or Opus first). Connections last up to 30 minutes, and the model is English-only today.</p> <p>To get started, <a href="https://aws.amazon.com/marketplace/pp/prodview-l4qyhvfxnkq7e" target="_blank" rel="noopener">find Dialog-RSN-1 on AWS Marketplace</a>, then deploy it straight into an Amazon SageMaker endpoint in your own account. Or you can deploy directly from <a href="https://aws.amazon.com/sagemaker/ai/jumpstart/" target="_blank" rel="noopener">Amazon SageMaker JumpStart</a>.</p> <p>With Dialog-RSN-1 now onboarded to SageMaker JumpStart, deploying Dialog-RSN-1 takes one click. From the Amazon SageMaker AI console, open the Model Hub, select Dialog-RSN-1 from the JumpStart catalog, and choose Deploy. SageMaker JumpStart then spins up a real-time inference endpoint on a serving stack it has already tuned for you. No containers to wrangle, no instance types to second-guess, and no manual benchmarking. For automated workflows, the same one-click deployment also runs in a few lines of the SageMaker Python SDK.</p> <p>The Dialog-RSN-1 endpoint runs entirely within your own AWS account. It is deployed in your VPC, accessed through your IAM roles, and monitored with the same Amazon CloudWatch logging and metrics you use for every other workload. Because inference happens inside your account, your callers’ audio and transcripts stay within a boundary you control. For a model handling live customer conversation, this helps support your data residency and auditability requirements.</p> <h2 id="built-for-speed-and-accuracy">Built for speed and accuracy</h2> <p>Models built for live calls may make you choose between speed and understanding. And models built for speed may miss the meaning, and ones built for reasoning may lead to wait time for callers. Dialog-RSN-1 avoids the tradeoff.</p> <p>With PolyAI, you can build dialog agents that hear and handle calls the way your human agents would. These agents catch hesitation, hear frustration before it escalates, and know when to speak.</p> <p>Real-time customer conversation is the job PolyAI’s Dialog-RSN-1 is built for, and it is already handling live calls in production today. Because the model reasons directly over the caller’s audio, it picks up tone, hesitation, and timing, the signals a plain transcript loses, and decides for itself the right moment to respond.</p> <h2 id="a-model-that-hears-calls-the-way-humans-do">A model that hears calls the way humans do</h2> <p>Dialog-RSN-1 is a model focused on real-time conversations. There is no separate speech-to-text step and no reasoning model on the appropriate moment to talk, so thereby no multiple handoffs.</p> <p>In practice, that means the callers get responses faster:</p> <ul> <li>Barge-in keeps working even when call volume spikes, instead of getting switched off to protect performance.</li> <li>Responses keep pace, so the model is not lagging behind the conversation while it reasons through what to say.</li> <li>Transcription is produced from the audio itself, because Dialog-RSN-1 is reading the actual audio, not someone else’s best guess at it.</li> </ul> <h2 id="dialog-rsn-1-on-amazon-sagemaker-jumpstart">Dialog-RSN-1 on Amazon SageMaker JumpStart</h2> <p>Amazon SageMaker JumpStart is the machine learning hub inside Amazon SageMaker AI, and it exists to collapse the distance between choosing a model and running it in production. For Dialog-RSN-1, that means the frontier of real-time dialog is a few clicks away. You can discover it, prove it on your own data, and ship it to a secure endpoint, all in one place. Here is what you get.</p> <div style="width: 810px" class="wp-caption alignnone"> <a href="https://d2908q01vomqb2.cloudfront.net/f1f836cb4ea6efb2a

36

Read more in our launch blog, so excited to see where you all take this: https://blog.google/innovation-and-ai/technology/developers-tools/genie-4-in-gemini-api/

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

officiallogank 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Read more in our launch blog, so excited to see where you all take this: https://blog.google/innovation-and-ai/technology/developers-tools/genie-4-in-gemini-api/

37

Introducing Genie 4 in the Gemini API + @GoogleAIStudio, our first world model for developers to build with and create new world model experiences 🔮

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

officiallogank 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Introducing Genie 4 in the Gemini API + @GoogleAIStudio, our first world model for developers to build with and create new world model experiences 🔮 Try it out: https://ai.studio/genie

38

Today we are rolling out Genie 4 on the Gemini API and AI Studio🚀

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

_philschmid 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Today we are rolling out Genie 4 on the Gemini API and AI Studio🚀 Seed a 720p 24fps world from text or image and steer it live with WASD, prompts, and 48 kHz stereo audio. Stream via WebRTC (browser + ephemeral tokens) or WebSocket. Available on: - Gemini API: https://aistudio.google.com/docs/genie - AI Studio: https://aistudio.google.com/live?model=genie-4

39

b12547

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

github-actions[bot] 1 bài viết · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>webgpu: add POOL_2D support (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="6387361702" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/32250" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/32250/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/32250">#32250</a>)</p> <ul> <li> <p>Shader, pipeline, and launcher</p> </li> <li> <p>Update docs and add newline to wgsl</p> </li> <li> <p>Formatting fixes</p> </li> </ul> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69756852">https://github.com/ggml-org/llama.cpp/attestations/69756852</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/23780/hovercard">DISABLED</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-macos-x64.tar.gz">macOS Intel (x64)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-xcframework.zip">iOS XCFramework</a></li> </ul> <p><strong>Linux:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-x64.tar.gz">Ubuntu x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-arm64.tar.gz">Ubuntu arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-s390x.tar.gz">Ubuntu 24.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-26.04-s390x.tar.gz">Ubuntu 26.04 s390x (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-zdnn-s390x.tar.gz">Ubuntu 26.04 s390x (zDNN)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-vulkan-x64.tar.gz">Ubuntu x64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-vulkan-arm64.tar.gz">Ubuntu arm64 (Vulkan)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-cuda-12.8-x64.tar.gz">Ubuntu x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/cudart-llama-b12547-bin-ubuntu-cuda-12.8-x64.tar.gz">CUDA 12.8 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-cuda-13.5-x64.tar.gz">Ubuntu x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/cudart-llama-b12547-bin-ubuntu-cuda-13.5-x64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-cuda-13.5-arm64.tar.gz">Ubuntu arm64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/cudart-llama-b12547-bin-ubuntu-cuda-13.5-arm64.tar.gz">CUDA 13.5 libraries</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-rocm-10.0-x64.tar.gz">Ubuntu x64 (ROCm 10.0)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-openvino-2026.4.1-x64.tar.gz">Ubuntu x64 (OpenVINO)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-sycl-fp32-x64.tar.gz">Ubuntu x64 (SYCL FP32)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-ubuntu-sycl-fp16-x64.tar.gz">Ubuntu x64 (SYCL FP16)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-linux-arm64-snapdragon.tar.gz">Linux arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/linux.md">setup guide</a></li> </ul> <p><strong>Android:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-android-arm64.tar.gz">Android arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-android-arm64-snapdragon.tar.gz">Android arm64 (Snapdragon: CPU, Adreno GPU, Hexagon NPU)</a> - <a href="https://github.com/ggml-org/llama.cpp/blob/master/docs/backend/snapdragon/README.md">setup guide</a></li> </ul> <p><strong>Windows:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-win-cpu-x64.zip">Windows x64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-win-cpu-arm64.zip">Windows arm64 (CPU)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-win-opencl-adreno-arm64.zip">Windows arm64 (OpenCL Adreno)</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-win-cuda-12.4-x64.zip">Windows x64 (CUDA 12)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/cudart-llama-bin-win-cuda-12.4-x64.zip">CUDA 12.4 DLLs</a></li> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/llama-b12547-bin-win-cuda-13.5-x64.zip">Windows x64 (CUDA 13)</a> - <a href="https://github.com/ggml-org/llama.cpp/releases/download/b12547/cudart-llama-bin-win-cuda-13.5-x64.zip">CUDA

  • b12547 ggml-org/llama.cpp releases · 20 thg 11, 2026
40

Let's goooo! Super excited to announce our partnership with @Replit & @amasad for our Ramadan Global Buildathon!

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

arblauvelt 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Let's goooo! Super excited to announce our partnership with @Replit & @amasad for our Ramadan Global Buildathon! Limited to 1,000 teams - already past the 100 mark. Learn more & register today: http://Build.LaunchGood.com ps - would it be wrong to participate in my own Buildathon? I have an idea for a physical product 😅 Media

21–40 / 107
Trang 2 / 6