Urgent.News

What's breaking now, across thousands of outlets.

AI

停掉控制面之后,AI 任务还在跑:我们为什么把它拆成三层

用一个界面对着某台机器上的某个终端窗口,是大多数人开始用 AI 写代码的方式。任务变多之后会出现三个具体问题:任务分散在多台机器上、每个任务需要独立且可丢弃的环境、长任务不能因为浏览器关了或者界面断了就死掉。 这篇讲 TaskHandoff 在这三个问题上做的架构选择:为什么控制面和执行面要拆开,状态到底归谁管,以及由此付出的代价。 问题:任务一多,你就开始手动当调度器 假设你手上有三台机器:一台笔记本、一台常开的家用服务器、一台公司内网主机。你在它们上面分别跑 Codex 或 OpenCode。于是你每天在做这些事: 记得哪台机器上有哪个仓库、哪个分支、哪个 worktree; 手动把环境装好,或者忍受容器里从零开始装工具; 反复切 SSH 窗口看任务进度,因为任务只在那个终端的上下文里存在; 关掉笔记本之后,不知道家用服务器上的任务到底还在不在跑。…

Original Chinese Read in English

The article discusses an architecture choice made by TaskHandoff to address three specific problems that arise as AI tasks become more numerous: task distribution across multiple machines, each task requiring its own independent and disposable environment, and long-running tasks not being killed when the browser is closed or the interface is disconnected.

The solution involves separating the control plane from the execution plane. The control plane is responsible for managing node lists, instance dashboards, AI session views, and chat credentials and message routing. The Node Agent manages node local configurations, runtime resources, directory lists, and instance lifecycles. Controlled instances contain the actual work area, applications, AI sessions, and triggers, and can run independently.

The key point is that instance lifecycles belong to the Node Agent, so stopping or restarting the control plane does not affect the instances running on the node. The AI session maintains its conversation state, while the control plane handles credentials, bindings, command parsing, and routing. This design prevents the control plane from stopping Docker instances when restarted, and allows AI sessions to continue running even if the browser is closed or the interface is disconnected.

The article provides a step-by-step explanation of how the system works, including how to use the browser/desktop/mobile interfaces, manage nodes and instances, and handle long-running tasks across multiple machines and devices.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 2 other outlets

Read the original at dev.to →

More in AI

Automated Red Teaming for AI Agents

Your agent refused. Politely. Correctly. Then it refunded $240 on an order that wasn't the user's. No test failed. The transcript looked perfect. The bug only showed up in the tool call.

  • Automated red teaming tests AI agents interacting with tools.
  • Focus on actions, not language, to catch slip-through bugs.

More from Wednesday 14 October →