EAIDaily — July 13, 2026

AI Coding × Embodied Intelligence Daily Briefing

1. GPT-5.6 Sol Ultra Proves 50-Year Math Conjecture in Under 1 Hour

What happened: OpenAI announced that its GPT-5.6 Sol Ultra model generated a complete proof of the Cycle Double Cover Conjecture — a graph theory problem open since the 1970s (Szekeres 1973, Seymour 1979). The model deployed 64 parallel sub-agents plus adversarial agents to search for gaps and edge cases, completing the proof in roughly 1 hour out of an 8-hour allocated window. OpenAI published the proof and prompts as a PDF on its CDN, claiming the entire proof was generated independently by the model with no web search allowed.

Why it matters: If peer-reviewed and verified (it has not yet been formally vetted or checked with Lean-style tools), this would be the first LLM to independently solve a problem on Wikipedia’s “unsolved problems in mathematics” list. It demonstrates that multi-agent orchestration at frontier scale can produce creative mathematical reasoning — not just retrieval or pattern-matching — but recombining existing knowledge in novel ways. The use of adversarial sub-agents for self-verification points toward a future where AI research agents build their own quality assurance loops, a pattern directly applicable to AI coding agents that must verify their own code before committing.

🔗 IT之家 report · AI HOT item

2. China MIIT Officially Warns Against Claude Code Security “Backdoor” — Trust Crisis Deepens

What happened: China’s Ministry of Industry and Information Technology (MIIT) cybersecurity threat-sharing platform (NVDB) issued an official risk advisory on July 8, declaring that Anthropic’s Claude Code (versions 2.1.91–2.1.196) contains a hidden monitoring mechanism that silently transmits user location, device identifiers, account identity, source code, and project documents to overseas servers — bypassing user authorization, with no pop-ups or logs. Alibaba banned all employees from using Claude Code on July 10, replacing it with the self-built agent coding platform Qoder. Tencent had already removed Claude Code from its model selection pool in November 2025; Meituan and JD.com followed with restrictions. On July 13, state media reinforced the warning, calling for “full-chain” protection including minimum-privilege principles, data isolation, and accelerated domestic AI tool substitution.

Why it matters: This marks a regulatory escalation from corporate bans to government-level security advisories — the same trajectory as export-control hardening but from the demand side. For AI coding, it means Chinese enterprises face a fork: either adopt domestic alternatives (Qoder, ZCode, etc.) or operate foreign coding agents in air-gapped environments. The broader signal is that trust in AI coding tools has become a geopolitical variable, not just a technical concern. The “minimum privilege + data isolation” framing will shape procurement standards globally, as other jurisdictions may adopt similar regulatory templates.

🔗 MIIT advisory via 环球网 · 央媒 commentary

3. xAI Grok Build CLI Uploads Entire Repository — Including .env Secrets and Git History

What happened: A network-traffic teardown of xAI’s Grok Build CLI (v0.2.93) revealed three disturbing behaviors: (1) files read by the agent — including .env secret keys — are transmitted verbatim and unredacted via POST /v1/responses and archived in a session_state package via POST /v1/storage (both returning HTTP 200); (2) the entire repository is uploaded as a git bundle to a Google Cloud Storage bucket named grok-code-session-traces, independent of what the agent actually reads — even with the prompt “do not read any files,” a canary file was recoverable from the uploaded bundle; (3) disabling the “Improve the model” setting does not stop uploads — the /v1/settings endpoint still returns trace_upload_enabled: true. In a 12 GB repo test, the storage channel transmitted 5.10 GiB while the model conversation channel moved only 192 KB — a 27,800:1 ratio.

Why it matters: This is the second major coding-agent privacy incident in a week (after Claude Code’s steganography/backdoor revelations). Together they establish a pattern: coding agents are not just text-in/text-out tools — they are network clients with upload behaviors that users cannot reliably control through settings. The implication for organizations is that any codebase touched by a coding CLI may have been fully copied to a vendor’s cloud storage, including secrets, internal architecture, and git history. Auditing outbound traffic and sandboxing agent environments are no longer optional — they are baseline requirements. The 27,800:1 ratio also raises the question: if the model only needs 192 KB of context, what is the business purpose of the 5.1 GiB upload?

🔗 HN original gist · Detailed guide · AI HOT item

4. Perplexity “Teammate”: AI Coding Agent for Full Project Lifecycle, Model-Agnostic Architecture

What happened: Business Insider revealed that Perplexity ($20B valuation AI search startup) has built an internal coding agent codenamed “Teammate,” in use by engineers since May 2026. Unlike Cursor or Claude Code (which focus on code generation and editing), Teammate is positioned as a project-level engineering agent: managing entire projects, researching problems, and monitoring production services over long time horizons. It is model-agnostic — routing tasks to whichever LLM performs best for each subtask. Perplexity CTO Denis Yarats has pushed engineers toward AI-first coding, stating that by year-end they should “stop looking at code” and rely on AI, arguing that code quality concerns are moot if generated code passes all quality checks. No public launch date has been confirmed.

Why it matters: Teammate represents the next evolutionary step for coding agents: from “autocomplete” (Copilot) → “task-level agent” (Claude Code) → “project-level orchestrator.” Its model-agnostic design is architecturally significant — it means the agent’s capability ceiling is determined by orchestration logic, not by a single model’s limitations. If Perplexity launches it commercially, the coding-agent market will have four distinct tiers of abstraction, forcing buyers to choose between line-level, task-level, project-level, or portfolio-level automation. Yarats’s “stop looking at code” stance also crystallizes the industry’s most divisive question: when does delegation become abdication?

🔗 Business Insider via ReadAboutAI · 中文分析

5. Step Star Launches World’s First “Native AI Agent Phone” — Beating OpenAI’s 2027 Timeline

What happened: On July 13, Step Star (阶跃星辰, a Shanghai-based LLM unicorn founded by former Microsoft VP Jiang Daxin) launched its first AI agent phone at a live-streamed event, introducing three products simultaneously: a new AI terminal brand, a proprietary agent operating system, and the first commercially available “native agent phone.” The phone’s core differentiator is system-level architecture: the self-built Step model is embedded at the OS layer, enabling the phone to autonomously execute cross-app tasks (ordering food, booking appointments) through Step-GUI, which can operate across 200+ apps. Manufacturing partner Huqin Technology (华勤, >10% global smartphone share) provides deep-integrated ODM production. Step Star previously deployed models on 60% of top Chinese phone brands, with 4.2M+ devices already running Step models. OpenAI has expressed interest in AI terminals but plans its own device only for 2027.

Why it matters: This is the first time an LLM company has shipped a consumer hardware product where the agent is the primary interaction paradigm, not an overlay on an existing OS. The Step Star phone tests whether “native agent” UX can displace the app-centric model that has defined smartphones since 2008. For the AI coding world, the signal is that the agent paradigm is expanding beyond developer tools into consumer devices — the same agent architecture (plan → execute → verify) that powers Claude Code is being embedded into phones for everyday tasks. If consumer agents succeed, it validates the agent-first design pattern at scale, accelerating its adoption in enterprise coding workflows.

🔗 Step Star launch · 凤凰网科技

6. Mindwalk: Open-Source 3D Visualization for AI Coding Agent Session Replay

What happened: A new open-source tool called Mindwalk (Go + TypeScript, v0.1.0) lets developers replay Claude Code and Codex session logs as interactive 3D visualizations of their codebase. It renders the repository as a “night city map” — files the agent touched glow, untouched areas stay dark. Touch states are color-coded: seen (moss green), read (moon white), edited (warm amber), unvisited (dark). A HUD shows friction signals (error rate, churned files), and a playback scrubber lets developers step through sessions frame-by-frame. The tool runs fully local with no cloud, no upload, no account. It gained 108 points and 46 comments on Hacker News in its first day.

Why it matters: As coding agents become more autonomous and long-running, understanding what they did and why becomes a first-class engineering problem. Mindwalk addresses the observability gap between “agent ran for 30 minutes and produced a diff” and “I can audit the agent’s reasoning path.” The 3D spatial metaphor — attention as a shape, not a log — may become a standard pattern for agent monitoring. For organizations adopting coding agents, tools like Mindwalk will be essential for trust verification: before approving an agent’s changes, you need to see its exploration footprint, not just its final output. This is the observability layer that makes autonomous coding agents auditable.

🔗 GitHub · dev.to breakdown · AI HOT item

7. 1X Releases 25-DOF Bionic Dexterous Hand for Neo Humanoid — 10K/Year Production Scale

What happened: Silicon Valley robotics company 1X (backed by OpenAI) showcased the latest dexterous hand for its Neo humanoid robot, featuring 25 degrees of freedom with bionic tendon-driven actuation — flexibility approaching human hand capability. The hand includes a tactile sensing layer, IP68 waterproofing, and food-grade materials. 1X has completed full production line setup with annual capacity of 10,000 units, claiming to be one of the very few companies that have closed the “technology verification → engineering optimization → scaled production” triple loop for high-end dexterous hands.

Why it matters: Dexterous manipulation is the last major hardware bottleneck for humanoid robots — most current humanoids have hands with 6–12 DOF, suitable for grasping but not for fine manipulation. A 25-DOF hand at 10K/year production scale means that the physical capability gap between robots and humans for hand-intensive tasks (surgery, assembly, cooking) is closing rapidly. For embodied intelligence, this is the hardware complement to NVIDIA’s GR00T software: the brain (GR00T VLA model) now has hands that can execute what it plans. The 10K/year production figure is also significant — it’s the first confirmed scaled manufacturing of high-DOF dexterous hands, moving from demo units to deployable inventory.

🔗 IT之家 report · 机器人日报

8. Nadella’s “Reverse Information Paradox”: Enterprises Must Protect Knowledge Sovereignty When Using AI

What happened: Microsoft CEO Satya Nadella introduced the concept of a “reverse information paradox” in the AI era: buyers pay money to use AI while simultaneously exposing proprietary knowledge (prompts, tool usage patterns, correction feedback) — “intellectual exhaust” that models learn from, tilting information asymmetry toward sellers. Nadella argued enterprises need trust boundaries ensuring that their data, traces, evaluations, adaptation weights, and memories accumulate inside the boundary, not outside. He called for enterprises to own private evaluations, retain organizational memory ownership, and have the right to use model outputs to fine-tune or train their own models — controlling their own learning loops.

Why it matters: This is the highest-profile articulation of what the Grok Build and Claude Code privacy incidents demonstrate in practice: using AI tools inherently leaks organizational knowledge. For AI coding specifically, the implication is stark — every debugging pattern, architecture decision, and code review preference you feed to a coding agent becomes training data for the model provider. Nadella’s framing elevates this from a privacy compliance issue to a strategic competitive concern: if your “learning loop” runs through someone else’s model, they accumulate your institutional knowledge while you pay for the privilege. The solution architecture — private evaluations, on-premises fine-tuning rights, data boundary controls — will shape enterprise AI procurement standards for the next decade.

🔗 Nadella on X · AI HOT item

Quick Takes

Trend Lines

1. Agent observability becomes a product category: Mindwalk’s 3D session replay + friction HUD shows that understanding agent behavior is now a distinct engineering need, not just logging. Expect observability suites for coding agents within 6 months.

2. Trust boundaries replace feature checklists as procurement criteria: MIIT’s Claude Code ban + Grok Build’s 27,800:1 upload ratio + Nadella’s “reverse information paradox” all point to the same shift: organizations will evaluate AI tools on data sovereignty guarantees first, capability second.

3. Model-agnostic agent orchestration emerges: Perplexity Teammate routes subtasks to the best LLM per category. Mesh LLM runs P2P inference across heterogeneous hardware. The winning agent architecture may not be “best model” but “best router.”

4. Embodied intelligence enters the dexterous-hand era: 1X’s 25-DOF hand at 10K/year + NVIDIA GR00T 1.7 in LeRobot = the software-hardware stack for fine manipulation is finally closing. The bottleneck shifts from “can the robot grip?” to “can the robot decide what to grip?”

5. AI research agents prove creativity, not just retrieval: GPT-5.6’s cycle double cover proof + adversarial self-verification + the ASPIRE framework’s 77-point LIBERO-Pro gain both show agents generating novel solutions. The “AI only remixes” argument is losing empirical support.

6. Consumer hardware becomes the agent proving ground: Step Star’s native agent phone tests whether agents work outside developer terminals. If consumers accept “the phone does it for me,” the agent paradigm escapes the IDE entirely.

Compiled by @WoLoveAI · Data sources: AI HOT (aihot.virxact.com), WebSearch, official announcements, HN discussions