EAIDaily — 2026-11-01 (English Edition)
Coverage window: 2026-10-31 → 2026-11-01 (Beijing time) Focus: AI Coding · Embodied Intelligence Method: AI HOT selected feed (5 items/24h) + 9 WebSearch/WebFetch verification passes + direct source fetch (Agility Robotics IR, InfoQ, The Information front page, White House proclamation, CAICT/Xinhua standard text)
How to read this issue. Two dates collide today. On the AI-coding side the story is unit economics and attention — no new frontier model shipped, but OpenAI quietly withdrew the only volume discount it ever sold, DeepSeek open-sourced an architecture whose entire premise is that human attention, not model capability, is now the bottleneck, and a Claude Code default was measured burning ~16% of a user’s bill on three-word status strings. On the embodied side the two capital ledgers diverged sharply in public: Agility Robotics priced its uniqueness at ~$465M while 61% of its SPAC trust walked away, and Chinese primary-market embodied funding halved in deal count in a single month — on the same day that China’s first embodied-intelligence dataset quality standard took legal effect and a US Section 232 clock started running on robot imports.
1. DeepSeek open-sources dsh-superagent-prototype: the agent stops waiting to be asked
What happened. On 31 October at 20:05 Beijing time, the DeepSeek Harness team pushed a single commit to a new repo under the official deepseek-ai GitHub org — 216 files, +37,068 lines, MIT-licensed — named dsh-superagent-prototype. It is not a model. It is an architecture proposal, plus working prototype code, for redesigning how an agent relates to a human.
The diagnosis is stated plainly: as models get stronger, the constraint moves from “how much code can the model write” to “how many concurrent threads can one human supervise” — DeepSeek’s own observation is that a person can only actively track 3–5 sessions at once. The design principle is therefore inverted from most agent UX: minimise human attention consumed per unit of value delivered. The agent is instructed to interrupt only when a result is usable, a decision genuinely requires a human, or the task cannot proceed.
Architecture, as published:
| Layer | Function |
|---|---|
| Source | Abstracts work entry points (GitHub, Feishu/Lark) as event streams; maintains read position, identifies event origin, routes messages into the correct work thread |
| Eval | Decides whether an inbound message should become work, based on sender identity, rules, and existing task state |
| Ticket | The durable unit of work — decoupled from any single agent session; states include awaiting execution, working, awaiting external event, awaiting human answer, awaiting review, blocked, failed |
| Mandate | The authorisation record: why this task is permitted, its scope, the rule version, and the basis for the grant |
| Assignment → Executor | Each ticket gets its own session and working directory; the main session only receives events and dispatches |
Mechanism details worth noting:
- Speculative execution — the agent can begin background work on something it merely suspects needs doing.
- Session-independent lifecycle — a ticket can close its current execution phase and resume later when new feedback arrives on the subscribed thread, instead of being recreated.
- Background limits — routine background work continues at most 30 minutes past a turn boundary, then the shell task is terminated and state recorded; sub-agents have separate lifecycle rules. Concurrency reserves extra scheduling slots for human messages so a human can always intervene.
- Proactive admission is gated, not free. Three modes —
off,observe(evaluate and log the judgement but do not act),auto(act when configured rules are met). Default isobserve. Chat content, comments and cited documents are explicitly allowed to inform a judgement but are not allowed to modify access rights or mandate scope. - Reported measurement in a simulated multi-task environment: median task completion 12.4 min, p95 15.7 min, ahead of the single-session baseline tested.
Why it matters.
- It names the bottleneck and it isn’t the model. The field has spent two years optimising tokens, context and tool calls. DeepSeek is arguing the scarce resource is now the operator’s attention span, and that the correct engineering response is a notification budget, not a bigger context window.
- The unit of organisation changes from conversation to ticket. This is the single most consequential design move. Once a task outlives a session, PR review feedback, CI failures and follow-up constraints can resume the same work with the same context — which is exactly the failure mode every current coding agent has.
- Autonomy is shipped with an explicit permission object.
Mandateis an attempt to make “why was this allowed” a machine-checkable record — the same structural move as the runtime permission layers published over the past two weeks (Anthropicsandbox-runtime, Google Agent Compute Engine, NVIDIA OpenShell), applied one level up at the task-authorisation layer. - DeepSeek states the prototype was substantially built by coding agents. AI-built infrastructure for managing AI is a claim that will get tested, but it is being put forward openly.
Caveat, stated by DeepSeek itself: the Executor session runs commands as the deploying OS user, and a working directory plus command restrictions is not full security isolation. The repo is positioned as architecture research for controlled environments, not a production-grade enterprise agent. The 12.4/15.7-minute figures are DeepSeek’s own simulated-environment measurements against an unnamed single-session baseline.
2. OpenAI reprices Pro: the only volume discount it ever sold is being withdrawn
What happened. Effective 30 October 2026, OpenAI cut the included usage on the $200 Pro tier:
| Change | Before | After |
|---|---|---|
| ChatGPT Work + Codex allowance (Pro 200) | 20× the Plus allowance | 10× |
| GPT-6 Pro messages in Chat | 200/week | 100/week |
| Price | $200/mo | unchanged |
| One-time credit grant | — | 62,500 credits (≈$2,500), expires 31 Dec 2026 |
Simultaneously OpenAI introduced Pro 500 at $500/mo: 25× the Plus allowance plus Ultrafast, up to ~8× generation speed (≈300 output tok/s in Codex). Ultrafast is not free — on API it is priced at 6× standard: GPT-6.1 Sol $12/$60 per Mtok vs $2/$10; GPT-6 Astra $60/$300 vs $10/$50. On Pro 500 it draws down the included allowance at 8× the standard rate, and from purchased credits at 6×. The 5-hour rolling limit is not returning.
The structural finding, which the pricing page does not show: divide price by allowance multiple and four of the five rungs land on exactly $20 per unit (Plus ×1/$20, Pro 100 ×10/$100, Pro 200-after ×10/$200, Pro 500 ×25/$500). The fifth — a Pro 200 seat bought before DevDay on 29 September — is the only plan OpenAI has ever sold at a volume discount, and it is the one being retired. Grandfathered holders keep 20× through 29 October, then drop to 10× at the same price, with the expiring credit grant as a nine-week cushion.
Also in scope: dots (always-on GPT-6 Astra agents with their own cloud computer) are now included on Pro and their traffic does not draw on the ChatGPT allowance — but the eligible-market list excludes the EEA, Switzerland and the UK with no published rollout date. Business Premium reportedly has them in all supported regions. Separately, GPT-6.1 Astra is reported delayed on safety grounds.
Why it matters.
- Unit price is now identical everywhere, so competition moves off price. When every rung costs $20 per allowance unit, buyers must choose on capability per unit — which is precisely the axis where Anthropic and the open-weight harnesses have been gaining.
- Speed is now a priced line item, not a bundled extra. Ultrafast at 6×/8× means the 25× allowance and the 8× speed pull against each other on one budget. For interactive blocking work that is a good trade; for background or batch agent work it is close to the worst way to spend the money.
- Region is now a feature gate. A European buyer cannot obtain speed on the flagship model at any price, and cannot obtain dots at all on a personal plan. This is the clearest instance yet of AI coding capability being partitioned by jurisdiction.
- Safety is a release gate, again. A frontier coding model delayed on safety grounds, in the same week the allowance shrinks, is the “capability vs. trustworthy delivery” tension made visible in a shipping calendar.
Caveat: the GPT-6.1 Astra safety delay is reported rather than officially announced. Allowance multipliers and Ultrafast rates are from OpenAI’s own help-centre and pricing pages; the “≈300 tok/s” figure is a publisher estimate of the Ultrafast tier, not an OpenAI spec.
3. Agility Robotics sets its Nasdaq date — and 61% of the SPAC trust walks
What happened. On 30 October, Agility Robotics and Churchill Capital Corp XI announced expected gross proceeds of ≈$465M for their business combination, before expenses:
| Component | Amount |
|---|---|
| Churchill XI trust (post-redemption) | ≈$164M |
| Common-stock PIPE at $10/share, led by Foxconn | ≈$201M |
| Equity already received since announcement | $100M |
| Total | ≈$465M |
Timeline: shareholder vote 2 November, close 4 November, first trade on Nasdaq as AGLT on 5 November, 180-day lock-up with all existing holders rolling 100% of equity. Named strategic investors: NVIDIA, Amazon, SoftBank Vision Fund 2, Schaeffler, Foxconn, Abico, DCVC, Playground Global.
The number that matters is the gap. When the deal was announced in June it was projected at >$620M, with ≈$424M from trust assuming no redemptions. Actual trust: $164M. Public holders pulled ≈$260M — about 61% of the trust. Hedge-fund money took its cash back; a Foxconn-led strategic PIPE replaced it. Agility will be the only US-listed pure-play humanoid company with proven active commercial deployments.
Commercial base as stated by the company: Digit has >65,000 hours of real-world operation; GXO expanding to two additional sites (Statesville NC, Lebanon TN — Digit 4 early 2027, migrating to Digit 5); AGCO manufacturing pilot in 2027; three additional paying manufacturing customers, unnamed but described as a global automaker selling >3M vehicles/year, one of the world’s largest automotive technology and components developers, and a leading global consumer-products manufacturer; pipeline of >30 prospective customers; >$300M committed multi-year Digit 5 orders, which the company explicitly cautions “does not represent current-period revenue.” Digit 5 early-access deliveries H1 2027, GA end of 2027.
Why it matters.
- A clean instrument, finally. Tesla’s Optimus sits inside a car company; Unitree lists in Shanghai; Figure and Physical Intelligence stay private. AGLT is the first listed equity whose value rises and falls almost entirely on whether bipedal labour gets bought at scale — every quarterly report becomes a referendum, stripped of EV noise.
- Public money and industrial money voted in opposite directions. 61% redemption alongside a Foxconn-led PIPE is a precise split: financial investors want liquidity, and the contract manufacturer that assembles iPhones wants a seat inside one of two US humanoid makers positioned to need exactly its capacity.
- The listing lands five days after Section 232. Whatever it does to input costs, the proclamation formally designates domestic humanoid capability as something the state wants to exist. AGLT is the purest listed beneficiary — domestic buyers now have a fresh reason to pay a premium over Chinese hardware.
- The arithmetic is still brutal. Against the momentum markers: roughly $1.8M of 2025 revenue, a ~$140M operating loss, Digit at ~$8,500/month rental, and an investor presentation putting post-close EV near $2.5B. The release leans on momentum precisely because the financial scale is much smaller than the headline.
Caveat: the $465M is “expected” and pre-expenses; redemption reversals remain possible up to the 2 November vote, so final trust maths changes. The ~$2.5B EV figure comes from a circulating investor presentation, not the 8-K. The >$300M order figure is milestone-contingent potential value.
4. Meta built a humanoid with a Chinese OEM in three months — and is already on version two
What happened. The Information reported (31 October US / 1 November China) that Meta and Shanghai-based Fourier Intelligence have jointly built a humanoid prototype codenamed “Max” — the first public disclosure of the partnership.
| Attribute | Detail |
|---|---|
| Weight / height | ≈106 lb (~48 kg) / ≈1.5 m |
| Build time | 3 months |
| Compute | NVIDIA Jetson Thor + a separate motion-control software stack |
| Interaction hardware | Two chest speakers; eyes and mouth capable of human-like expression; five-finger dexterous hands that can pick up small bottles and toys |
| Meta’s stated requirements | Voice recognition at 5 m; gesture/wave interpretation at 3 m; maintained eye contact; rendered states for listening / thinking / speaking / uncertain |
| Status | Shown internally to some employees in late August; no launch timeline |
Max 2 began in September: redesigned torso, more capable hands, an added projector for visual content, and additional sensors to help the robot climb stairs. Meta’s VP of robot product, Li-Chen Miller, reportedly spent nearly two months on-site at Fourier’s Shanghai factory.
Organisational context: Meta Robotics Studio was stood up in 2025 with ex-Cruise CEO Marc Whitten, who left at the end of August; Ning Li now leads the studio on an interim basis, reporting to CTO Andrew Bosworth, who internally frames the humanoid as the physical carrier for Muse. Meta is hiring a supplier development engineer in Shanghai explicitly to move robots “from prototype to mass production,” plus product design and technical programme roles in Shenzhen.
The regulatory collision. In July the FCC barred imports of new Chinese humanoids over supply-chain and cyber risk. Current rules allow up to 4,000 units for testing or development where there is no marketing or sale — the clause that likely let Meta bring prototypes in. In August the FCC proposed cutting that threshold to 40 units absent written approval. Meta’s statement: it faces “the same realities as the rest of the industry” sourcing components not readily available domestically, the Fourier collaboration is “focused on internal research and experimentation,” and it has no plans to sell these devices.
Why it matters.
- A US consumer-tech giant is physically co-developing with a Chinese OEM while its own government builds the wall. The split is now explicit: R&D depends on the Chinese supply chain; market access is being legislated against it. Meta’s hiring in Shanghai and Shenzhen says it is planning for the dependency, not exiting it.
- The spec sheet is interaction, not locomotion. 5 m voice, 3 m gesture, eye contact, rendered internal states — Meta is specifying a social interface, consistent with framing the robot as a Muse body rather than a warehouse worker. That is a genuinely different product thesis from Digit, Optimus or G2.
- Speed is the signal. Three months from kickoff to a working prototype, and version two already underway, indicates the Chinese OEM ecosystem can compress hardware iteration far faster than a US team building from scratch — which is exactly the capability the FCC proposal targets.
- Leadership churn is the counter-signal. The founding studio head out after 18 months, an interim lead, and the CTO personally deep in operations is not a programme running to plan.
Caveat: all details are from The Information via unnamed people familiar; neither Meta nor Fourier has confirmed the partnership on the record beyond Meta’s quoted statement. The FCC 40-unit figure is a proposal, not a final rule.
5. China’s embodied-intelligence dataset standard takes legal effect — the scale narrative is over
What happened. 1 November 2026 is the effective date for a bundle of Chinese national and industry standards:
| Standard | Scope |
|---|---|
| YD/T 6771-2026 — AI Key Foundational Technologies: Quality Requirements and Evaluation Methods for Embodied Intelligence Datasets | Drafted by CAICT with 40+ organisations, MIIT-approved. Three parts: data-production operational norms, organisational-mechanism guarantees, and quality metrics across eight dimensions — completeness, consistency, diversity, authenticity, usability, practicality, extensibility, security |
| 4 large-model platform standards (CAICT-led) | Cover the five stages of data processing, model training, inference, resource scheduling, and O&M — pulling competition from “model benchmark scores” to output per unit of compute |
| GB/T 47514-2026 — Distributed Computing: Computing Power Measurement Methods | A common measurement language so scheduling and trading have a pricing basis |
| 7 national standards on agent interconnection | Target non-unified communication interfaces and missing identity management — the “information island” problem |
Context: China’s AI core industry exceeds ¥1.2T; the LLM market reached ¥49.539B in 2025 (+49.1%) and is expected to pass ¥70B in 2026; >80,000 enterprises have deployed LLMs; actual intelligent computing capacity exceeds 2,592 EFLOPS; the broad embodied-intelligence market is projected above ¥1T in 2026. Compliance spend is estimated at 10–15% of project delivery cost in sensitive scenarios and 5–8% in low-risk ones — a real threshold for small AI firms without dedicated compliance teams.
Why it matters.
- Data is now valued by density, not hours. The standard switches the unit of competition from dataset size to effective information density × task difficulty × closed-loop gain. Valuations supported by “we collected N million hours” now face an acceptance criterion, and the million-hour production capacity that was treated as a hard R&D threshold in 2026 is no longer sufficient on its own.
- This is the same “verification over generation” move seen in AI coding. Benchmarks gave way to acceptance criteria; generation gave way to provable quality. Embodied intelligence just got its own version, at the input layer rather than the output layer.
- Agent identity and interop became a national standard question. Seven GB standards on agent interconnection is an implicit admission that cross-platform agent collaboration is now an economic prerequisite, not a nice-to-have — the same conclusion Google reached with Agent Client Protocol and Android Studio BYOA last week.
- Compliance capability becomes the dividing line. Large platforms can embed the standards in their R&D process at low marginal cost; small embodied startups must remediate on data provenance, platform O&M norms and inference efficiency simultaneously.
Caveat: effective date is 1 November; enforcement practice and certification schemes are not yet documented. The market-size and compliance-cost figures are outlet/consultancy estimates.
6. Embodied capital halves in a month: the ledger splits into “uniqueness” and “acceptability”
What happened. IT桔子 data through 29 October, published 30–31 October:
| Period | Deals | Value |
|---|---|---|
| Oct 2026 | 33 | ¥10.105B |
| Sep 2026 | 60 | ¥11.028B |
| Jun 2026 (peak) | 55 | ¥30.892B |
| H1 2026 (艾媒) | 172 | ¥109.174B (~¥18.2B/mo avg) |
Deal count −45% month-on-month; value only −8.4%; average deal size ¥184M → ¥306M. October is roughly 55% of the H1 monthly average.
The more honest signal is the secondary market: embodied secondary transfers are quoting at 6.5–8折 of the last round’s valuation, and not for bad assets — one frequently cited case has an investor who entered at ¥3B post-money watching the paper valuation reach ¥22B, asking ¥12B (a ~45% discount), and still finding no buyer.
Public markets moved the same day: the A-share humanoid index fell 4.20% on 30 October with ≈¥9.327B net main-capital outflow, wiping out the prior week’s +7.03% rebound.
Against that, the industrial ledger kept running: MIIT expects >100,000 humanoid units produced in China in 2026 (H1: >400 models, >40,000 units); 智元 reports H1 revenue ≈¥2B; 宇树 reports Q1–Q3 revenue ¥1.817B with net profit ¥387M (+270%). But Counterpoint’s shipment mix says >60% of H1 global humanoid volume went to stages, shows and labs, with manufacturing at 13% and warehousing 5%; Frost & Sullivan counts only 1,200 units / $78M revenue globally in H1 under “production operation.”
Two operators’ framings, both worth recording:
- 智元 partner/SVP 姚卯青 attributes the cooling to “re-convergence of a hot track” rather than a robotics-specific cycle, and names the screening criteria as success rate, takt time, stable operation period, and total operating cost.
- 智元 CTO 彭志辉: “10,000 units rolling off the line is a victory for manufacturing; 10,000 units on the job is a victory for physical AI” — the basis for the Worken metric (active robots × autonomous hours × output-efficiency ratio).
Why it matters.
- Two markets pricing two different things. Public markets price uniqueness (Agility’s “only listed pure-play with deployments”); primary markets price acceptability (can this be verified to work on someone’s line). Both were repriced on the same day.
- Fewer deals, bigger deals is a selection event, not a collapse. Capital concentrated into fewer, later, more defensible names — consistent with the secondary market’s discount on everything else.
- The growth is real and the mix is still wrong. Unit output is beating every forecast while >60% of volume goes to stages and labs. That gap is precisely what the new dataset standard and the Worken metric are both trying to close.
- Money is rotating upstream. Chips, tactile sensing, data collection and certification have higher order visibility and don’t depend on any single OEM winning — visible in 辉羲智能’s A-share IPO tutoring filing (reported here 31 October) with >¥2.5B of equity financing this year.
Caveat: IT桔子 counts only disclosed rounds and is a private-market database, not an official statistic; the secondary-market discount range and the ¥3B→¥22B→¥12B case are media-reported. Counterpoint and Frost & Sullivan use different denominators and scopes. 智元’s revenue is unaudited; MIIT’s 100,000-unit figure is a projection.
7. 破壳机器人 ships RoboAPI: the embodied model as an API, free to attach
What happened. On 30 October, PokeBot (破壳机器人, founded April 2026) released RoboAPI, its first model product, alongside the first public disclosure of its world-action model Poke-Aurora.
The delivery form is the point. On an adapted robotic arm, a developer collects no data and trains no model — a single prompt instructs the arm, which then performs tasks it was not specifically trained for in an unfamiliar environment. RoboAPI takes robot observation and state plus the user instruction and predicts the next action near-real-time. The team’s stated reference is explicit: the GPT-3 API, which let developers stop training and deploying their own language models.
Positioning: currently non-commercial, not offered to for-profit third parties, with free developer access via quick-start docs and a developer platform.
Why it matters.
- The delivery unit is changing from weights to interface. For two years the embodied field shipped “model weights + a paper.” An API with zero integration cost is the first step of genuine platformisation — the same transition that created the LLM application layer.
- Zero-shot generalisation is now the product claim, not the benchmark claim. RoboAPI is explicitly positioned to demonstrate zero-shot transfer. That reframes what an embodied model is for.
- It puts pressure on the data-standard question from the other side. If an API can bypass per-customer data collection entirely, the dataset quality standard that took effect today governs the producers of that API rather than its consumers.
Caveat: vendor-announced with no third-party reproduction; “near-real-time” is unquantified; the zero-shot scope is stated for “adapted arms,” implying a supported-hardware list not yet published. Non-commercial status means no production evidence exists yet.
8. Claude Code’s background-agent status ticker measured at ~16% of a user’s bill
What happened. Reporting on 31 October quantified a cost behaviour that has been on by default since Claude Code 2.1.232 (August 2026): roughly every 30 seconds, the entire background-agent conversation is sent to the model (often Opus) to generate a 3–5 word status update. Measured impact for heavy background-agent users: ≈16% of total API spend and ≈20% of API calls. There is no built-in toggle. Mitigation requires measuring your own ratio via OpenTelemetry or applying community scripts to stop the timer.
Separately, Claude Code 2.1.316 shipped on 31 October: pooled group budgets, a new sub-agent effort setting, and a fix for shell commands left running after exit. Opus 4.8 fast mode is retiring. Release cadence remains roughly daily (2.1.314 on 30 October → 2.1.316 on 31 October).
Why it matters.
- Observability is now a cost centre, and it is not user-controllable. The industry has spent a month on token-waste tooling — TokenEconomizer measured 18–31% savings from tool pruning and failure-loop intervention; Factory Droid cut its base prompt 37%. Those are user-side optimisations. This one is vendor-side, default-on, and undiscoverable without instrumentation.
- It pairs precisely with item 2. OpenAI is repricing allowance; Anthropic is consuming it in the background. In both cases the developer’s mental model of “what am I paying for” no longer matches the implementation.
- It is the same argument DeepSeek is making in item 1, from the opposite direction. DeepSeek is building a notification budget to protect attention. Claude Code is spending ~16% of a bill to emit three-word strings.
Caveat: the ~16%/~20% figures are community measurement on heavy background-agent workloads, not an Anthropic disclosure; the impact is described as negligible for occasional or desktop-only use. The 30-second interval is approximate.
Radar — also in the window
- OpenAI lowers its raise. The Information (30 Oct): now seeking $20B instead of $30B, after decreasing its possible valuation. Still unannounced officially.
- Anthropic S-1: ~$900B of off-balance-sheet obligations. Bloomberg (picked up 31 Oct): $117.5B liabilities against $112B cash, with leases and data-centre/power/GPU purchase agreements not directly on the balance sheet. On the All-In podcast, White House science and technology advisor David Sacks said Anthropic could become “the greatest company in the history of capitalism” and possibly the highest-return VC investment ever. The Information (30 Oct) separately: “An Anthropic Windfall Could Await State Pension Funds.” S&P lowered Meta’s credit outlook the same day over AI spending.
- >$3T of hyperscaler commitments. Bloomberg (31 Oct): Alphabet, Meta, Microsoft, Amazon and Oracle have pledged >$3T. Google >$1T (≈8× a year ago); Meta >$800B with nearly half in leases amortised up to 30 years; Oracle is the first large tech company to go free-cash-flow negative because of AI data centres, expected to recover by 2028.
- Section 232 robotics proclamation (28 Oct). Trump signed a proclamation finding imports of robotics, industrial machinery and components threaten US national security — explicitly naming humanoid, quadruped and autonomous ground robots — and ordered Commerce + USTR to negotiate, with a 180-day report (≈26 April 2027). No tariff, quota or fee took effect; tariffs, quotas, fees and domestic-investment incentives are all reserved as future options. Robotics supported ≈$7.1T of 2024 US manufactured-goods shipments and ≈$86B of equipment production.
- OpenRouter: a 233-line code-review agent that actually runs the code. Tutorial (1 Nov 08:00 Beijing):
review.pycombining Responses API + Files API + a hosted Linux Shell sandbox + Apply Patch, uploading the diff so the model can execute and confirm the bug before returning a V4A patch. Four models benchmarked; designed to drop into a pre-push hook or GitHub Actions. Companion tutorial (31 Oct): an always-on Hacker News monitoring agent with@openrouter/agent0.11.0 and published real cost data. - Mundo world model — 大晓机器人 × NTU S-Lab (30 Oct): 1–12 images → an explorable 3D space with editable mass and friction, scripted actions and forces, physics-engine trajectories with contact positions and collision forces, video-model rendering, navigation and manipulation sides, and “bullet-time” 4D inspection. Already used to rebuild a hotel floor and simulate washing-machine door opening.
- Embodied funding not yet in the body: 智澄 AI (Hangzhou, founder 胡鲁辉, ex-Meta chief engineering lead) raised several-hundred-million-yuan; XR1 composite robot is in NIO’s production line, testing at VW, with a third-generation inspection robot for State Grid; open-sourced the JEPA-based 澄灵 world model 0.1 in May.
- Open-source agent layer (31 Oct): Hermes Agent plugin pack with SHA-pinned reproducible plugins and unified provider quotas; Android Harness v3.1 (native Android AI coding agent, no root or PC); Superagent Desktop (macOS host for Claude Code/Codex with persistent chat and browser automation); OSS Autopilot (Claude Code plugin for PR tracking, maintainer responses and issue discovery);
vibe-ic(MCP-EDA, natural language to verified silicon);qq-bridge(QQ bots ↔ DeepSeek Harness agents). - Kimi K3.1 Pro open weights due 4 November. DeepSeek Search/Fetch per-call billing (¥5 per 1,000 successful requests) started 1 November 00:00 Beijing time — agent tool calls now cost independently of tokens.
- OSS release board (30–31 Oct): Factory Droid 1.1.0 (public audit API for enterprise owners,
doctorcheck for duplicate PATH installs), OpenCode 2.2.5 (percentage compaction buffers, one-key worktree switching), Devin Desktop 3.11.235/238 (4 MB log retention up from 25 KB; Anthropic Cyber Verification Program toggle), Replit Cloud Agent 2026.10.30.
Six trends this window
- The bottleneck is named, and in both fields it is not the model. DeepSeek says it is human attention (3–5 trackable sessions); 姚卯青 says it is acceptability (success rate, takt time, stable period, total cost); the new Chinese standard says it is data quality density. Three independent parties, one conclusion: capability is no longer the scarce input.
- Agent economics became opaque at exactly the moment it became decisive. OpenAI flattened unit price across every rung while halving one tier’s allowance; Claude Code spends ~16% of a bill on three-word status strings with no toggle; DeepSeek bills Search/Fetch per call from 1 November. Comparing “which model is cheaper” now requires instrumenting your own harness.
- Embodied capital split into two ledgers with different currencies. Public markets bought uniqueness (AGLT) while 61% of that very SPAC’s trust redeemed; primary markets cut deal count 45% while average deal size rose 66%. Industrial money (Foxconn) stepped in where financial money stepped out.
- The US–China robotics relationship is now formally two-track: co-develop, don’t import. Meta builds with Fourier in Shanghai and hires for mass production there, while the FCC proposes cutting the R&D import cap from 4,000 to 40 and Section 232 starts a 180-day clock. R&D dependency and market access are being legislated in opposite directions simultaneously.
- Embodied delivery is being re-formatted, twice. RoboAPI turns a model into a free API; the dataset standard turns data into a graded commodity. Both are moves to make the layer attachable rather than buildable — the precondition for a platform.
- Standards and proclamations replaced benchmarks as the day’s most consequential documents. Eight-dimension dataset quality, four platform standards, computing-power measurement, seven agent-interconnection GB standards, and a Section 232 finding all landed in a four-day span. Competitive advantage is increasingly written in compliance capability, not capability alone.
Sources
- AI HOT selected feed (5 items/24h), 1 Nov — OpenRouter code-review and always-on-agent tutorials; Sacks on Anthropic; Bloomberg $3T; Anthropic off-balance-sheet debt.
- Direct fetch: agilityrobotics.com joint release (Form 425/8-K exhibit); InfoQ/163 on
dsh-superagent-prototype; theinformation.com front page; whitehouse.gov Section 232 proclamation; CAICT/Xinhua standard text. - Embodied: 21世纪经济报道 (智元/宇树 “交卷期” headline, 31 Oct); 红星新闻 (姚卯青); IT桔子 via 投行圈子/163; 界面新闻 (CEL, Mundo); 机器之心 (RoboAPI); 腾讯新闻/电鳗财经 (standards bundle); 网易/智能纪元 AGI (Meta × Fourier); korthosrobotics + aidaily.si + singularity.kiwi (Agility).
- AI coding: hnglance (HN thread reproducing OpenAI’s Pro email); pick-right.com (allowance arithmetic, Ultrafast pricing); theclarity.today (streaming rate); help.openai.com (Ultrafast rules); havoptic.com (release board); techyupdate.com / note.com (Claude Code 16% measurement).
Quality check
- All DeepSeek numbers are the team’s own, measured in a simulated environment against an unnamed single-session baseline; the prototype’s own security warning is quoted rather than softened.
- Agility’s $465M is “expected,” pre-expenses, and subject to redemption reversal before the 2 November vote; the >$620M projection and the ~$2.5B EV come from trade press and a circulating investor presentation respectively, not the 8-K. The >$300M order figure is explicitly milestone-contingent.
- Meta × Fourier rests entirely on one outlet’s unnamed sources. Meta’s on-record statement covers only sourcing difficulty and “no plans to sell.” The FCC 40-unit figure is a proposal.
- The Chinese standards bundle is verified against Xinhua/CAICT primary text for YD/T 6771-2026; the companion standards (4 platform items, GB/T 47514-2026, 7 agent-interconnection items) are reported by 电鳗财经 via Tencent News and not individually cross-checked against the standards database.
- The Claude Code 16% figure is community measurement, not an Anthropic disclosure, and applies to heavy background-agent workloads.
- Dedup: CEL, 灵渠OS, GO-3 scaling, AgiBot Innovation Day core (Oct 29–30) and 辉羲智能 IPO tutoring were covered in the 31 October issue and appear here only as context or comparators. Agility’s SPAC terms, the OpenAI repricing, the DeepSeek prototype, the standards effective date, RoboAPI, the Claude Code cost measurement, Meta × Fourier and the funding-winter ledger are all first coverage in this window. The Pro 500 tier introduction appeared in the 30 October radar; today’s item is the 20×→10× cut and the unit-price arithmetic.