<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: SeaOtter ( Kentaro Mori )</title>
    <description>The latest articles on DEV Community by SeaOtter ( Kentaro Mori ) (@moruku36).</description>
    <link>https://dev.to/moruku36</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4165444%2F3289b767-50b2-46c5-9619-2ec3c048fb0c.png</url>
      <title>DEV Community: SeaOtter ( Kentaro Mori )</title>
      <link>https://dev.to/moruku36</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/moruku36"/>
    <language>en</language>
    <item>
      <title>The Differences Between Sakana Chat's Two Models, "Namazu" and "Fugu Max," and How to Choose</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Mon, 16 Nov 2026 00:26:08 +0000</pubDate>
      <link>https://dev.to/moruku36/the-differences-between-sakana-chats-two-models-namazu-and-fugu-max-and-how-to-choose-pk8</link>
      <guid>https://dev.to/moruku36/the-differences-between-sakana-chats-two-models-namazu-and-fugu-max-and-how-to-choose-pk8</guid>
      <description>&lt;p&gt;Key point: &lt;strong&gt;Namazu is a single model specialized for Japanese, while Fugu Max is an orchestrator that coordinates multiple models.&lt;/strong&gt; The memory feature is available on both.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;In the model selection menu of Sakana Chat, you'll see "Namazu" and "Fugu Max" listed side by side. The names alone don't make the difference obvious, so you may be unsure which one to pick.&lt;/p&gt;

&lt;p&gt;Sakana AI is developing a mobile app, and on November 9, 2026, it announced a call for beta testers on its official X account. In this article, we break down the differences between the two models available on the web version, based on publicly available information.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Main Features (Overview of the Two Models)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Namazu&lt;/strong&gt;: A single LLM specialized for Japanese and Japanese business practices. It is based on Moonshot AI's open model "Kimi K2.6" and has been further trained (post-trained) by Sakana AI on proprietary in-house data. It has been available since Sakana Chat launched in March 2026.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fugu Max&lt;/strong&gt;: An orchestrator model that coordinates multiple models. It is itself a language model, and it dynamically assembles agent configurations and processing steps based on the user's question, then executes them. From the API, it can be called like a single model.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The main updates to Sakana Chat since its public release are as follows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;March 2026: Launched alongside the alpha version of Namazu&lt;/li&gt;
&lt;li&gt;August 13, 2026: Fugu was added, making model selection possible. Code execution and image/document attachments were supported&lt;/li&gt;
&lt;li&gt;September 17, 2026: Fugu was overhauled into Fugu Max and made available to all users. The memory feature, usable with both Namazu and Fugu Max, was also added&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Namazu also became available via API on August 3, 2026. The API is OpenAI-compatible and includes web search and code execution as built-in tools by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. How It Works
&lt;/h2&gt;

&lt;h3&gt;
  
  
  3-1. Namazu's Post-Training
&lt;/h3&gt;

&lt;p&gt;Namazu has undergone additional training on proprietary in-house data on top of its base model. According to official information, the post-training covers the following:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Honorifics and business practices: Adapting to natural Japanese for document and email processing&lt;/li&gt;
&lt;li&gt;Reducing excessive refusals: Adjusting responses so the model doesn't decline too often&lt;/li&gt;
&lt;li&gt;Suppressing output bias: Adjusting to reduce bias toward the values of specific countries&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;According to Sakana AI's own evaluations, Namazu maintained the base model's reasoning ability (AIME26, MMLU-Pro, LiveCodeBench v6) while outperforming the base model on Japanese instruction following (JFBench), Japanese-English translation, and response neutrality. The FairPoliticsQA score for response neutrality reportedly rose from 34.10% to 56.30%.&lt;/p&gt;

&lt;p&gt;All of these are the company's own evaluations and claims, not independently verified by third parties. The translation and FairPoliticsQA figures are in-house benchmarks.&lt;/p&gt;

&lt;h3&gt;
  
  
  3-2. Fugu Max's Orchestration
&lt;/h3&gt;

&lt;p&gt;Rather than having humans define roles in advance, Fugu Max assembles specialist agents from a model pool according to the task and assigns the processing work. Models in the pool can be swapped out, and specific models can also be excluded.&lt;/p&gt;

&lt;p&gt;The technical foundations are the ICLR 2026 papers "TRINITY" and "Conductor." In TRINITY, an evolutionary lightweight coordinator assigns each model the role of Thinker, Worker, or Verifier. In Conductor, the natural-language coordination strategies themselves are learned through reinforcement learning.&lt;/p&gt;

&lt;p&gt;AB-MCTS (arXiv:2503.04412) is also relevant prior research. However, it has not been officially stated that it is used inside Fugu.&lt;/p&gt;

&lt;p&gt;The Fugu family consists of the following four models:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Fugu&lt;/strong&gt;: A balanced model for performance and speed&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fugu Ultra&lt;/strong&gt;: A model focused on performance&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fugu Max&lt;/strong&gt;: A model focused on cost performance, with the largest model pool&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fugu Cyber&lt;/strong&gt;: A model specialized for security&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The one you can select in Sakana Chat is Fugu Max.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Usage (Rough Guidelines for Choosing)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;When to choose Namazu&lt;/strong&gt;: Repeated workflows that produce natural Japanese outputs from Japanese instructions, such as processing documents and emails that require honorifics and knowledge of business practices. It is also suitable when response neutrality matters.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When to choose Fugu Max&lt;/strong&gt;: When you want to combine the strengths of multiple models, or when you want agents to be assembled according to the task.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The memory feature, which carries conversation context forward, is available on both Namazu and Fugu Max.&lt;/p&gt;

&lt;p&gt;API pricing is as follows (per 1 million tokens):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Model        Input          Output         Notes
Namazu       $0.95          $4.00          From December 1, 2026
                                           Input $1.90 / Output $6.00 scheduled
Fugu Max     $2             $6
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  5. Applications (Official Use Cases)
&lt;/h2&gt;

&lt;p&gt;Official use cases for Namazu include automated generation of market research reports and customer support automation. The intended use is repeated workflows that take in Japanese instructions and return natural Japanese outputs.&lt;/p&gt;

&lt;p&gt;Fugu Max is set up to distribute processing to models according to the task. A use case would be tackling problems that are hard for a single model by combining multiple models.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. How This Differs from the Past (Contrast with the Single Massive Model Approach)
&lt;/h2&gt;

&lt;p&gt;Sakana AI promotes three pillars: "pre-training, post-training, and orchestration." Namazu is positioned as the post-training product, and Fugu as the orchestration product.&lt;/p&gt;

&lt;p&gt;In the official FAQ, Fugu is described as a service that orchestrates multiple models, while Namazu is described as a single proprietary model that has been additionally trained in-house.&lt;/p&gt;

&lt;p&gt;This is a different approach from the path of pre-training a single massive model in-house. A difference in approach alone does not determine which is better in terms of performance.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Caveats
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Benchmarks&lt;/strong&gt;: All numbers are the company's own evaluations and claims, not verified by third parties. They do not establish superiority or inferiority over competing products.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Technical report&lt;/strong&gt;: The benchmarks in arXiv:2606.21228 are for Fugu and Fugu Ultra; they are not figures for Fugu Max.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Model pool&lt;/strong&gt;: The setup allows models to be swapped out. The official explanation is that this protects users from vendor lock-in, API discontinuation, and geopolitical uncertainty.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AB-MCTS&lt;/strong&gt;: It has not been officially stated that it is used inside Fugu.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mobile app&lt;/strong&gt;: It is in development, and a call for beta testers has been officially announced.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  8. Summary
&lt;/h2&gt;

&lt;p&gt;Namazu is a single model post-trained for Japanese and Japanese business practices. Fugu Max is an orchestrator that dynamically assembles multiple models.&lt;/p&gt;

&lt;p&gt;For Japanese document and email processing, Namazu is the choice; for problems that require coordination among multiple models, it's worth trying Fugu Max. The memory feature is available on both.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. The Author's Take
&lt;/h2&gt;

&lt;p&gt;Having used both models, Namazu felt designed for users who prioritize response speed. With Fugu Max, I got a strong sense of accuracy in answers to heavy tasks and complex consultations. This is purely the author's subjective experience.&lt;/p&gt;

&lt;p&gt;Going forward, I think the question will be how Sakana AI differentiates itself between cutting-edge models like ChatGPT and Claude and lightweight models coming out of China. Optimization for Japanese and the evolution of the mechanism for bundling models together look set to be key.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://sakana.ai/namazu/" rel="noopener noreferrer"&gt;https://sakana.ai/namazu/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sakana.ai/namazu-api/" rel="noopener noreferrer"&gt;https://sakana.ai/namazu-api/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sakana.ai/fugu/" rel="noopener noreferrer"&gt;https://sakana.ai/fugu/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sakana.ai/chat-update/" rel="noopener noreferrer"&gt;https://sakana.ai/chat-update/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://sakana.ai/chat-fugumax/" rel="noopener noreferrer"&gt;https://sakana.ai/chat-fugumax/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://arxiv.org/abs/2606.21228" rel="noopener noreferrer"&gt;https://arxiv.org/abs/2606.21228&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://arxiv.org/abs/2503.04412" rel="noopener noreferrer"&gt;https://arxiv.org/abs/2503.04412&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://chat.sakana.ai/" rel="noopener noreferrer"&gt;https://chat.sakana.ai/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>sakanaai</category>
      <category>llm</category>
      <category>ai</category>
      <category>japanese</category>
    </item>
    <item>
      <title>The Week Gemini 4 Carbon and Hydrogen Landed: Antigravity's Orchestrator and /swarm, Explained</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Sun, 15 Nov 2026 00:04:45 +0000</pubDate>
      <link>https://dev.to/moruku36/the-week-gemini-4-carbon-and-hydrogen-landed-antigravitys-orchestrator-and-swarm-explained-4125</link>
      <guid>https://dev.to/moruku36/the-week-gemini-4-carbon-and-hydrogen-landed-antigravitys-orchestrator-and-swarm-explained-4125</guid>
      <description>&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;When you hand heavy work to an AI agent, you keep running into the same trade-off: the smart models are slow and burn through your usage quota, while the fast models get stuck exactly where it matters.&lt;/p&gt;

&lt;p&gt;Between November 10 and 13, 2026, Google shipped its answer to that problem all at once: Gemini 4 Carbon, its strongest model; Gemini 4 Hydrogen, a fast new model; and two new features in its development environment Antigravity — /swarm and Orchestrator.&lt;/p&gt;

&lt;p&gt;Since Gemini 3.8 Flash arrived in September, Google's model lineup had felt like it was standing still. This week's releases refresh it completely. This article summarizes what changed and how the pieces work, based only on Google's official blog posts.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What was released
&lt;/h2&gt;

&lt;p&gt;The six main changes this week:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemini 4 Carbon&lt;/strong&gt; (November 10) — Google's strongest model, built for long-horizon agentic work, complex coding and debugging, and scientific reasoning. In subscriptions it is available only on Google AI Ultra; the API is open to paying developers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gemini 4 Hydrogen&lt;/strong&gt; (November 12) — The fast successor to Gemini 3.8 Flash, built for everyday coding and agent execution, with four thinking levels. In Google Search it is available to all users.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;/swarm&lt;/strong&gt; (November 10, preview) — An Antigravity feature that turns a single prompt into a coordinated team of agents whose progress you can track in real time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Orchestrator&lt;/strong&gt; (November 12) — A new option in Antigravity's model selector that dynamically switches between models within the same session. At launch it was for Ultra subscribers, pairing Carbon as the planner with Hydrogen for execution. On November 13 it also reached Pro subscribers, where it pairs Argon as the planner with Hydrogen. Orchestrator with Carbon remains Ultra-only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dynamic Workflows&lt;/strong&gt; (November 13, /run-workflow) — Lets the agent generate and run a short Python script that coordinates many agents, running phases in parallel with parallel() or in sequence with pipeline().&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smaller Antigravity updates&lt;/strong&gt; — A font size setting, split-view plugins, approval before the browser agent downloads a file, and a layout tailored to your kind of work. On November 11, Carbon also became selectable when signing in with Google Cloud credentials.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. How it works
&lt;/h2&gt;

&lt;p&gt;Both /swarm and Orchestrator are built on the same idea: don't make one model do everything.&lt;/p&gt;

&lt;p&gt;In /swarm, Carbon takes the roles that demand deep reasoning — architectural design, coordination, and auditing. Faster, lighter models act as workers and verifiers in parallel, each in an isolated workspace, and the verifiers test every change. According to Google, tens of thousands of swarms were launched in the first few days.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqebio8kxn7zs0vp05c3l.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqebio8kxn7zs0vp05c3l.jpg" alt="A /swarm session in Antigravity: agents with split roles analyzing a repository in parallel (author's screenshot)" width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Orchestrator divides roles inside a single session. Carbon starts in a read-only phase: it explores dependencies, resolves ambiguities, and builds a plan with explicit re-planning triggers. Hydrogen then takes over to write edits and run tests. If Hydrogen hits friction, it hands back to Carbon, which inspects the state, repairs the plan, and lets Hydrogen resume.&lt;/p&gt;

&lt;p&gt;Unlike a static router that picks one model up front, Orchestrator moves back and forth as the work evolves. In Google's measurements on Terminal-Bench, Orchestrator reached near-Carbon task success rates while consuming 24% less quota on average and finishing 19% faster.&lt;/p&gt;

&lt;p&gt;Orchestrator launched for Ultra subscribers, but on November 13 it also reached Pro subscribers: on Pro, Argon plans and Hydrogen executes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F01vfkj7sz2yvqdc1xi8d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F01vfkj7sz2yvqdc1xi8d.png" alt="How Orchestrator works" width="800" height="1262"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Dynamic Workflows (/run-workflow) also arrived the same week, on November 13. When you run /run-workflow, the agent writes a short Python script that coordinates many agents. The script runs after your approval, moving through phases in parallel with parallel() or in sequence with pipeline().&lt;/p&gt;

&lt;p&gt;Each agent works in its own conversation and returns a structured result matching a JSON Schema, so your main conversation's context stays clean. You can set a model and an isolated workspace per agent, and save the script to a file to run it again.&lt;/p&gt;

&lt;p&gt;Orchestrator plans and routes inside a single conversation. Dynamic Workflows, by contrast, controls the steps with a script — a predictable approach.&lt;/p&gt;

&lt;p&gt;/swarm has agents coordinating with each other on a shared message board. Dynamic Workflows fits work like applying the same check across a list of files or packages.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. My take
&lt;/h2&gt;

&lt;p&gt;The /swarm idea itself is not new. But with Gemini 3.8 Flash as the worker, the team felt underpowered — there was not much to gain from coordinating weak agents.&lt;/p&gt;

&lt;p&gt;That changes now that Hydrogen can do the execution while Carbon or Argon sits in the coordinator's seat. A fast, capable executor paired with a deep-thinking lead makes orchestration practical, and in my view it is a strong lineup against Anthropic and OpenAI.&lt;/p&gt;

&lt;p&gt;After months of standing still since 3.8 Flash in September, Google's models feel refreshed — and, for the first time in a while, on par with the competition.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Caveats
&lt;/h2&gt;

&lt;p&gt;The caveat is consumption. Running several models in parallel structurally costs more tokens and quota. Carbon itself is designed to use more tokens than Argon to explore thoroughly and run extended verification loops, as Google's blog notes.&lt;/p&gt;

&lt;p&gt;Orchestrator's 24% saving is a mechanism for keeping that cost down. Where you spend the frontier model, and which work you leave to the lighter one, will matter more in day-to-day development.&lt;/p&gt;

&lt;p&gt;Also note that /swarm is still a preview, and Carbon's API price is an introductory one that may change.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Summary
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;This week Google shipped Carbon and Hydrogen, completing the Gemini 4 lineup.&lt;/li&gt;
&lt;li&gt;Antigravity gained /swarm and Orchestrator, making multi-model setups — a coordinator plus executors — a standard option.&lt;/li&gt;
&lt;li&gt;The open problem is consumption: using each model where it counts takes deliberate design.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The same week also brought pre-orders for Gemini-powered intelligent eyewear. The collections, made with Gentle Monster, Warby Parker, and Samsung, go on sale December 10. Google also announced Guided Vision, a conversational audio description feature.&lt;/p&gt;

&lt;p&gt;The same week, on November 11, also brought the Gemini Decisions API, a decision-only endpoint powered by Gemini Decision 1 that generates no text. One multimodal input of up to 256K tokens can be scored against up to 1,000 yes/no, choice, or rubric-scoring questions in a single pass, returning probabilities and confidence scores. Latency is 150–250 ms end to end, pricing is $0.10 per 1M input tokens with no output tokens billed, and a free tier is available in AI Studio — built for tool selection, policy checks, and model routing, where only the decision is needed.&lt;/p&gt;

&lt;p&gt;Also on November 10, DeepMind announced Gemini Robotics 2.5, its most capable vision-language-action model, evaluated across more than 200 tasks. In a real-world proof of concept, Apptronik's Apollo 2 humanoid performed automotive kitting on active Mercedes-Benz production lines in Kecskemét, Hungary, and Sindelfingen, Germany, with a 96% success rate (a proof-of-concept figure from Google). Development was accelerated using Gemini 4 Argon, and the model is now rolling out to robotics partners.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Google, "Gemini 4 Carbon is now available" &lt;a href="https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-4-carbon-now-available/" rel="noopener noreferrer"&gt;https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-4-carbon-now-available/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google, "Introducing Gemini 4 Hydrogen for Agentic Workflows" &lt;a href="https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-hydrogen/" rel="noopener noreferrer"&gt;https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-hydrogen/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Antigravity Blog, "Gemini 4 Hydrogen and Orchestrator" &lt;a href="https://antigravity.google/blog/gemini-4-hydrogen-in-google-antigravity" rel="noopener noreferrer"&gt;https://antigravity.google/blog/gemini-4-hydrogen-in-google-antigravity&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Antigravity Changelog &lt;a href="https://antigravity.google/docs/changelog" rel="noopener noreferrer"&gt;https://antigravity.google/docs/changelog&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Antigravity, "Choose a model" &lt;a href="https://antigravity.google/docs/models#orchestrator" rel="noopener noreferrer"&gt;https://antigravity.google/docs/models#orchestrator&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Antigravity, "Dynamic Workflows (/run-workflow)" &lt;a href="https://antigravity.google/docs/dynamic-workflows" rel="noopener noreferrer"&gt;https://antigravity.google/docs/dynamic-workflows&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google, "Intelligent eyewear collections with Gemini features" &lt;a href="https://blog.google/innovation-and-ai/technology/xr-ar/google-intelligent-eyewear-collections-pre-order/" rel="noopener noreferrer"&gt;https://blog.google/innovation-and-ai/technology/xr-ar/google-intelligent-eyewear-collections-pre-order/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google, "Gemini Decisions API: Fast multimodal decisions" &lt;a href="https://blog.google/innovation-and-ai/technology/developers-tools/gemini-decisions-api/" rel="noopener noreferrer"&gt;https://blog.google/innovation-and-ai/technology/developers-tools/gemini-decisions-api/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google DeepMind, "Gemini Robotics 2.5: Accelerating Physical Intelligence" &lt;a href="https://deepmind.google/blog/gemini-robotics-2-5-accelerates-real-world-physical-intelligence/" rel="noopener noreferrer"&gt;https://deepmind.google/blog/gemini-robotics-2-5-accelerates-real-world-physical-intelligence/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Why Rust Is Getting Attention Now: From the Language's History, Its Relationship with Python, and AI Infrastructure Case Studies</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Sat, 14 Nov 2026 00:11:09 +0000</pubDate>
      <link>https://dev.to/moruku36/why-rust-is-getting-attention-now-from-the-languages-history-its-relationship-with-python-and-38id</link>
      <guid>https://dev.to/moruku36/why-rust-is-getting-attention-now-from-the-languages-history-its-relationship-with-python-and-38id</guid>
      <description>&lt;p&gt;Survey date: November 11, 2026&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;When you hear Rust, you might think of it as a replacement for C or C++. In fact, it is used in areas such as operating systems and browsers, where speed and fine-grained resource management are required.&lt;/p&gt;

&lt;p&gt;However, Rust's recent role goes beyond that. There are also examples of replacing parts of services built in Python with Rust, building the internals of components used from Python in Rust, and newly building the foundation for running AI agents in Rust.&lt;/p&gt;

&lt;p&gt;In this report, we trace the history and features of Rust to explain why it is attracting attention. We also cover a case study introduced by Anthropic of migrating a Python-based service to Rust, as well as NVIDIA OpenShell.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Conclusion: A Language That Aims to Achieve Both Performance and Safety
&lt;/h2&gt;

&lt;p&gt;Rust is &lt;strong&gt;a programming language that values high execution performance and fine-grained control over memory, while aiming to prevent many problems caused by memory handling before the program runs&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It is particularly valued for the following combination:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It offers fine-grained control close to that of C and C++.&lt;/li&gt;
&lt;li&gt;Its ownership system allows unsafe memory usage to be checked at compile time.&lt;/li&gt;
&lt;li&gt;Because garbage collection is not mandatory, latency and resource usage can be easier to predict in some cases.&lt;/li&gt;
&lt;li&gt;Development tools such as Cargo are well established.&lt;/li&gt;
&lt;li&gt;It can be combined with existing Python and C/C++ systems.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;However, using Rust does not guarantee that code will always become faster or that bugs will disappear. Since learning it and migrating to it take effort, it needs to be chosen according to the use case.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. History of Rust: From a Personal Experiment to Shared Infrastructure
&lt;/h2&gt;

&lt;h3&gt;
  
  
  2006: Started as a Personal Project
&lt;/h3&gt;

&lt;p&gt;Rust began in 2006 as Graydon Hoare's personal project. It was created with the goal of building a systems programming language that could achieve both safety and performance.&lt;/p&gt;

&lt;h3&gt;
  
  
  2009–2010: Mozilla Support and Public Release
&lt;/h3&gt;

&lt;p&gt;In 2009, Mozilla began funding the work, and by the end of the year it had become an in-house project. After that, development proceeded openly as a project of Mozilla Research.&lt;/p&gt;

&lt;p&gt;Some sources say it "started in 2010." This difference comes from whether the starting point is taken to be the beginning of personal development or the project's adoption and public release at Mozilla.&lt;/p&gt;

&lt;h3&gt;
  
  
  2012 Onward: Refining Practicality Through Servo
&lt;/h3&gt;

&lt;p&gt;Mozilla supported Servo, a browser engine written in Rust. A browser is large-scale software where performance, concurrency, and safety all matter. Rust was developed and refined while building real systems like this.&lt;/p&gt;

&lt;h3&gt;
  
  
  2015: Rust 1.0
&lt;/h3&gt;

&lt;p&gt;Rust 1.0 was released in May 2015. As a stable release, it valued compatibility and marked a major milestone toward making it easier to build practical software for the long term.&lt;/p&gt;

&lt;h3&gt;
  
  
  2021: Establishment of the Rust Foundation
&lt;/h3&gt;

&lt;p&gt;The Rust Foundation was established, creating a system in which multiple companies and the community support the language and related infrastructure. It has grown as shared infrastructure supported by everyone, rather than relying on Mozilla alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  2025: Stabilization of the Rust 2024 Edition
&lt;/h3&gt;

&lt;p&gt;The Rust 2024 Edition has "2024" in its name, but it was released as stable in 2025. Editions are a mechanism for evolving the language while helping existing code keep working. Libraries using different editions can be combined.&lt;/p&gt;

&lt;p&gt;Viewed historically, Rust was not born from a single new idea alone; rather, it is a project that has incorporated the results of past languages and research and has been nurtured by many people as practical, shared infrastructure.&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://github.com/graydon/rust-prehistory" rel="noopener noreferrer"&gt;Prehistory of Rust&lt;/a&gt; / &lt;a href="https://rustfoundation.org/media/10-years-of-stable-rust-an-infrastructure-story/" rel="noopener noreferrer"&gt;10th Anniversary Retrospective by the Founder&lt;/a&gt; / &lt;a href="https://blog.rust-lang.org/2015/05/15/Rust-1.0/" rel="noopener noreferrer"&gt;Rust 1.0 Announcement&lt;/a&gt; / &lt;a href="https://blog.rust-lang.org/releases/1.85.0/" rel="noopener noreferrer"&gt;Rust 2024&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. What Kind of Language Is Rust?
&lt;/h2&gt;

&lt;p&gt;Rust is a general-purpose language that checks types before execution and compiles programs to machine code for execution. It can be used not only for low-level development such as OSs, but also for web services, CLIs, data processing, and supporting infrastructure around AI.&lt;/p&gt;

&lt;p&gt;The design of the language reflects the influence of various earlier languages.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;C++&lt;/strong&gt;: The idea of managing resources such as memory and files in fine detail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ML / OCaml family&lt;/strong&gt;: Type-driven ways of writing code, such as type inference and pattern matching.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Haskell&lt;/strong&gt;: The approach of tying shared behavior to types.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory management research&lt;/strong&gt;: The idea of checking reference safety in advance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In short, it is &lt;strong&gt;a language that combines C++-like resource management with the expressive power of functional languages through types&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://doc.rust-lang.org/reference/influences.html" rel="noopener noreferrer"&gt;Rust Reference: Influences&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  5. "Ownership" at the Heart of Rust
&lt;/h2&gt;

&lt;p&gt;Rust's defining features are ownership, borrowing, and lifetimes.&lt;/p&gt;

&lt;p&gt;In languages like C and C++ that allow fine-grained control over memory, problems can occur such as using memory that has already been freed, or freeing the same memory twice. Such problems can sometimes lead to vulnerabilities.&lt;/p&gt;

&lt;p&gt;In Rust, the responsibility for managing data is handled as "ownership." When other processes temporarily use data, they "borrow" it. The compiler checks things like whether those references outlive the original data.&lt;/p&gt;

&lt;p&gt;As an analogy, it is a mechanism for verifying, before running the program, who the "owner" of the data is and who is borrowing it until when.&lt;/p&gt;

&lt;p&gt;However, it is not a silver bullet. Logic bugs, deadlocks, and memory leaks can still occur. Also, if there are problems in &lt;code&gt;unsafe&lt;/code&gt; code or at the boundary with other languages, code using safe Rust can still be affected.&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://doc.rust-lang.org/book/ch04-01-what-is-ownership.html" rel="noopener noreferrer"&gt;Rust Official Book: Ownership&lt;/a&gt; / &lt;a href="https://doc.rust-lang.org/book/ch20-01-unsafe-rust.html" rel="noopener noreferrer"&gt;Unsafe Rust&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Why Rust Tends to Be Lightweight and Fast
&lt;/h2&gt;

&lt;p&gt;There is no single reason why Rust is fast.&lt;/p&gt;

&lt;h3&gt;
  
  
  More Can Be Decided Before Execution
&lt;/h3&gt;

&lt;p&gt;Based on information such as types and call targets, the compiler can optimize the code into native machine code.&lt;/p&gt;

&lt;h3&gt;
  
  
  Memory Usage Is Easy to Tune
&lt;/h3&gt;

&lt;p&gt;You can design your code with awareness of where data is placed, copying, and memory allocation. Reducing unnecessary allocations and copies can lead to improvements in speed and memory usage.&lt;/p&gt;

&lt;h3&gt;
  
  
  No Mandatory Garbage Collection
&lt;/h3&gt;

&lt;p&gt;Garbage collection (GC) is a mechanism that finds and reclaims memory that is no longer needed while the program is running. Rust does not require it, and instead manages resources using ownership and related mechanisms.&lt;/p&gt;

&lt;p&gt;Because of this, depending on the application, it can be easier to avoid delays caused by collection pauses and to estimate resource usage. On the other hand, languages that use GC have the advantage of being easier to develop in — neither is always superior.&lt;/p&gt;

&lt;h3&gt;
  
  
  Easier to Achieve Both Convenience and Speed
&lt;/h3&gt;

&lt;p&gt;Rust provides features such as iterators and generics that improve readability and reusability. Because the compiler can turn these into efficient code, it is easier to achieve both "writing conveniently" and "running fast."&lt;/p&gt;

&lt;p&gt;However, operations such as bounds checks, memory allocation, and locks do incur costs. &lt;strong&gt;Simply rewriting code in Rust does not guarantee that it will always become faster, nor is there any guarantee that it will always be faster than C++.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://doc.rust-lang.org/book/ch13-04-performance.html" rel="noopener noreferrer"&gt;Rust Official: Iterators and Performance&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Why It Has Come to Be Used So Widely
&lt;/h2&gt;

&lt;p&gt;If performance were the only consideration, C and C++ are also excellent. Rust is attracting attention because, in addition to performance, it is also expected to offer safety and maintainability.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In infrastructure that handles input over networks, memory safety is helpful.&lt;/li&gt;
&lt;li&gt;Concurrent processing can be built while keeping memory usage and latency under control.&lt;/li&gt;
&lt;li&gt;Builds, dependencies, and tests can be handled in a relatively unified way with Cargo.&lt;/li&gt;
&lt;li&gt;It can be introduced into only part of an existing system.&lt;/li&gt;
&lt;li&gt;Large-scale adoption cases are increasing, building up material to inform adoption decisions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In particular, it can be said to be a good fit for areas where both performance and reliability are required, such as operating systems, browsers, networking, cloud infrastructure, and AI agent runtime environments.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. What Replacing Python with Rust Means
&lt;/h2&gt;

&lt;p&gt;"Replacing Python with Rust" actually takes several forms.&lt;/p&gt;

&lt;h3&gt;
  
  
  ① Porting the Service Itself to Rust
&lt;/h3&gt;

&lt;p&gt;This is the approach of rewriting all or a major part of a service written in Python in Rust. It can be a candidate when startup time, memory consumption, latency, and similar issues are a concern.&lt;/p&gt;

&lt;p&gt;However, porting involves development, validation, and maintenance costs. Performance improvements are not necessarily caused by the language alone; in some cases, changes to algorithms or architecture contribute to the improvement.&lt;/p&gt;

&lt;h3&gt;
  
  
  ② Keeping Python as the Interface and Using Rust for Only Part of the Internals
&lt;/h3&gt;

&lt;p&gt;This is the approach of maintaining Python's ease of writing and existing code while implementing performance-intensive parts in Rust.&lt;/p&gt;

&lt;p&gt;For example, &lt;a href="https://pydantic.dev/articles/pydantic-v2" rel="noopener noreferrer"&gt;Pydantic v2&lt;/a&gt; keeps the same usage from Python while using Rust for the core data-validation logic.&lt;/p&gt;

&lt;h3&gt;
  
  
  ③ Building Python Development Tools in Rust
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://docs.astral.sh/uv/" rel="noopener noreferrer"&gt;uv&lt;/a&gt; is a Rust-built tool for Python package management and related tasks. This is an example not of eliminating Python, but of building tools that support Python development in Rust.&lt;/p&gt;

&lt;p&gt;In other words, Rust and Python are not in a simple competitive relationship. A combination is possible: &lt;strong&gt;develop quickly in Python, and use Rust where performance and safety matter&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Note that in AI GPU computation, even when called from Python, native code such as CUDA is often running internally. Therefore, simply changing the caller to Rust does not automatically make GPU matrix operations faster.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Anthropic's Python-to-Rust Porting Case
&lt;/h2&gt;

&lt;p&gt;Anthropic noted in its &lt;a href="https://www.anthropic.com/claude-fable-and-mythos-5-2" rel="noopener noreferrer"&gt;Announcement of Claude Fable 5.2 / Mythos 5.2&lt;/a&gt; on November 9, 2026, that an agent team using an early version of Fable 5.2 had ported an important production service from Python to Rust.&lt;/p&gt;

&lt;p&gt;According to the company, efficiency and reliability improved after the port, and &lt;strong&gt;startup became about 26x faster&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;For this case, the following distinctions are important.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The target was an "important production service." It is not stated that the AI model itself was rewritten.&lt;/li&gt;
&lt;li&gt;The figure of about 26x is the company's announcement about &lt;strong&gt;startup&lt;/strong&gt;. It does not mean that inference speed or overall system throughput became 26x faster.&lt;/li&gt;
&lt;li&gt;The name of the target service, absolute times, and details of the measurement conditions are not shown in the relevant passage.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Even so, this report is an interesting case suggesting that porting to Rust can be an option for operational challenges in services built with Python.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Representative Adoption Cases
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Azure Boost
&lt;/h3&gt;

&lt;p&gt;Microsoft's &lt;a href="https://learn.microsoft.com/en-us/azure/azure-boost/overview" rel="noopener noreferrer"&gt;Azure Boost&lt;/a&gt; is a mechanism for offloading processing such as networking and storage associated with virtualization to dedicated hardware. Microsoft explains its policy of using Rust as the primary language for new Azure Boost code.&lt;/p&gt;

&lt;p&gt;However, this does not mean that all of Azure was replaced from C with Rust. Nor can the performance improvements in Azure Boost be attributed to Rust alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  Discord
&lt;/h3&gt;

&lt;p&gt;Discord has published a case of migrating a service handling read states from Go to Rust. The aim was to reduce GC-related latency spikes that occurred under specific load conditions.&lt;/p&gt;

&lt;p&gt;This is an example where Rust may be chosen depending on the required latency and resource characteristics, not only for services written in C/C++ but also for services written in Go. On the other hand, this is not a general claim that Go is always slow.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://discord.com/blog/why-discord-is-switching-from-go-to-rust" rel="noopener noreferrer"&gt;Discord Official: Why Discord is switching from Go to Rust&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Linux Kernel
&lt;/h3&gt;

&lt;p&gt;The Linux kernel is written mainly in C, but work to make Rust usable is also underway. This is not a rewrite of the entire existing Linux in Rust, but an effort to increase options while allowing C and Rust to coexist.&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://docs.kernel.org/process/programming-language.html" rel="noopener noreferrer"&gt;Official Linux documentation&lt;/a&gt; / &lt;a href="https://rust-for-linux.com/" rel="noopener noreferrer"&gt;Rust for Linux&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  NVIDIA OpenShell
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/NVIDIA/OpenShell" rel="noopener noreferrer"&gt;NVIDIA OpenShell&lt;/a&gt; is an execution platform that controls file operations, communication, and other actions by AI agents through policies.&lt;/p&gt;

&lt;p&gt;Rust is used in the &lt;a href="https://github.com/NVIDIA/OpenShell/blob/main/crates/openshell-sandbox/README.md" rel="noopener noreferrer"&gt;sandbox runtime&lt;/a&gt;, which handles Linux isolation mechanisms, and in the &lt;a href="https://github.com/NVIDIA/OpenShell/blob/main/crates/openshell-server/README.md" rel="noopener noreferrer"&gt;server responsible for sandbox management and related tasks&lt;/a&gt;. Meanwhile, there are also SDKs in Python, TypeScript, Go, and other languages.&lt;/p&gt;

&lt;p&gt;In other words, it uses &lt;strong&gt;Rust for the foundation, with users connecting from multiple languages&lt;/strong&gt;. It can be seen as an example not only of replacing C/C++, but also of building a new AI foundation in Rust.&lt;/p&gt;

&lt;p&gt;OpenShell has been accepted as a &lt;a href="https://www.cncf.io/projects/openshell/" rel="noopener noreferrer"&gt;CNCF Sandbox project&lt;/a&gt;. Here, "CNCF Sandbox" is the name of the project's incubation stage and has a different meaning from the runtime isolation environment provided by OpenShell.&lt;/p&gt;

&lt;p&gt;Individuals can also participate in development, but the &lt;a href="https://github.com/NVIDIA/OpenShell/blob/main/CONTRIBUTING.md" rel="noopener noreferrer"&gt;Contributing Guide&lt;/a&gt; requires obtaining maintainer vouch approval before the first PR. AI-assisted implementation is allowed, but the submitter is required to understand and be able to explain their own changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  11. Security and Government Interest
&lt;/h2&gt;

&lt;p&gt;Mishandling memory can lead to serious vulnerabilities in OSs, browsers, and other software. Microsoft and Chromium each explain that about 70% of the vulnerabilities they examined were related to memory safety.&lt;/p&gt;

&lt;p&gt;However, these figures differ in scope, time period, severity, and other factors. Numbers from different studies cannot be compared as statistics collected under the same conditions.&lt;/p&gt;

&lt;p&gt;The U.S. NSA, CISA, and others also recommend planning a migration to memory-safe languages. Examples cited include not only Rust, but also Python, Go, Java, and others. This does not mean that "only Rust was mandated" or that "C/C++ was completely banned."&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://www.microsoft.com/en-us/msrc/blog/2019/07/we-need-a-safer-systems-programming-language/" rel="noopener noreferrer"&gt;Microsoft's explanation&lt;/a&gt; / &lt;a href="https://www.chromium.org/Home/chromium-security/memory-safety/" rel="noopener noreferrer"&gt;Chromium's explanation&lt;/a&gt; / &lt;a href="https://www.nsa.gov/serve-from-netstorage/Press-Room/Press-Releases-Statements/Press-Release-View/Article/3608324/us-and-international-partners-issue-recommendations-to-secure-software-products/index.html" rel="noopener noreferrer"&gt;Joint recommendation by the NSA and others&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  12. Rust's Weaknesses and Caveats
&lt;/h2&gt;

&lt;p&gt;Rust has clear strengths, but adoption also comes with the following costs.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Learning ownership, borrowing, and lifetimes takes time.&lt;/li&gt;
&lt;li&gt;Long compile times and language complexity can burden development.&lt;/li&gt;
&lt;li&gt;For small prototypes, Python can be more concise and allow faster development in some cases.&lt;/li&gt;
&lt;li&gt;There are migration costs related to existing libraries, team experience, interoperability with other languages, and more.&lt;/li&gt;
&lt;li&gt;Even with Rust, design mistakes and logic errors do not go away.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In addition, Rust's safety also depends on whether implementations such as &lt;code&gt;unsafe&lt;/code&gt; code, dependency libraries, and interfaces with other languages are correct. On November 9, 2026, Microsoft reported an issue related to an &lt;code&gt;unsafe&lt;/code&gt; implementation inside the Rust standard library.&lt;/p&gt;

&lt;p&gt;Sources: &lt;a href="https://blog.rust-lang.org/2026/03/02/2025-State-Of-Rust-Survey-results/" rel="noopener noreferrer"&gt;Rust User Survey&lt;/a&gt; / &lt;a href="https://www.microsoft.com/en-us/security/blog/2026/11/09/forge-lab-uses-agentic-tools-to-identify-memory-safety-issues-in-rust/" rel="noopener noreferrer"&gt;Microsoft FORGE report&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  13. Summary
&lt;/h2&gt;

&lt;p&gt;Rust is used not only as a language for writing low-level, machine-close code as an alternative to C/C++, but also for combining with Python and for building new foundations for the cloud and AI agents.&lt;/p&gt;

&lt;p&gt;Using Rust makes it possible to aim for both performance and safety. It can be combined with Python, with only part of the processing built in Rust.&lt;/p&gt;

&lt;p&gt;On the other hand, Rust also requires learning effort, migration effort, and build effort. Simply adopting it does not guarantee speed or safety. A realistic approach is to use it together with existing languages, based on the use case and measurement results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Postscript: Rust 1.100.0 Is Out
&lt;/h2&gt;

&lt;p&gt;On November 12, just before this article went out, Rust 1.100.0 was released — the milestone 100th release in the 1.x line.&lt;/p&gt;

&lt;p&gt;The main changes are as follows.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Never type (!) stabilized — after 10 years and 5 stabilization attempts, the type of computations that never return a value can now be named anywhere in code&lt;/li&gt;
&lt;li&gt;Allocator API stabilized — custom allocators can now be used with types such as Vec and Box&lt;/li&gt;
&lt;li&gt;DropGuard added — a helper that runs a closure on every exit path from a scope, making cleanup and rollback easier to write&lt;/li&gt;
&lt;li&gt;Cargo min-publish-age — you can set a cooldown so Cargo waits before adopting freshly published versions, a supply-chain security measure&lt;/li&gt;
&lt;li&gt;Cargo unused-dependency warnings — Cargo now reports dependencies that are no longer used&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A deep language change like the never type and a supply-chain safeguard landed in the same milestone release.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://blog.rust-lang.org/2026/11/12/Rust-1.100.0/" rel="noopener noreferrer"&gt;Announcing Rust 1.100.0&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>What I Learned Setting Up OpenClaw: Four Boundaries I Had to Decide</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Fri, 13 Nov 2026 00:01:58 +0000</pubDate>
      <link>https://dev.to/moruku36/what-i-learned-setting-up-openclaw-four-boundaries-i-had-to-decide-3422</link>
      <guid>https://dev.to/moruku36/what-i-learned-setting-up-openclaw-four-boundaries-i-had-to-decide-3422</guid>
      <description>&lt;p&gt;The official site promises a setup that works right away. To run it safely, I had to define the boundaries one by one.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;I installed OpenClaw in my home AI lab. The official site says you can just install it and start using it, but I couldn't operate it as-is.&lt;br&gt;
Each time I expanded what it could do, I redefined the boundary, and I only recorded what worked with evidence. This post summarizes that work.&lt;br&gt;
Note: in the linked records at the end, I refer to OpenClaw by my nickname for it, "Kurotchi".&lt;/p&gt;

&lt;h2&gt;
  
  
  2. I Drew the Line Between Isolation and Usability
&lt;/h2&gt;

&lt;p&gt;At first, following a suggestion from an AI agent on the ChatGPT side, I prioritized isolation. I put OpenClaw in an isolated Docker environment, designed so it couldn't see credentials.&lt;br&gt;
But from inside that isolated environment I couldn't use the dev CLI directly, and every task needed a workaround. The overhead grew and the work stopped flowing.&lt;br&gt;
So on my own judgment, I switched to running the working agent directly on my Mac.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Run the runtime on the Mac&lt;br&gt;
Operate the browser in a separate environment&lt;br&gt;
Handle credentials separately&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I separated the runtime, the browser, and authentication. If the setup isn't sustainable, it won't keep running, no matter how safe it is.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. I Separated Authentication from Authorization
&lt;/h2&gt;

&lt;p&gt;Pushing branches and creating PRs on GitHub worked. Still, normal work stopped halfway. Approval for child sessions was missing.&lt;br&gt;
Being logged in and being allowed to act were two different things. So I separated authentication, operation permissions, and approval prompts, and I also split execution from collecting results.&lt;br&gt;
I limited the admin UI to loopback, and I did not pass the Docker control socket to the browser container.&lt;br&gt;
I verified features in small steps using public pages and dummy data. On November 9, 2026, I confirmed a push of a real work branch and a successful CI run, but that doesn't mean it can do everything.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Authentication shows who you are&lt;br&gt;
Permissions show what you can touch&lt;br&gt;
Approvals ask for permission each time&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;My policy is to operate only within the range I have verified.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. I Bridged Scheduled Jobs and Normal Chat
&lt;/h2&gt;

&lt;p&gt;I use Meta's Muse, ChatGPT, and OpenClaw together. They are three AI agents with different design philosophies.&lt;br&gt;
I share scheduled task status on a message board in a GitHub repo, running a multi-AI workflow where the agents help each other.&lt;br&gt;
In scheduled processing, I could read the inbox. But that didn't mean I could use that content directly in normal conversation.&lt;br&gt;
So I built a traceable path from the received body back to its source, and made it routine to read it back and confirm the match. I don't treat received text as permission to execute.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Check the inbox contents&lt;br&gt;
Trace body and source from the conversation&lt;br&gt;
Share summaries only&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;State sharing is limited to non-sensitive summaries, with restricted destinations, frequency, and deduplication. Delivery is still not perfect.&lt;br&gt;
Connecting things with different designs and policies on the same foundation is hard.&lt;/p&gt;

&lt;p&gt;I treat being able to read the inbox and getting that content into a conversation as two separate things.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. I Separated the Billing Path
&lt;/h2&gt;

&lt;p&gt;At first I was running on pay-as-you-go OpenAI API usage. It cost about $15 in one day, which wasn't sustainable.&lt;br&gt;
On a suggestion from an AI agent on the ChatGPT side, I changed the route to one tied to a Codex subscription. I didn't change the model or the reasoning level.&lt;br&gt;
I emptied the fallback candidates for the target agent's model. If the subscription isn't available, it stops. It won't automatically fall back to the paid API.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Use the subscription route normally&lt;br&gt;
Stop if it's unavailable&lt;br&gt;
Never fall back to metered usage&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A design that stops when it can't run seemed like the best way to prevent surprise charges.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Limitations
&lt;/h2&gt;

&lt;p&gt;Fully autonomous operation, complete separation of auth sessions, and stability after restarts are all unverified.&lt;br&gt;
Behavior when hitting subscription limits is untested. So I can't say API costs go to zero, and I haven't measured the actual savings.&lt;br&gt;
This record is organized by cross-checking existing public build logs. I didn't run new live tests for this writeup.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Conclusion
&lt;/h2&gt;

&lt;p&gt;I decided the boundaries one at a time, and recorded only what succeeded. The operation is still in progress, but the approach is becoming clear.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Ahead
&lt;/h2&gt;

&lt;p&gt;On November 13, I learned about OpenShell at an NVIDIA seminar. OpenShell is the runtime included in NemoClaw, NVIDIA's collection of open blueprints for building agents. It controls agent behavior through policies and runs agents inside a sandbox. NemoClaw also provides a blueprint for running OpenClaw agents as they are.&lt;/p&gt;

&lt;p&gt;In my current OpenClaw setup, the boundaries are maintained through configuration and operating rules. Combining it with OpenShell could let the runtime itself enforce those boundaries. Aiming for an enterprise-grade, secure AI agent OSS, I have added this to my implementation plans.&lt;/p&gt;

&lt;p&gt;This is still at the concept stage; verification comes next.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;11月6日 OpenClaw／クロッチ導入・検証記録 &lt;a href="https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/openclaw-status-2026-11-06.ja.md" rel="noopener noreferrer"&gt;https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/openclaw-status-2026-11-06.ja.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;11月8日 ホームラボとクロッチの構築レポート &lt;a href="https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/home-lab-kurotchi-build-report-2026-11-08.ja.md" rel="noopener noreferrer"&gt;https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/home-lab-kurotchi-build-report-2026-11-08.ja.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;11月9日 クロッチの改善記録 &lt;a href="https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/kurotchi-improvements-2026-11-09.ja.md" rel="noopener noreferrer"&gt;https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/kurotchi-improvements-2026-11-09.ja.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;11月10日 ラウンジ復旧と Codex サブスク切替 &lt;a href="https://github.com/moruku36/home-ai-engineering-lab/blob/47d3068d86db54499368602d6b3d28a7d3569e3b/docs/kurotchi-lounge-codex-cutover-2026-11-10.ja.md" rel="noopener noreferrer"&gt;https://github.com/moruku36/home-ai-engineering-lab/blob/47d3068d86db54499368602d6b3d28a7d3569e3b/docs/kurotchi-lounge-codex-cutover-2026-11-10.ja.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;NVIDIA NemoClaw (OpenShell) &lt;a href="https://www.nvidia.com/en-us/ai/nemoclaw/" rel="noopener noreferrer"&gt;https://www.nvidia.com/en-us/ai/nemoclaw/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>docker</category>
      <category>security</category>
    </item>
    <item>
      <title>What I Took from OpenAI Japan Live: New Models and the Automation of Development</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Thu, 12 Nov 2026 00:01:06 +0000</pubDate>
      <link>https://dev.to/moruku36/what-i-took-from-openai-japan-live-new-models-and-the-automation-of-development-13e0</link>
      <guid>https://dev.to/moruku36/what-i-took-from-openai-japan-live-new-models-and-the-automation-of-development-13e0</guid>
      <description>&lt;p&gt;I watched OpenAI Japan Live (November 11, 2026, online) and organized the key points on the model lineup, defense, development automation, and migration.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;I watched OpenAI Japan Live, held on November 11, 2026, online. It had four sessions: new models and products, autonomous defense, development automation with Codex, and migration practices with Hitachi.&lt;br&gt;
The central theme was combining multiple models to move development and operations forward, rather than relying on a single powerful model. I will look back at each session in order.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. New Models and Products
&lt;/h2&gt;

&lt;p&gt;A setup was shown where you choose the best model based on task complexity and immediacy. To balance cost and performance, &lt;strong&gt;using different models&lt;/strong&gt; for different jobs is the default.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;GPT-6 Astra&lt;/strong&gt;　The top-tier model, handling advanced design and reasoning&lt;br&gt;
・&lt;strong&gt;GPT-6.1 Sol&lt;/strong&gt;　Offers equivalent performance at 1/5 the cost of Astra&lt;br&gt;
・&lt;strong&gt;GPT-6.1 Terra&lt;/strong&gt;　Specialized for document generation and screen operations&lt;br&gt;
・&lt;strong&gt;GPT-6 Luna&lt;/strong&gt;　Handles routine implementation and bulk processing at low cost&lt;br&gt;
・&lt;strong&gt;GPT-6 UltraFast&lt;/strong&gt;　Delivers up to 8x the normal speed&lt;br&gt;
・&lt;strong&gt;GPT-6 Cyber&lt;/strong&gt;　Specialized for diagnosis and verification, offered only to TAC members&lt;/p&gt;

&lt;p&gt;Features and products beyond the models each have their own roles.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Image 2.6&lt;/strong&gt;　Supports GIF generation from handwriting and SVG generation, limiting changes outside specified areas. It comes in quality-focused Sunburst and speed-focused Flare, with Flare cutting processing time to about half of the 2.5 generation&lt;br&gt;
・&lt;strong&gt;GPT Live&lt;/strong&gt;　A voice conversation feature that handles interruptions while speaking, adding Himari and Rido as Japanese voices&lt;br&gt;
・&lt;strong&gt;Dots&lt;/strong&gt;　Stays resident 24 hours a day, remembers context, and suggests next actions&lt;br&gt;
・&lt;strong&gt;ChatGPT Spaces&lt;/strong&gt;　Detects outdated descriptions and updates them, serving as a foundation for team sharing&lt;br&gt;
・&lt;strong&gt;ChatGPT Slides&lt;/strong&gt;　Lets you instruct edits directly on slides using annotations&lt;br&gt;
・&lt;strong&gt;Sizes&lt;/strong&gt;　Integrates with RDBs, storage, and MCP, and shares with authentication. It aims to prevent unmanaged sprawl of internal apps&lt;br&gt;
・&lt;strong&gt;Decisions API&lt;/strong&gt;　Runs GPT-6 behind the scenes, executing classification that used to take 1.4 seconds in as fast as 130ms to under 280ms&lt;br&gt;
・&lt;strong&gt;Agents API&lt;/strong&gt;　Extends Codex execution targets to managed infrastructure and proprietary environments such as AWS&lt;/p&gt;

&lt;h2&gt;
  
  
  3. AI-Powered Cyber Defense
&lt;/h2&gt;

&lt;p&gt;The average time from vulnerability disclosure to exploitation has shrunk from 2.3 years in 2018 to 10 hours in 2026. Meanwhile, 87% of companies keep systems running with known exploitable vulnerabilities still in place. The idea to close this gap by getting ahead of attackers and finishing fixes in advance is the &lt;strong&gt;defenders' window&lt;/strong&gt;.&lt;br&gt;
In &lt;a href="https://openai.com/index/patch-the-planet/" rel="noopener noreferrer"&gt;Patch the Planet&lt;/a&gt; with Trail of Bits and Calif, GPT-5.6 Sol and others identified flaws in PHP and carried fixes through to completion. The performance figures were shown as follows.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;SEC-bench Pro&lt;/strong&gt;　(&lt;a href="https://arxiv.org/abs/2605.26548v2" rel="noopener noreferrer"&gt;benchmark paper&lt;/a&gt;) GPT-6 Cyber at 87%, Astra at 85.4%, 5.6 Sol at 79.1%&lt;br&gt;
・&lt;strong&gt;ExploitGym&lt;/strong&gt;　(&lt;a href="https://arxiv.org/abs/2605.11086" rel="noopener noreferrer"&gt;benchmark paper&lt;/a&gt;) GPT-6 Cyber at 48.5%, Astra at 42.4%, 5.6 Sol at 30.3%&lt;/p&gt;

&lt;p&gt;Access to powerful cyber capabilities is controlled through an approval-based system called &lt;a href="https://help.openai.com/en/articles/20001258-openai-daybreak-trusted-access-for-cyber-overview" rel="noopener noreferrer"&gt;Trusted Access for Cyber (TAC)&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Daybreak Blue&lt;/strong&gt;　Handles broad defense work such as code review, vulnerability triage, and malware analysis&lt;br&gt;
・&lt;strong&gt;Daybreak Red&lt;/strong&gt;　Handles approved specialist work such as PoC development and penetration testing&lt;/p&gt;

&lt;p&gt;For the same PoC request, the difference was shown as: regular GPT-5.5 refuses, Blue creates assets for verification, and Red proceeds to execution in an approved environment. Limits and behavior change by tier.&lt;br&gt;
The Codex Security Plugin monitors inside the IDE, and Codex Security Cloud works with GitHub and GitLab to monitor continuously. Remediation proceeds in the following four stages.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Discovery&lt;/strong&gt;　Find issues from structure and paths, and assign severity&lt;br&gt;
・&lt;strong&gt;Verification&lt;/strong&gt;　Reproduce the conditions and impact to confirm them&lt;br&gt;
・&lt;strong&gt;Fix&lt;/strong&gt;　Generate and apply patches for the root cause&lt;br&gt;
・&lt;strong&gt;Proof&lt;/strong&gt;　Record that the issue is resolved through reproduction tests&lt;/p&gt;

&lt;p&gt;The defense posture was evaluated across the following five perspectives.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Coverage and readiness&lt;/strong&gt;　Look at the share of planned targets that were actually verified&lt;br&gt;
・&lt;strong&gt;Detection quality&lt;/strong&gt;　Look at the share of detections that were real issues&lt;br&gt;
・&lt;strong&gt;Assignment and handoff&lt;/strong&gt;　Look at the time from ticket creation to owner assignment&lt;br&gt;
・&lt;strong&gt;Fix and re-verification&lt;/strong&gt;　Look at the number of completed fixes and the days from detection to completion&lt;br&gt;
・&lt;strong&gt;Effort and cost&lt;/strong&gt;　Look at the reduction rate in human effort and the operating cost of the execution environment&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Harness Engineering and the Software Factory
&lt;/h2&gt;

&lt;p&gt;Codex takes input, reasons via the Response API, and repeats search, diff review, and command execution in the App Server and Sandbox. Harness engineering is the technique of tuning instructions and tools to stabilize this loop. &lt;strong&gt;Foundation design&lt;/strong&gt; determines accuracy.&lt;br&gt;
agent.md is a file that records the ground rules loaded at startup, preserving reproducibility even when history is cleared. Packing everything into it reduces accuracy through contamination, so procedures are split into Skills. What to write in agent.md includes the following.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Repository structure&lt;/strong&gt;　State the repository structure and dependencies explicitly&lt;br&gt;
・&lt;strong&gt;Commands&lt;/strong&gt;　Define commands for setup, builds, and checks&lt;br&gt;
・&lt;strong&gt;Conventions&lt;/strong&gt;　Set conventions for naming and function size&lt;br&gt;
・&lt;strong&gt;Constraints&lt;/strong&gt;　Set safety constraints such as files that must not be changed&lt;br&gt;
・&lt;strong&gt;Learning&lt;/strong&gt;　Update failure records to learn from them&lt;br&gt;
・&lt;strong&gt;Separation&lt;/strong&gt;　Separate work procedures into .codex/skills/&lt;/p&gt;

&lt;p&gt;Models are also assigned by use. Routine bulk implementation gets GPT-6 Luna with Reasoning Effort Max, and interactive design gets GPT-6.1 Sol with Mid. As operating patterns, six types of automation were shown.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Symphony&lt;/strong&gt;　Starts from a ticket and moves from implementation through to PR&lt;br&gt;
・&lt;strong&gt;Issue Planner&lt;/strong&gt;　Deduplicates requests and bug reports, and confirms reproduction&lt;br&gt;
・&lt;strong&gt;Build Factory&lt;/strong&gt;　Launches a GUI on a VM to verify behavior&lt;br&gt;
・&lt;strong&gt;PR Review Bot&lt;/strong&gt;　Adds checks on affected areas&lt;br&gt;
・&lt;strong&gt;Perf-Factory&lt;/strong&gt;　Creates a fix PR when performance degradation is detected&lt;br&gt;
・&lt;strong&gt;Sev-Bot&lt;/strong&gt;　Shows mitigations and root-cause fixes when an outage alert fires&lt;/p&gt;

&lt;p&gt;In the migration from Enzyme to React Testing Library, investigation and planning, implementation, and verification are repeated, returning to the previous stage when targets are missed. Since the same Codex App Server and Core run on the CLI, Desktop App, and IDE Extension screens, harnesses can be shared across the team.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Hitachi's Legacy Modernization in Practice
&lt;/h2&gt;

&lt;p&gt;Japan's core systems have specs that no longer match reality, and they have become black boxes as the engineers who knew them retire. Test code often does not remain, so rewriting them suddenly risks breaking hidden exception handling.&lt;br&gt;
OpenAI's FDE and Hitachi, Ltd. ran a joint project to recover business logic from millions of lines of legacy code (&lt;a href="https://www.hitachi.com/en/press/articles/2026/06/0617/" rel="noopener noreferrer"&gt;Hitachi, Ltd. press release&lt;/a&gt;). FDE is OpenAI's engineering organization that embeds with customers on-site to solve hard problems. Before migration, they auto-generated regression test suites that reproduce current behavior to build a &lt;strong&gt;safe foundation&lt;/strong&gt;. The role split is as follows.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;AI's role&lt;/strong&gt;　Analyze code to extract logic, and create draft specs and regression test suites&lt;br&gt;
・&lt;strong&gt;Human's role&lt;/strong&gt;　Hitachi experts use domain knowledge to verify validity, assess exception cases, and give final approval&lt;/p&gt;

&lt;p&gt;In the early stages, ambiguous behavior of older languages, such as global variables with side effects, threw off AI reasoning. A key point is that accuracy was improved through repeated human verification.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Caveats
&lt;/h2&gt;

&lt;p&gt;The figures and content in this article are secondary information based on session presentations and transcripts of recordings. You need to check official materials for formal specs and the latest offering terms.&lt;br&gt;
Features with strong privileges are managed under the TAC &lt;strong&gt;approval system&lt;/strong&gt; and cannot be used unconditionally. The effectiveness of agent.md and Skills also depends on how well the setup and procedures are maintained.&lt;/p&gt;

&lt;p&gt;・&lt;strong&gt;Check figures&lt;/strong&gt;　Verify figures and content against primary sources&lt;br&gt;
・&lt;strong&gt;Design for approval&lt;/strong&gt;　Design strong privileges on the assumption of approval&lt;br&gt;
・&lt;strong&gt;Maintain instructions&lt;/strong&gt;　Maintain instructions and procedures to stabilize results&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Summary
&lt;/h2&gt;

&lt;p&gt;On both defense and development, permission management and reproducibility are the foundation. The idea is that the more powerful a capability is, the more approval and verification it gets, leaving a history of the work.&lt;br&gt;
Legacy migration is the same: to proceed safely, confirm current behavior first and then fix. Deciding the split between AI and humans is the shortcut.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;p&gt;I structured this based on the OpenAI Japan Live session presentations.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>openai</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>The Meta AI Hackathon Is Over: What the Winners of 5,367 Projects Built, and What I Learned by Missing Out</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Wed, 11 Nov 2026 00:02:25 +0000</pubDate>
      <link>https://dev.to/moruku36/the-meta-ai-hackathon-is-over-what-the-winners-of-5367-projects-built-and-what-i-learned-by-glc</link>
      <guid>https://dev.to/moruku36/the-meta-ai-hackathon-is-over-what-the-winners-of-5367-projects-built-and-what-i-learned-by-glc</guid>
      <description>&lt;p&gt;I didn't win, but almost every top project had one thing in common: &lt;strong&gt;a built-in verification mechanism&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;This is part 2 of my Meta Global AI Developer Hackathon results report.&lt;/p&gt;

&lt;p&gt;In part 1, I wrote about why I joined and what I submitted.&lt;/p&gt;

&lt;p&gt;In this part 2, I'll introduce the winners announced at the closing ceremony.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What I Learned at the Closing
&lt;/h2&gt;

&lt;p&gt;There were roughly 33,000-40,000 applicants, with 20,000 participants.&lt;/p&gt;

&lt;p&gt;There were 5,367 submitted projects, with over $1M in total prizes.&lt;/p&gt;

&lt;p&gt;At the closing, finalists pitched live and judges reviewed them on the spot.&lt;/p&gt;

&lt;p&gt;After deliberation, winners were announced for the Indie and Startup tracks, plus special prizes.&lt;/p&gt;

&lt;p&gt;Only the $10,000 Community Vote was still open.&lt;/p&gt;

&lt;p&gt;The winner is scheduled to be announced on 2026-11-16.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Indie Track Winners
&lt;/h2&gt;

&lt;p&gt;The Indie track is for individuals and small teams.&lt;/p&gt;

&lt;p&gt;All five top projects had strong ties to the real world.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;🥇 &lt;strong&gt;ControlAnything&lt;/strong&gt; is an AR assistance app for Quest 3. Pinch a real physical device and it automatically generates a working connector for it on the spot.&lt;/p&gt;

&lt;p&gt;🥈 &lt;strong&gt;Gatekeeper&lt;/strong&gt; is an inspection tool that monitors new npm packages. It detected malware about a day earlier than public lists, and requires cited evidence for its findings.&lt;/p&gt;

&lt;p&gt;🥉 &lt;strong&gt;David Barry&lt;/strong&gt; is a home assessment app for making use of basements. Just take photos with your phone to learn whether you can legally turn it into a second home, and how.&lt;/p&gt;

&lt;p&gt;4th: &lt;strong&gt;Aurora (Nemesis)&lt;/strong&gt; is a physics simulation generator for robot training. It builds environments from natural language or images and can retrain legged robots in them.&lt;/p&gt;

&lt;p&gt;5th: &lt;strong&gt;Video2URDF&lt;/strong&gt; is a conversion tool that creates robot models from video. It automatically generates URDFs from videos of articulated objects, cutting development effort.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  4. Startup Track Winners
&lt;/h2&gt;

&lt;p&gt;The Startup track is for teams aiming to build businesses.&lt;/p&gt;

&lt;p&gt;The winners tackled concrete work in the field, manufacturing, and other domains.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;🥇 &lt;strong&gt;Consai (Punchwalk)&lt;/strong&gt; is a defect management tool for construction sites. It creates verified punch lists from voice and photos to reduce rework.&lt;/p&gt;

&lt;p&gt;🥈 &lt;strong&gt;Formwright&lt;/strong&gt; is a hardware design tool that goes from prompt to physical device. It generates circuits, boards, enclosures, and firmware, all the way to a manufacturing order.&lt;/p&gt;

&lt;p&gt;🥉 &lt;strong&gt;ORCA&lt;/strong&gt; is a design support tool for interference between 3D models. It doesn't just detect collisions — it proposes fixes with geometric proof.&lt;/p&gt;

&lt;p&gt;4th: &lt;strong&gt;Voluma Bio&lt;/strong&gt; is a 3D measurement tool for research. It automatically generates 3D measurements from micro-CT images to help with analysis.&lt;/p&gt;

&lt;p&gt;5th: &lt;strong&gt;Kroonen AI (Glimmer Scope)&lt;/strong&gt; is a tool for improving model interpretability. It visualizes LLMs' internal concepts and lets you probe behavior with dials.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  5. Special Prizes
&lt;/h2&gt;

&lt;p&gt;Special prizes went to projects with outstanding technology or creativity.&lt;/p&gt;

&lt;p&gt;Several of them also had verification built in.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Most Viral: &lt;strong&gt;Adrian's Playtest Agent&lt;/strong&gt; is a game testing assistant. It plays games from screenshots alone and reports bugs with replay verification.&lt;/p&gt;

&lt;p&gt;Best Build on Meta Open Weights: &lt;strong&gt;Tessa&lt;/strong&gt; is an astronomical data analysis tool. It autonomously searched NASA TESS data for exoplanet candidates and found 8 new ones.&lt;/p&gt;

&lt;p&gt;Best Agentic: &lt;strong&gt;oqed&lt;/strong&gt; is a code optimization tool. It has an LLM write fast assembly code and only accepts output that passes strict verification.&lt;/p&gt;

&lt;p&gt;Best Creative: &lt;strong&gt;Team Synthexis's synthexis&lt;/strong&gt; is an instrument you play with a webcam. You can perform a synthesizer with hand and face movements for intuitive expression.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  6. My Result and Takeaways
&lt;/h2&gt;

&lt;p&gt;I submitted &lt;strong&gt;Trifecta Checker&lt;/strong&gt; solo to the Indie track.&lt;/p&gt;

&lt;p&gt;It was a checker app that verifies AI output on three dimensions.&lt;/p&gt;

&lt;p&gt;The result: no prize, and I didn't make the finalists.&lt;/p&gt;

&lt;p&gt;Missing out was disappointing, but seeing the top projects, I understood why.&lt;/p&gt;

&lt;p&gt;What many of them shared was &lt;strong&gt;verification built into the product itself&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Cited evidence, verification gates, geometric proofs, replay verification, and more were all baked in.&lt;/p&gt;

&lt;p&gt;It felt like the question wasn't just what you can make AI generate, but how you make the result trustworthy.&lt;/p&gt;

&lt;p&gt;The other thing was how deeply they stepped into the real world.&lt;/p&gt;

&lt;p&gt;Construction sites, basements, robots, research images — the targets were specific.&lt;/p&gt;

&lt;p&gt;I think my project was close in its focus on verification.&lt;/p&gt;

&lt;p&gt;But the link between the target domain and that verification felt weak.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Caveats
&lt;/h2&gt;

&lt;p&gt;These results are based on the announcements at the closing.&lt;/p&gt;

&lt;p&gt;The Community Vote is not final yet and is subject to change.&lt;/p&gt;

&lt;p&gt;The official gallery entries are the source of truth for each project.&lt;/p&gt;

&lt;p&gt;The intros in this article are 2-3 sentence summaries of the key points.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Wrap-up
&lt;/h2&gt;

&lt;p&gt;Looking at the top projects, I felt that how you build trust mattered as much as flashiness.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Built-in verification&lt;/strong&gt; and a dive into the field will be my guide going forward.&lt;/p&gt;

&lt;p&gt;For my next build, I want to narrow the target to one thing and build it all the way through verification.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;p&gt;Official gallery pages for the winners (Cerebral Valley)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ControlAnything: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/3441" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/3441&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Gatekeeper: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/1193" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/1193&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;David Barry: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/4356" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/4356&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Aurora（Nemesis）: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2723" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2723&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Video2URDF: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2050" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2050&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Consai（Punchwalk）: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/4672" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/4672&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Formwright: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/3836" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/3836&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;ORCA by IssueLab: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/3002" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/3002&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Voluma Bio: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/4991" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/4991&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Kroonen AI（Glimmer Scope）: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2162" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2162&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Adrian（Playtest Agent）: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/531" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/531&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Tessa: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2303" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/2303&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;oqed: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/149" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/149&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Team Synthexis（synthexis）: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/5090" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon/hackathon/gallery/5090&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>hackathon</category>
      <category>startup</category>
    </item>
    <item>
      <title>Observing a slowdown: when long conversations with my AI agent get heavy on Windows</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Tue, 10 Nov 2026 00:14:32 +0000</pubDate>
      <link>https://dev.to/moruku36/observing-a-slowdown-when-long-conversations-with-my-ai-agent-get-heavy-on-windows-1170</link>
      <guid>https://dev.to/moruku36/observing-a-slowdown-when-long-conversations-with-my-ai-agent-get-heavy-on-windows-1170</guid>
      <description>&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;As I kept using the same conversation with dots on Windows, the response of on-screen operations gradually became slower. This article is a record of that observation.&lt;/p&gt;

&lt;p&gt;By "dots," I mean my personal AI agent that runs continuously in OpenAI's environment and keeps working on the tasks I give it.&lt;/p&gt;

&lt;p&gt;What this article deals with is latency in the UI itself: typing, rendering, and switching between conversations. dots is an always-on agent that runs on the cloud side, and the conversation itself proceeds outside my local PC. The time the AI takes to generate a response, or the time dots takes to finish a task I asked for, is a separate matter from how sluggish the screen in front of me feels. When I say "heavy" in this article, I mean the latter: the UI operation latency.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Symptoms
&lt;/h2&gt;

&lt;p&gt;The operations that became slow were the following:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The time between typing a character and seeing it appear on screen&lt;/li&gt;
&lt;li&gt;The response to send actions and button presses&lt;/li&gt;
&lt;li&gt;Scrolling and screen refreshes&lt;/li&gt;
&lt;li&gt;Loading and switching between past conversations&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;At times, each operation felt like it took about 1–3 seconds (these are impressions, not measurements). The longer I kept using the same conversation, the heavier it tended to get. In a newly started regular chat, by contrast, I did not feel this slowness. Once it became considerably faster again, but later the problem returned.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Environment
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The machine is a Windows PC with 32 GB of memory&lt;/li&gt;
&lt;li&gt;The latency remained in the same dots conversation, both in the app and in the browser&lt;/li&gt;
&lt;li&gt;On the same PC, Notepad and newly started regular chats felt fast&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That said, the fact that Notepad and new regular chats felt fast does not rule out a problem with the PC as a whole.&lt;/p&gt;

&lt;p&gt;I do not have the exact version numbers of the app or OS I was using. I also did not measure the latency quantitatively, and the cause has not been identified.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. What I tried
&lt;/h2&gt;

&lt;p&gt;I tried the following, but could not confirm any lasting improvement:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Display-related measures: I tried changing settings inside the app, but could not confirm any lasting improvement. On the Windows side, I confirmed that the transparency and animation effects were Off (their state before that check is unknown)&lt;/li&gt;
&lt;li&gt;Cleanup such as organizing tabs and closing the browser: memory usage went down, but the latency in the same conversation remained&lt;/li&gt;
&lt;li&gt;Closing, reopening, and restarting the app: it did become considerably faster once in the morning, but that was after a Windows Update and a restart, and before I changed any display settings. The effect of another restart in the afternoon has not been confirmed&lt;/li&gt;
&lt;li&gt;Opening the same dots in a different browser: I did not feel any major improvement&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Since I tried these in combination, I cannot separate out how effective each individual measure was. The temporary improvement that day happened before the display-related measures, so it cannot be credited to them.&lt;/p&gt;

&lt;p&gt;Separately, entering text into the conversation from my iPhone felt faster, so I am considering an arrangement where I work on the PC but split off just the conversation input to the iPhone. This is based on a comparative impression; I have not measured any improvement.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Current status
&lt;/h2&gt;

&lt;p&gt;In the public Issues, there are multiple similar reports of operations becoming heavy within the same conversation or during long sessions. The related public information is as follows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Issue list: &lt;a href="https://github.com/openai/codex/issues" rel="noopener noreferrer"&gt;https://github.com/openai/codex/issues&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issue #38547: &lt;a href="https://github.com/openai/codex/issues/38547" rel="noopener noreferrer"&gt;https://github.com/openai/codex/issues/38547&lt;/a&gt; — A contributor explained that a specific contributing cause had been addressed in a particular version, and the issue is now Closed&lt;/li&gt;
&lt;li&gt;Issue #20214: &lt;a href="https://github.com/openai/codex/issues/20214" rel="noopener noreferrer"&gt;https://github.com/openai/codex/issues/20214&lt;/a&gt; — A contributor explained a fix for one contributing factor in slowdowns during long sessions. Since then, there have been posts reporting both improvement and persistence&lt;/li&gt;
&lt;li&gt;PR #40672: &lt;a href="https://github.com/openai/codex/pull/40672" rel="noopener noreferrer"&gt;https://github.com/openai/codex/pull/40672&lt;/a&gt; — A related code change has been merged into main&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;However, each of these is an explanation of work on an individual cause; none of them means that all symptoms are fixed, and they are not a guarantee by the company. Nor is it certain that a merged change has reached every distribution channel.&lt;/p&gt;

&lt;p&gt;As for my own case, I reported it to OpenAI support and received confirmation that the report was received. I have not received a reply, a root-cause determination, or a fix timeline, and the matter is currently at the stage of having asked for their handling. I also do not know whether my case shares a cause with any of the public Issues.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Summary
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Continuing the same conversation with dots on Windows left latency in typing, rendering, and conversation switching&lt;/li&gt;
&lt;li&gt;I tried settings changes, cleanup, restarts, and more, but could not confirm any lasting improvement&lt;/li&gt;
&lt;li&gt;The cause has not been identified, and I am at the stage of having reported it to support and asked for their handling&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  7. Update (November 13, 2026)
&lt;/h2&gt;

&lt;p&gt;On November 13, 2026, OpenAI announced an update to dots in a post from the official ChatGPT account. The update includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Faster replies&lt;/li&gt;
&lt;li&gt;Less jargon, making explanations easier to follow&lt;/li&gt;
&lt;li&gt;Better follow-through on requested work&lt;/li&gt;
&lt;li&gt;Custom instructions: you can now instruct your dot directly in the thread, and set instructions and rules under Customize &amp;gt; Behavior on mobile, or from your dot's menu on web and desktop&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In my environment, the interface feels noticeably lighter after this update. That said, I cannot yet say whether the slowdown this article describes — the UI growing heavier as a single conversation continues — is fixed. I have not measured anything, so for now this is only an impression.&lt;/p&gt;

&lt;p&gt;Source: OpenAI, post from the official ChatGPT account (November 13, 2026)&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>I Built a Home Lab Where AI Agents Can Work: Two Physical Machines, What Works, and the Walls I Hit</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Sun, 08 Nov 2026 01:51:31 +0000</pubDate>
      <link>https://dev.to/moruku36/i-built-a-home-lab-where-ai-agents-can-work-two-physical-machines-what-works-and-the-walls-i-hit-25h3</link>
      <guid>https://dev.to/moruku36/i-built-a-home-lab-where-ai-agents-can-work-two-physical-machines-what-works-and-the-walls-i-hit-25h3</guid>
      <description>&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;I SSH into my home server on a weekend night. The services are running. But I do not know where I left off. I ask AI to continue. It cannot carry over the state.&lt;/p&gt;

&lt;p&gt;This post is the build log to change that. I wanted more than a lab that starts services. I wanted &lt;strong&gt;a lab that can hand off work and state&lt;/strong&gt;. The physical devices are two machines: an Intel NUC and a Mac mini.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Setup
&lt;/h2&gt;

&lt;p&gt;The center is an Intel NUC (Ubuntu). It runs the automation and monitoring base on Docker Compose. It also has a QEMU/KVM VM for analysis, with no virtual NIC.&lt;/p&gt;

&lt;p&gt;The extra always-on host is a Mac mini (M4). It runs OpenClaw, with an agent that can call Codex and Claude Code. For state sharing between multiple AIs, I use a message board on a GitHub repository.&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Intel NUC: n8n, GitHub data collection and report generation, Prometheus, Grafana, Uptime Kuma&lt;/li&gt;
&lt;li&gt;Analysis VM: offline analysis experiments with REA and Ghidra&lt;/li&gt;
&lt;li&gt;Mac mini: OpenClaw, Codex, Claude Code&lt;/li&gt;
&lt;li&gt;Message board: state sharing between multiple AIs (GitHub repository)&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;It is easy to think more machines means distributed work. In reality, it only adds places. Without a shared board for state, the machines are not connected.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. What I Built
&lt;/h2&gt;

&lt;p&gt;On the NUC, I checked manual runs from GitHub data collection to Markdown report generation to reference via MCP. For Prometheus and Grafana, I checked normal responses from collection targets. I also did encrypted backups and a restore test in an isolated environment.&lt;/p&gt;

&lt;p&gt;On the Mac mini, I checked starting both CLIs from OpenClaw, and got as far as limited generation like edit plans and short replies. In a dedicated GitHub test, push, PR creation, and merge all succeeded. For the message board, I checked regular state posts and a path to read received text in normal chat.&lt;/p&gt;

&lt;p&gt;Once it works, it is tempting to assume it will work every time. In reality, results change when conditions change. I count these three separately.&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Scheduled runs are set up&lt;/li&gt;
&lt;li&gt;Manual runs succeed&lt;/li&gt;
&lt;li&gt;All required items were collected&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  4. Walls Unique to Physical Machines
&lt;/h2&gt;

&lt;p&gt;The first wall was SSH. The SSH agent offered too many keys, and I hit the limit on auth failures. Keyboard layout differences also caused input mismatches.&lt;/p&gt;

&lt;p&gt;The next wall was screen lock. Screen lock after login blocked remote operation. It still happened in the final build stage. &lt;strong&gt;Being able to SSH in and being able to unlock the GUI are different things.&lt;/strong&gt; I checked this separately from full headless operation.&lt;/p&gt;

&lt;p&gt;FileVault and auto-login are a tradeoff. Recovery after reboot and sleep remain as separate check items. Unlike cloud VMs, physical machines have "screen", "power", and "keys" as separate, independent walls.&lt;/p&gt;

&lt;p&gt;SSH access can seem to mean remote operation is complete. In reality, one screen lock stops it. I check connection and unattended operation separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Software Walls and Fixes
&lt;/h2&gt;

&lt;h3&gt;
  
  
  A Backup Restarted a Service It Should Have Left Stopped
&lt;/h3&gt;

&lt;p&gt;A night backup restarted Open WebUI, which I had stopped on purpose. The old process stopped the whole stack and brought back the whole stack.&lt;/p&gt;

&lt;p&gt;I fixed it to stop and restart only the stacks that were running before the process. The lesson: backup success must include &lt;strong&gt;keeping stopped state&lt;/strong&gt;, not just "made the file".&lt;/p&gt;

&lt;h3&gt;
  
  
  Re-running Collection Broke a Good Report
&lt;/h3&gt;

&lt;p&gt;The unauthenticated GitHub API has a budget limit. I re-collected on the same day, and a narrow result overwrote the earlier detailed report.&lt;/p&gt;

&lt;p&gt;I changed the protection to calculate completeness from the content each time. Re-running does not always fix things. It can overwrite with a thin result.&lt;/p&gt;

&lt;h3&gt;
  
  
  When the Result Is "Unknown", I Do Not Retry
&lt;/h3&gt;

&lt;p&gt;In the dedicated GitHub test, the PR was merged on the GitHub side. But the agent-side result log could not confirm success, and stopped as "unknown".&lt;/p&gt;

&lt;p&gt;Here I did not retry. I checked the external state. Even if the external change succeeded, a failed result pickup looks unknown from the agent. Retrying and running it twice would have been more dangerous.&lt;/p&gt;

&lt;h3&gt;
  
  
  Approval Registration Error Is Unresolved
&lt;/h3&gt;

&lt;p&gt;In normal work, child session approval registration fails with a missing &lt;code&gt;operator.approvals&lt;/code&gt; error, and stops before Git commands run. As of the baseline date, this issue is unresolved.&lt;/p&gt;

&lt;p&gt;I cannot conclude it is a GitHub auth failure or a target repository permission issue. Permission on a different connection in the admin screen does not prove the same permission on the failed connection. Until I know the cause, I will only narrow down the target.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Notes
&lt;/h2&gt;

&lt;p&gt;I treat received information as untrusted. Even if the message board has a request, I do not treat it as execution permission.&lt;/p&gt;

&lt;p&gt;I check monitoring separately. "The entrance is visible", "the needed information is complete", and "notifications arrive" are separate checks. Exit code 0 from an analysis tool is not a pass for analysis ability.&lt;/p&gt;

&lt;p&gt;This post only covers checks in a limited scope. I have not passed the current health of all services, automatic development for any repository, or full automatic round trips between the three parties.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Summary
&lt;/h2&gt;

&lt;p&gt;By feel, I am about 80% there. This is not a measured success rate. It is my subjective view from the remaining items.&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Narrow down the approval registration error&lt;/li&gt;
&lt;li&gt;Accept the analysis VM ability&lt;/li&gt;
&lt;li&gt;Try a restore with the new backup&lt;/li&gt;
&lt;li&gt;Final check of unattended operation on the Mac mini&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;From a lab that starts to a lab that hands off. The remaining walls are now specific, so I will keep checking them one by one.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. References
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Build report (source for this post): &lt;a href="https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/home-lab-kurotchi-build-report-2026-11-08.ja.md" rel="noopener noreferrer"&gt;https://github.com/moruku36/home-ai-engineering-lab/blob/main/docs/home-lab-kurotchi-build-report-2026-11-08.ja.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Repository: &lt;a href="https://github.com/moruku36/home-ai-engineering-lab" rel="noopener noreferrer"&gt;https://github.com/moruku36/home-ai-engineering-lab&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;OpenClaw approval API definition (check on operator.approvals requirement): &lt;a href="https://github.com/openclaw/openclaw/blob/v2026.11.1/src/gateway/methods/core-descriptors.ts" rel="noopener noreferrer"&gt;https://github.com/openclaw/openclaw/blob/v2026.11.1/src/gateway/methods/core-descriptors.ts&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

</description>
      <category>opensource</category>
      <category>ai</category>
      <category>devops</category>
      <category>homelab</category>
    </item>
    <item>
      <title>I Verified Sakura AI Engine's Free Tier: 3 Models, 3 Tasks, Honest Results</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Fri, 06 Nov 2026 08:40:32 +0000</pubDate>
      <link>https://dev.to/moruku36/i-verified-sakura-ai-engines-free-tier-3-models-3-tasks-honest-results-1541</link>
      <guid>https://dev.to/moruku36/i-verified-sakura-ai-engines-free-tier-3-models-3-tasks-honest-results-1541</guid>
      <description>&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;When I evaluate an LLM API for work, two worries come first.&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Will I get billed without noticing while "just trying" the free tier?&lt;/li&gt;
&lt;li&gt;Will my input text be stored or used for training?&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Sakura AI Engine, a Japanese cloud service by Sakura Internet, answers both on its official pages. It states a zero data retention (ZDR) policy — inputs are neither stored nor used for training — and offers a free plan with 3,000 chat requests per month.&lt;/p&gt;

&lt;p&gt;On November 6, 2026, I ran three models from the free plan through the same three tasks in the web Playground, then checked every answer by eye and by independent calculation. Here is what I found.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What the free plan actually includes
&lt;/h2&gt;

&lt;p&gt;From the official product page:&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;Chat Completions: free up to 3,000 requests per month. Past that, requests are rate-limited — there is no automatic billing&lt;/li&gt;
&lt;li&gt;ZDR: input data is not stored and not used for training. Processing runs in data centers in Japan&lt;/li&gt;
&lt;li&gt;The Chat Completions catalog lists 10 models. One of them (a medical model) is outside the free tier, so 9 models are free to try&lt;/li&gt;
&lt;li&gt;RAG is outside the free tier and billed by usage (3 JPY per 100 chunks)&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  A common misconception
&lt;/h3&gt;

&lt;p&gt;A "free plan" does not mean everything is free. RAG and the medical model are excluded. Check the scope before you build on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. How I verified
&lt;/h2&gt;

&lt;p&gt;I used the Playground with a fresh conversation for each trial, one submission per model per task, and no retries.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Models: gpt-oss-120b / llm-jp-3.1-8x13b-instruct4 / preview/Kimi-K2.6
Task 1 (explanation): explain RAG for non-experts in 450 characters or fewer
Task 2 (code): a Python moving_average(values, window) function plus unittest cases.
               Expected values for [2,4,6,8,10] with window=4 and 5 had to be
               derived independently from the sublists
Task 3 (summary): summarize a municipal energy-saving text in exactly 3 bullets,
               without adding numbers that are not in the source
Settings: Playground defaults (temperature and token limits not verified)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I did not execute any generated code. I checked the test expectations with my own arithmetic, independently of the models. I did not measure time to first token or token counts.&lt;/p&gt;

&lt;h3&gt;
  
  
  A common misconception
&lt;/h3&gt;

&lt;p&gt;A model's own "reasoning" is not verification. In this run, one model confidently explained wrong expected values as if they were correct. Always cross-check with an independent method.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Results
&lt;/h2&gt;

&lt;h3&gt;
  
  
  4.1 Explanation (RAG)
&lt;/h3&gt;

&lt;p&gt;All three models separated the roles of retrieval and generation, and noted that having sources does not guarantee correctness.&lt;/p&gt;

&lt;p&gt;Kimi-K2.6 was concise and split its caveats into two kinds: the source documents themselves can be wrong, and the AI can misinterpret or miscombine them. gpt-oss-120b also covered how to check sources, although one claim — that real-time intake makes answers comprehensive — was stronger than the conditions justify.&lt;/p&gt;

&lt;p&gt;llm-jp-3.1-8x13b-instruct4 ignored the 450-character limit and answered in long paragraphs. The content was not far off, but the requested form and length were not followed.&lt;/p&gt;

&lt;h3&gt;
  
  
  4.2 Code generation
&lt;/h3&gt;

&lt;p&gt;The correct expected values, from my own calculation:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[2,4,6,8,10], window=4 -&amp;gt; [5, 7]   ((2+4+6+8)/4=5, (4+6+8+10)/4=7)
[2,4,6,8,10], window=5 -&amp;gt; [6]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;gpt-oss-120b and Kimi-K2.6 produced functions, tests, and expected values that all matched the independent calculation. Kimi-K2.6 provided 10 tests, including one that the input list is not modified.&lt;/p&gt;

&lt;p&gt;llm-jp-3.1-8x13b-instruct4 wrote a function that visually matched the spec, but several expected values in its tests were wrong:&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;window=4 expected &lt;a&gt;5, 6, 7, 8, 9&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;window=5 expected [4, 6, 8, 10], and [6, 8, 10] on another line (correct: [6])&lt;/li&gt;
&lt;li&gt;[2,4,6] with window=4 expected &lt;a&gt;4, 6&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Its explanation then justified the wrong values, and the input-immutability test was missing&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Since I did not execute the code, this only establishes whether the expected values were right — not whether the code runs.&lt;/p&gt;

&lt;h3&gt;
  
  
  4.3 Summarization
&lt;/h3&gt;

&lt;p&gt;I scored the summaries against nine elements of the source text: 20 facilities in 2024, 1.2M kWh total with the 55/30/15 split, LED and air-conditioning measures, a 12% year-over-year decrease, the hot-day room-temperature problem, continued measurement, the 24M JPY cost, payback period undetermined due to electricity price fluctuation, and the caution against generalizing single-year numbers.&lt;/p&gt;

&lt;p&gt;Kimi-K2.6 returned exactly three bullets, kept all nine elements, and added no numbers of its own.&lt;/p&gt;

&lt;p&gt;gpt-oss-120b kept all nine elements but added figures that are not in the source: 660k / 360k / 180k kWh. The arithmetic behind them is correct, but the instruction was to add nothing.&lt;/p&gt;

&lt;p&gt;llm-jp-3.1-8x13b-instruct4 answered in a single paragraph instead of three bullets and dropped a few points, including the hot-day condition.&lt;/p&gt;

&lt;h3&gt;
  
  
  A common misconception
&lt;/h3&gt;

&lt;p&gt;Each model ran each task exactly once. These results are not a ranking. Read them as concrete examples of each model's habits.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What the earlier round showed
&lt;/h2&gt;

&lt;p&gt;In past records from an earlier round on the same day (9 models × 3 tasks, 27 trials), similar habits appeared:&lt;/p&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;One model reversed "do not generalize" into "generalize" in its summary&lt;/li&gt;
&lt;li&gt;One model swapped the facility ratios&lt;/li&gt;
&lt;li&gt;One small model's generated tests had every expected value wrong (the only execution evidence in those records is a single input run of an older Qwen function)&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Combining both rounds, the weak point is not fluency. It is &lt;strong&gt;faithfulness&lt;/strong&gt; to numbers and meaning. Expected values and summaries only become usable after an independent check.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Limitations
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;I have not verified the APIs yet. OpenAI-compatible and Anthropic-compatible endpoint checks, and Claude Code integration, are still to come&lt;/li&gt;
&lt;li&gt;I did not execute the generated code, so I cannot claim it works or that any test passes&lt;/li&gt;
&lt;li&gt;I did not measure TTFT or token counts, and I am not comparing speed&lt;/li&gt;
&lt;li&gt;After the trials, the usage display showed 37 requests and 0 JPY. That is 7 more than the 9 submissions I recorded, so treat the 0 JPY as a display observation, not a confirmed final bill&lt;/li&gt;
&lt;li&gt;One tested model is a preview offering and may be discontinued or changed without notice&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  7. Summary
&lt;/h2&gt;

&lt;p&gt;Within the free plan, you can try 9 models with no billing risk, and the ZDR policy is stated in writing. As an evaluation entry point, the conditions are solid.&lt;/p&gt;

&lt;p&gt;Quality, however, varies by task and by model. In this run, skipping the cross-check on expected values and summary details would have carried errors straight into real work.&lt;/p&gt;

&lt;p&gt;Next, I will verify the API endpoints and the Claude Code integration, and update this post with the results.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sakura AI Engine official site (free plan terms, model list, and the "input data is not used for training or stored" policy): &lt;a href="https://ai.sakura.ad.jp/sakura-ai/ai-engine/" rel="noopener noreferrer"&gt;https://ai.sakura.ad.jp/sakura-ai/ai-engine/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Zennfes Autumn 2026, Sakura division (the contest this post is entered in): &lt;a href="https://zenn.dev/contests/zennfes-autumn-2026-sakura" rel="noopener noreferrer"&gt;https://zenn.dev/contests/zennfes-autumn-2026-sakura&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Sakura Internet official announcement (2026-11-02): &lt;a href="https://www.sakura.ad.jp/corporate/information/announcements/2026/11/02/1968226190/" rel="noopener noreferrer"&gt;https://www.sakura.ad.jp/corporate/information/announcements/2026/11/02/1968226190/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>japan</category>
      <category>testing</category>
    </item>
    <item>
      <title>What Changed in Google Antigravity's November Update: Remote Agents, Voice Mode, and a Native Jupyter Viewer</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Wed, 04 Nov 2026 08:34:49 +0000</pubDate>
      <link>https://dev.to/moruku36/what-changed-in-google-antigravitys-november-update-remote-agents-voice-mode-and-a-native-1ph9</link>
      <guid>https://dev.to/moruku36/what-changed-in-google-antigravitys-november-update-remote-agents-voice-mode-and-a-native-1ph9</guid>
      <description>&lt;p&gt;On November 3, 2026, Google Antigravity shipped an update that moves agent work into the cloud — and lets you talk to it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The problem
&lt;/h2&gt;

&lt;p&gt;Until now, an agent session lived and died with your laptop. Close the lid, and the work stopped. A permission prompt waited for your click.&lt;/p&gt;

&lt;p&gt;This release goes after both.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. What shipped
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Remote agents&lt;/strong&gt;: conversations run in the cloud, even with your laptop closed (Google AI Pro and Ultra, rolling out)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Voice mode&lt;/strong&gt;: talk to the agent via Gemini Live, and answer permission prompts out loud (rolling out)&lt;/li&gt;
&lt;li&gt;A native Jupyter notebook viewer&lt;/li&gt;
&lt;li&gt;A redesigned Automations page, plus downloads and history in the built-in browser&lt;/li&gt;
&lt;li&gt;Partner plugins in the Marketplace: Canva, Figma, Linear, Notion, Stripe, Supabase, Vercel&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Source: the official &lt;a href="https://antigravity.google/docs/changelog" rel="noopener noreferrer"&gt;changelog&lt;/a&gt; entry for November 3, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Remote agents: work that survives a closed laptop
&lt;/h2&gt;

&lt;p&gt;Conversations in a cloud project now run in an isolated, Google-managed environment — not on your machine. Close the browser or sleep the laptop; long tasks keep running.&lt;/p&gt;

&lt;p&gt;You feed work through &lt;a href="https://antigravity.google/docs/remote-agents" rel="noopener noreferrer"&gt;resources&lt;/a&gt;: GitHub repositories, Google Drive files, or uploads. Start from the app, the CLI, or antigravity.google.com/remote. A personal account on Google AI Pro or Ultra is required.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Common misconception:&lt;/strong&gt; this is not remote control of your own PC. That is the separate Remote Control feature, and it needs your machine on and online. Remote agents fit repository-scoped work. Tasks that depend on uncommitted local changes or a local dev server are a poor fit.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Voice mode: talk instead of type
&lt;/h2&gt;

&lt;p&gt;Voice mode runs on &lt;a href="https://antigravity.google/docs/voice-mode" rel="noopener noreferrer"&gt;Gemini Live&lt;/a&gt;. Click &lt;strong&gt;Start Voice mode&lt;/strong&gt; in an empty message box, pick one of nine voices, and talk.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhqvcgq9zn4qynkfvivdl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhqvcgq9zn4qynkfvivdl.png" alt="Choosing a voice in voice mode (from the official docs)" width="800" height="833"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fey0edbndr1qblinyye3d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fey0edbndr1qblinyye3d.png" alt="The voice mode call panel (from the official docs)" width="800" height="292"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can hand off a task out loud, steer it while it runs, and answer permission prompts by voice. Its work still appears in the conversation to read along.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Common misconception:&lt;/strong&gt; this is not dictation. Dictation turns speech into text. Here the conversation itself is spoken, and a transcript is saved when it ends.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Jupyter viewer and Automations
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;.ipynb&lt;/code&gt; files now open inside the app, with code cells, Markdown, tables, images, and outputs rendered. It is a viewer only — no built-in way to run cells.&lt;/p&gt;

&lt;p&gt;The Automations page now groups items into Scheduled, Always on, and Paused, with Next run and Last run times and a full-page creation form.&lt;/p&gt;

&lt;p&gt;The built-in browser improved too: downloads save without prompts, history powers address-bar suggestions, and syntax highlighting now loads on demand across 173 languages.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Plugins and a step into science
&lt;/h2&gt;

&lt;p&gt;The Marketplace added partner plugins: Canva, Figma, Linear, Notion, Stripe, Supabase, and Vercel.&lt;/p&gt;

&lt;p&gt;The same day, DeepMind released &lt;a href="https://deepmind.google/blog/agentic-cheminformatics-with-google-antigravity/" rel="noopener noreferrer"&gt;Cheminformatics Skills&lt;/a&gt; through the Science plugin. Built on RDKit, with ChEMBL and PubChem connectors, they search compounds, run matched molecular pair analysis, and propose new molecular designs.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Plans
&lt;/h2&gt;

&lt;p&gt;Antigravity has no separate price. Your Google AI plan sets the limits (&lt;a href="https://antigravity.google/docs/plans" rel="noopener noreferrer"&gt;Plans&lt;/a&gt;, &lt;a href="https://antigravity.google/pricing" rel="noopener noreferrer"&gt;Pricing&lt;/a&gt;). Prices are US prices.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;Price&lt;/th&gt;
&lt;th&gt;Quota&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;td&gt;$0&lt;/td&gt;
&lt;td&gt;A quota refreshed weekly. Gemini models. Local-first&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google AI Pro&lt;/td&gt;
&lt;td&gt;$19.99/mo&lt;/td&gt;
&lt;td&gt;Refreshes every five hours, up to a weekly limit. Claude Sonnet 5.5 / Opus 5.5 (non-trial). Remote agents&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google AI Ultra&lt;/td&gt;
&lt;td&gt;$99.99 / $199.99/mo&lt;/td&gt;
&lt;td&gt;5x / 20x the Pro quota&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Quota scales with how much work the agent does. Google does not publish exact numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Caveats
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Both headline features are rolling out gradually. An update does not guarantee you will see them yet.&lt;/li&gt;
&lt;li&gt;Remote agents need a personal account on a paid plan. Some plugin features are not yet available for business accounts.&lt;/li&gt;
&lt;li&gt;Jupyter support is view-only.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  9. Wrap-up
&lt;/h2&gt;

&lt;p&gt;Execution is moving off your machine. Input is moving off the keyboard. Antigravity is shifting from a tool you use while seated to an agent you hand work to.&lt;/p&gt;

</description>
      <category>google</category>
      <category>gemini</category>
      <category>ai</category>
      <category>agents</category>
    </item>
    <item>
      <title>Choosing a Database in the AI Coding Era: Supabase, Neon, MongoDB, Upstash, and Convex by Use Case</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Tue, 03 Nov 2026 09:06:33 +0000</pubDate>
      <link>https://dev.to/moruku36/choosing-a-database-in-the-ai-coding-era-supabase-neon-mongodb-upstash-and-convex-by-use-case-49h4</link>
      <guid>https://dev.to/moruku36/choosing-a-database-in-the-ai-coding-era-supabase-neon-mongodb-upstash-and-convex-by-use-case-49h4</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdi8r07vwpmtsed8sqhev.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdi8r07vwpmtsed8sqhev.png" alt="Article header image" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;AI writes most of the code now, but you still choose the database. I focus on how fast I can try things for free, types and docs that AI handles well, and whether I buy auth and related features or build them myself.&lt;/p&gt;

&lt;p&gt;To be clear, these five are not the same kind of thing. Supabase and Convex are BaaS types that include a DB, Neon is serverless Postgres at its core with surrounding features, MongoDB Atlas is the document DB itself, and Upstash Redis is a helper for cache and rate limiting. I compare them here by what I want to build.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Supabase
&lt;/h2&gt;

&lt;p&gt;Supabase is a BaaS with Postgres + Auth + Storage + Realtime + Edge Functions. It is open source and I can self-host.&lt;/p&gt;

&lt;p&gt;Free is $0 with DB 500MB, files 1GB, auth 50,000 MAU, and up to 2 active projects. It fits me when I want to launch a normal web app with auth as fast as possible. Pro is $25/month with DB 8GB, auth 100,000 MAU, and daily backups.&lt;/p&gt;

&lt;p&gt;Reference: &lt;a href="https://supabase.com/pricing" rel="noopener noreferrer"&gt;https://supabase.com/pricing&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Neon
&lt;/h2&gt;

&lt;p&gt;Neon is serverless Postgres at its core, now including Managed Better Auth, Object Storage, Functions, Realtime (Beta), and AI Gateway. Its strengths are branch-based DB copies, autoscaling, and extensions like pgvector.&lt;/p&gt;

&lt;p&gt;Free is $0 with no time limit and no card required, 100 projects, 100 CU-hours/month per project, and storage 1GB/project. It fits me when I want to reuse my SQL and Postgres assets and spin up many preview environments. Launch is usage-based, with an official guide of $15/month and $0.106/CU-hour.&lt;/p&gt;

&lt;p&gt;Reference: &lt;a href="https://neon.com/pricing" rel="noopener noreferrer"&gt;https://neon.com/pricing&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. MongoDB Atlas
&lt;/h2&gt;

&lt;p&gt;MongoDB Atlas centers on a document DB, and I build auth and the API layer myself or combine it with App Services. It fits me when the data shape is still changing and I want document flexibility.&lt;/p&gt;

&lt;p&gt;Free M0 is Free forever with 512MB and shared vCPU/RAM. I can consider Atlas Search and Vector Search on the same base for search use. Flex is $8-$30/month, and Dedicated starts at M10 from $0.08/hour.&lt;/p&gt;

&lt;p&gt;Reference: &lt;a href="https://www.mongodb.com/pricing" rel="noopener noreferrer"&gt;https://www.mongodb.com/pricing&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Upstash Redis
&lt;/h2&gt;

&lt;p&gt;Upstash Redis is serverless Redis, a helper for cache, sessions, and rate limiting. It fits me when I keep my main DB and add it alongside to improve speed and control.&lt;/p&gt;

&lt;p&gt;Free is $0 with 250MB, 500K commands per month, and 1 free DB. Per the official FAQ, a POST request alone issues a free Redis instantly with no signup, designed for AI agents to use right away. Usage is $0.2/100K commands, and fixed plans start at $10/month.&lt;/p&gt;

&lt;p&gt;Reference: &lt;a href="https://upstash.com/pricing" rel="noopener noreferrer"&gt;https://upstash.com/pricing&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Convex
&lt;/h2&gt;

&lt;p&gt;Convex is a reactive backend where I write queries, mutations, and actions in TypeScript. The DB is document-type and not SQL, with built-in realtime sync, file storage, scheduled execution, auth integration, and vector search. It fits me when I want realtime sync with React and TypeScript.&lt;/p&gt;

&lt;p&gt;Free/Starter is $0 + usage for overages, with 1 million function calls per month, DB 0.5GB, files 1GB, and tokens for Chef AI app generation included. Professional is $25/developer/month with 25 million function calls per month and DB 50GB. It is open source and I can self-host.&lt;/p&gt;

&lt;p&gt;Reference: &lt;a href="https://www.convex.dev/pricing" rel="noopener noreferrer"&gt;https://www.convex.dev/pricing&lt;/a&gt; / &lt;a href="https://docs.convex.dev/production/state/limits" rel="noopener noreferrer"&gt;https://docs.convex.dev/production/state/limits&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  7. How to Choose: Decide by What You Build
&lt;/h2&gt;

&lt;p&gt;It is easier to work backward from what I build. For a normal web app with auth as fast as possible, Supabase; to reuse SQL and Postgres assets and mass-produce preview environments, Neon. For unsettled data shapes, MongoDB Atlas; to add cache and rate limiting to a separate main DB, Upstash Redis; for realtime sync with React and TypeScript, Convex.&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Flowchart
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpugqr8wehf3532blripk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpugqr8wehf3532blripk.png" alt="DB selection flowchart by what you build" width="798" height="203"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For letting AI write it, I decide first whether I want Postgres types, document flexibility, or bundled surrounding features. That reduces rework. If requirements change, I just change the combination; I do not need to narrow it to one from the start.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Comparison Table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Data model&lt;/th&gt;
&lt;th&gt;Auth&lt;/th&gt;
&lt;th&gt;Realtime&lt;/th&gt;
&lt;th&gt;Free&lt;/th&gt;
&lt;th&gt;Paid entry&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Supabase&lt;/td&gt;
&lt;td&gt;BaaS&lt;/td&gt;
&lt;td&gt;Postgres&lt;/td&gt;
&lt;td&gt;Built-in Auth&lt;/td&gt;
&lt;td&gt;Realtime available&lt;/td&gt;
&lt;td&gt;$0 with DB 500MB, files 1GB, auth 50,000 MAU, up to 2 projects&lt;/td&gt;
&lt;td&gt;Pro $25/month with DB 8GB, auth 100,000 MAU, daily backups&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Neon&lt;/td&gt;
&lt;td&gt;Serverless Postgres + surrounding features&lt;/td&gt;
&lt;td&gt;Postgres&lt;/td&gt;
&lt;td&gt;Includes Managed Better Auth&lt;/td&gt;
&lt;td&gt;Includes Realtime (Beta)&lt;/td&gt;
&lt;td&gt;$0, no time limit and no card required, 100 projects, 100 CU-hours/month per project, storage 1GB/project&lt;/td&gt;
&lt;td&gt;Launch is usage-based (official guide $15/month, $0.106/CU-hour)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MongoDB Atlas&lt;/td&gt;
&lt;td&gt;Document DB&lt;/td&gt;
&lt;td&gt;Document-type&lt;/td&gt;
&lt;td&gt;Self-built or combined with App Services&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;M0 free with 512MB, shared vCPU/RAM&lt;/td&gt;
&lt;td&gt;Flex $8-$30/month, Dedicated M10 from $0.08/hour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Upstash Redis&lt;/td&gt;
&lt;td&gt;Serverless Redis, helper&lt;/td&gt;
&lt;td&gt;Redis&lt;/td&gt;
&lt;td&gt;Match to main system&lt;/td&gt;
&lt;td&gt;Used for cache and similar&lt;/td&gt;
&lt;td&gt;$0 with 250MB, 500K commands/month, 1 free DB&lt;/td&gt;
&lt;td&gt;Usage $0.2/100K commands, fixed from $10/month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Convex&lt;/td&gt;
&lt;td&gt;Reactive backend&lt;/td&gt;
&lt;td&gt;Document-type, not SQL&lt;/td&gt;
&lt;td&gt;Built-in auth integration&lt;/td&gt;
&lt;td&gt;Built-in realtime sync&lt;/td&gt;
&lt;td&gt;$0 + usage with 1M functions/month, DB 0.5GB, files 1GB&lt;/td&gt;
&lt;td&gt;Professional $25/developer/month with 25M functions/month, DB 50GB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  10. Caveats
&lt;/h2&gt;

&lt;p&gt;Supabase free pauses after 1 week with no access, so I check fit for left-alone test projects. Upstash is not a replacement for a main DB; I use it together with a main DB. Convex is not SQL, so I compare it with other options when I want to reuse existing SQL assets. Pricing and limits change, so I always confirm on the official sites.&lt;/p&gt;

&lt;h2&gt;
  
  
  11. Summary
&lt;/h2&gt;

&lt;p&gt;The options narrow naturally based on whether I want BaaS, want to use Postgres fully, or prioritize changing shapes. If I need a helper, I add Upstash; if realtime sync is core, I consider Convex. The shortcut is to let AI touch the free tiers first, then decide by surrounding features and operational feel.&lt;/p&gt;

&lt;h2&gt;
  
  
  12. Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://supabase.com/pricing" rel="noopener noreferrer"&gt;https://supabase.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://neon.com/pricing" rel="noopener noreferrer"&gt;https://neon.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.mongodb.com/pricing" rel="noopener noreferrer"&gt;https://www.mongodb.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://upstash.com/pricing" rel="noopener noreferrer"&gt;https://upstash.com/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.convex.dev/pricing" rel="noopener noreferrer"&gt;https://www.convex.dev/pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.convex.dev/production/state/limits" rel="noopener noreferrer"&gt;https://docs.convex.dev/production/state/limits&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;P.S. I wrote this article together with Muse (Fuwatchi), my AI agent. If you want to try Muse, I would appreciate it if you enter invite code EOA1TR. &lt;a href="https://muse.ai/join%60%60" rel="noopener noreferrer"&gt;https://muse.ai/join``&lt;/a&gt;&lt;/p&gt;

</description>
      <category>database</category>
      <category>postgres</category>
      <category>supabase</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Joining Meta's Global Hackathon from Japan</title>
      <dc:creator>SeaOtter ( Kentaro Mori )</dc:creator>
      <pubDate>Sat, 31 Oct 2026 08:35:55 +0000</pubDate>
      <link>https://dev.to/moruku36/joining-metas-global-hackathon-from-japan-3l31</link>
      <guid>https://dev.to/moruku36/joining-metas-global-hackathon-from-japan-3l31</guid>
      <description>&lt;p&gt;Running the same week as developers around the world has been much more fun than I expected. These are my notes from the first half of joining Meta's global AI hackathon solo from Japan.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Introduction
&lt;/h2&gt;

&lt;p&gt;The event is the Meta Global AI Developer Hackathon. It's fully online, running October 26 to November 4 (ET), with $1M in total prizes. I'm joining solo from Japan.&lt;/p&gt;

&lt;p&gt;But I'm not exactly alone. I'm building together with my AI agent partner, which makes this a slightly unusual way to join.&lt;/p&gt;

&lt;p&gt;During the event, developers all over the world are building at the same time. Just feeling that energy makes it worth joining.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Feeling Connected to the World
&lt;/h2&gt;

&lt;p&gt;What I enjoy most is the feeling of being connected to the world. Participants are in all different time zones, so while East Asia is active during the day, the US and European chats move forward while I'm asleep.&lt;/p&gt;

&lt;p&gt;When I wake up in the morning and open Discord, someone's project has moved forward overnight, or a discussion has heated up. To be honest, I haven't been able to take part in Discord much myself. Just watching it is fun.&lt;/p&gt;

&lt;p&gt;The projects are so varied. Some people are making escape games from photos of a room, others are automating listing work for older adults. Seeing everyone's urge to build lined up at once is inspiring just to watch. It naturally pushes me to build something too. Even though our countries and languages are different, I feel the passion for making things is the same everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Official Sessions and Office Hours
&lt;/h2&gt;

&lt;p&gt;At the kickoff, the event flow and tooling were introduced all at once to participants gathered from around the world. Hands-on live sessions are also being streamed.&lt;/p&gt;

&lt;p&gt;In the hands-on session, what stuck with me was the idea of building a verification layer into agents. The idea is to embed checks into the tools in a way that can't be bypassed.&lt;/p&gt;

&lt;p&gt;Personally, I'm most grateful for the office hours. There's a space where I can ask Meta engineers questions directly, so even though it's a global event, I don't feel any distance. Having a place like this where I can ask questions lets me reach further than I could by learning on my own.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. My Project
&lt;/h2&gt;

&lt;p&gt;My project is Trifecta Checker. It reads an AI agent's configuration and checks whether it forms a risky combination.&lt;/p&gt;

&lt;p&gt;I don't leave the judgment to the mood of an LLM; I use a deterministic rule engine instead. My commitment is that the same input always gives the same result.&lt;/p&gt;

&lt;p&gt;Your guide is the character Trafica. The public demo is here: &lt;a href="https://meta-global-ai-hackathon-trifecta-c.vercel.app/" rel="noopener noreferrer"&gt;https://meta-global-ai-hackathon-trifecta-c.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6kuqblehlnmogj98luz9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6kuqblehlnmogj98luz9.png" alt="How Trifecta Checker works" width="799" height="109"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Note that this judgment is just a heuristic guide, and does not prove safety.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Wrap-up
&lt;/h2&gt;

&lt;p&gt;Honestly, I'm not thinking much about the results. We build something interesting and show each other saying, "I made this." That alone makes this a fun event.&lt;/p&gt;

&lt;p&gt;The demo is live now, so please try it out if you'd like. If you try it, I'd love to hear in the comments what worked and what didn't — that feedback goes straight into the next iteration. The submission deadline is 11:00 on November 5 JST, and all I have left is to finish the demo video and submission. I'll enjoy running through the second half to the end.&lt;/p&gt;

&lt;p&gt;The official event page is here: &lt;a href="https://cerebralvalley.ai/e/meta-ai-developer-hackathon" rel="noopener noreferrer"&gt;https://cerebralvalley.ai/e/meta-ai-developer-hackathon&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  P.S.
&lt;/h2&gt;

&lt;p&gt;I built this with Muse as my main agent, together with my AI partner Fuwatchi (Muse). The API connectivity and overall usability have been great. If you'd like to try it, my invite code is EOA1TR: &lt;a href="https://muse.ai/join" rel="noopener noreferrer"&gt;https://muse.ai/join&lt;/a&gt;&lt;/p&gt;

</description>
      <category>metaai</category>
      <category>hackathon</category>
      <category>ai</category>
      <category>security</category>
    </item>
  </channel>
</rss>
