On Nov 11, 2026, two posts related to the AI Agent toolchain appeared on the V2EX forum: milletcode announced it had open-sourced its internally used, already-commercial multi-agent parallel orchestration platform, while another developer released the Xtaff Browser Chrome extension, which uses the MCP protocol to let users' own Agents directly operate the Chrome browser they use day to day. The two threads emerged on the same day, pointing respectively to the open-sourcing of the Agent orchestration layer and the opening up of the browser entry point.
milletcode open-sources multi-agent orchestration platform
According to the V2EX post, milletcode has open-sourced its multi-agent orchestration platform. The project homepage is milletcode.com, and the code is hosted in the milletcode/milletcode repository on GitHub. The poster said the product had been used internally for some time and was already formally commercialized, and that the open-sourcing was intended to "let more people feel the nuclear-blast power of multi-agent parallel work." The post did not disclose the specific technical architecture, the open-source license, or commercial customer information.
Xtaff Browser extension: opening browser capabilities via MCP
In the other thread, the developer shared a comparison of mainstream Browser Use approaches and released Xtaff Browser. The tool provides browser-operation capabilities as a Chrome extension, then exposes those capabilities to users' own Agents through MCP. The workflow has three steps: install the Xtaff Browser extension in Chrome, configure the corresponding MCP for the Agent, and start letting the Agent operate the browser.
The developer said this approach reuses the current browser environment without launching a separate Chrome instance, making it suitable for browsing forums, reading web page information, or operating logged-in business systems. In addition, a site Playbook can record the operation flow for a specific website so the Agent can reuse it later; session caching can save the session context during operations to make it easier to continue tasks. The developer stressed that the extension currently does not send requests to external services, and all related data is stored locally in the browser.
Comparison of three technical routes for browser operation
The developer compared the three mainstream approaches for letting Agents operate browsers:
| Technical route | Advantages | Limitations |
|---|---|---|
| CDP protocol (Playwright/Selenium) | Mature technology, well-developed ecosystem | A separately launched Chrome lacks the account login state of the everyday browser; taking over a Chrome already in use requires configuring remote debugging parameters in advance, which is not natural to use |
| Browser extension | No need to modify Chrome launch parameters; can directly reuse the login state of the user's everyday browser; better suited to personal Agent scenarios | Some Browser Use products from Anthropic and OpenAI usually serve only their own Agents and are not open to third-party integration; the usability of some products still needs improvement — the developer said a test of WorkBuddy did not run properly |
| WebContentsView + JS injection | High flexibility; you can control the browser container and script execution logic yourself | You need to maintain the relevant capabilities yourself, and it likewise faces the problem of not being able to directly reuse the user's everyday account session |
The developer said that after weighing the overall experience, they lean toward the browser extension route, and that Xtaff Browser was built to solve the question of "whether your own Agent can control everyday Chrome like the big vendors' Agents do."
The project is still being improved, and the developer welcomes discussion and feedback.
What to watch
Both threads come from V2EX sharing posts; the maturity of the products, the response of the open-source community, and the actual usability of the extension remain to be seen. The details of milletcode's open-source license and platform architecture, Xtaff Browser's compatibility with more Agent frameworks, and whether big-vendor browser extensions move toward openness will be notable milestones in the evolution of the Agent toolchain.