AI Coding Live News

Cursor Projects Goes Multiplayer: Teammates and Their Agents Share One Workspace, and Agents Sync Plans and Flag Conflicts With Each Other; Beta Rolling Out to All Users

On November 10, Cursor rebuilt Projects for multiplayer. You can invite teammates into a Project, and everyone plans, builds, and ships in one workspace alongside their coordinator and worker agents. A new shared context layer holds requirements docs, diagrams, tech specs, and mockups, so a decision made in one chat is visible to every agent in the Project. A shared task board shows who is doing what, what each agent is working on, and the PR behind each task. Agents belonging to different teammates can also talk to each other: they share plans before starting, flag conflicts while working, and unblock each other. The beta is rolling out to all Cursor users starting today.

Cursor Projects Goes Multiplayer: Teammates and Their Agents Share One Workspace, and Agents Sync Plans and Flag Conflicts With Each Other; Beta Rolling Out to All Users

Key Takeaways

  • Timeline: Projects first launched on September 10 (one person directing thousands of subagents) and became team multiplayer on November 10; the beta is rolling out to all users today
  • Shared context: requirements docs, diagrams, tech specs, and mockups live in one place, so a decision made once is visible to every agent; new teammates join with context already set up
  • Agent-to-agent: coordinators belonging to different teammates share plans up front and flag conflicts mid-work, for example agreeing on order when one person changes a schema another feature reads, avoiding late merge conflicts
  • Shared task board: shows people, agents, and PRs together; Cursor already runs on-call rotations in a shared Project, and the incoming engineer's agent can take over in-flight work directly
  • Impact figures: at the September launch Cursor said new users merge 30% more PRs and heavy Projects users merge 6x as many (vendor figures); no new figures were published for multiplayer
Read full story
Linked Models & Agents:

NVIDIA Donates OpenShell, Its AI Agent Security Runtime, to CNCF as a Sandbox Project: Cedar Policies and an Agent Substrate Integration With Google

At KubeCon North America on November 10, NVIDIA contributed OpenShell, its open-source security runtime for AI agents, to CNCF as a Sandbox project. OpenShell enforces access to files, networks, credentials, and model endpoints in the infrastructure outside the agent. The project is moving from NVIDIA's GitHub to the neutral ai-openshell organization and is adopting Cedar, another CNCF project, as its policy language. NVIDIA is also contributing to Google-led Agent Substrate and released three open-source Kubernetes components: NVKE, NVKR, and Snapshot. Teams running agents on Kubernetes now get a vendor-neutral permission and isolation layer.

NVIDIA Donates OpenShell, Its AI Agent Security Runtime, to CNCF as a Sandbox Project: Cedar Policies and an Agent Substrate Integration With Google

Key Takeaways

  • Governance: OpenShell joins the CNCF Sandbox after a TOC vote passed on September 26; code moves to the neutral ai-openshell org, and the NVIDIA/OpenShell repo stays in use until the move is done
  • Scale: about 21K GitHub stars and 2,091 forks, written in Rust under Apache-2.0; NVIDIA says hundreds of organizations use it and it has received tens of thousands of contributions in under a year (vendor figures)
  • Policy: it is adopting the CNCF project Cedar as its policy language; NVIDIA, Red Hat, Docker, and Canonical were early core contributors
  • Ecosystem: NVIDIA is contributing to Google-led Agent Substrate, wiring in Dynamo and KAI Scheduler, and working with Google on an OpenShell plus Agent Substrate integration
  • Companion tools: on HGX B300, Snapshot cut Crusoe's GLM-5.3 ready time from about 8 minutes to 31 seconds and Saturn Cloud's vLLM startup from 2-8.5 minutes to 6-34 seconds (partner figures)
Read full story

Anthropic Gives Claude Pro, Max, Ultra, and Team Users One Free Full Reset Across All Models and Limits, Usable Before December 10 at 2:00 p.m. PT

On November 10, Anthropic's official developer account ClaudeDevs said all Pro, Max, Ultra, and Team users are getting one free full reset, across all models and limits, usable anytime before December 10 at 2:00 p.m. PT (6:00 a.m. Singapore time on December 11). The company said it recently fixed a few small issues that used more limits than intended, and that the earlier Fable resets for the Fable 5.2 launch did not do much for people who had already hit their weekly limits for all models. The issues did not affect everyone, but Anthropic said it wanted to make up for the trouble. The reset is in Settings > Usage, or at clau.de/reset.

Key Takeaways

  • Who: every Pro, Max, Ultra, and Team user gets one free full reset, across all models and limits (official ClaudeDevs post)
  • Deadline: use it anytime before December 10, 2026 at 2:00 p.m. PT (6:00 a.m. Singapore time on December 11)
  • Why: Anthropic said it fixed a few small issues that used more limits than intended, and that earlier Fable resets did little for people who had already hit weekly limits for all models; the issues did not affect everyone
  • How: in Claude on the web, Desktop, or mobile, go to Settings > Usage, or open clau.de/reset, and click Reset for free under Limit resets; the button is not currently available in Claude Code in a terminal or IDE, but account limits are shared, so the restored usage applies in Claude Code too (Help Center)
  • Caveats: a reset does not raise your limits, refund extra usage already billed, or change your usage credit balance; it cannot be undone, and it lapses if you downgrade or cancel before using it
Read full story
Linked Models & Agents:

Meta FAIR Open-Sources e-means, a Drop-In k-means Replacement: Lower Loss in About One-Tenth the Epochs, 10-45x Faster Than Flash-KMeans on GPU, Now in FAISS 1.16.0

On November 10, Meta FAIR researcher Swann Bessa announced e-means on X, a clustering algorithm that replaces classic Lloyd k-means and is open-sourced in FAISS 1.16.0. It swaps full-batch iterations for mini-batch updates with exponential moving averages, and fitted scaling laws set the batch size and step size automatically, so k is the only setting. The paper says that on a range of embedding datasets e-means beats the loss Lloyd reaches after 25 epochs in 1.4 to 2.6 epochs, running 10-45x faster than Flash-KMeans on GPU and 8-15x faster than FAISS k-means on CPU (authors' figures). Teams building vector indexes, RAG pipelines, or dedup jobs can speed up this step directly.

Meta FAIR Open-Sources e-means, a Drop-In k-means Replacement: Lower Loss in About One-Tenth the Epochs, 10-45x Faster Than Flash-KMeans on GPU, Now in FAISS 1.16.0

Key Takeaways

  • Epochs: on a range of embedding datasets it beats Lloyd's 25-epoch test loss in 1.4-2.6 epochs; each of the 11 VIBE datasets needs only 1.6-2.4 epochs (paper/authors' figures)
  • Speed: 10-45x faster than Flash-KMeans on GPU and 8-15x faster than FAISS k-means on CPU; on one H100 with 10M vectors and 65,536 clusters, 25 Flash-KMeans epochs take 14-22 seconds
  • Scale: it splits 10 billion DINO embeddings into 16 million clusters in 2.5 epochs, below Lloyd's loss at 25 epochs
  • Dead clusters: with 1M vectors and k=16,384, reviving by proportionally splitting large clusters keeps dead clusters at 0.1%-0.3%, versus 4.6%-14.3% for EnCodec-style resampling
  • Getting started: from faiss.contrib.e_means import Emeans, 5 epochs by default, PyTorch and NumPy supported; paper arXiv:2611.09501
Read full story
Linked Models & Agents:
ADSponsored

Claude Launches Whiteboards and Sheets in Beta, Renames Dashboards to Claude Data at General Availability, and Lets Interactive Connectors Open Full Adobe, Atlassian, and Box Apps Inside Claude

On November 10, Anthropic added two new artifact types to Claude: Claude Whiteboards, a board teams can edit together, and Claude Sheets, a shared spreadsheet with tabs, formulas, and drop-downs, both in beta on all paid plans. Claude Dashboards, which entered beta in October, is renamed Claude Data and is now generally available, adding data stories, certified queries, and live sharing. Interactive connectors can now open full apps such as Adobe, Atlassian, Box, and Notion beside the conversation or in full screen, where you or Claude can make changes directly. The features are rolling out gradually starting today.

Claude Launches Whiteboards and Sheets in Beta, Renames Dashboards to Claude Data at General Availability, and Lets Interactive Connectors Open Full Adobe, Atlassian, and Box Apps Inside Claude

Key Takeaways

  • New artifacts: Claude Whiteboards and Claude Sheets are in beta on all paid plans and work on web, desktop, and mobile (official announcement)
  • Claude Data: the former Claude Dashboards (beta since October) is renamed and now GA, with certified queries and live sharing still in beta; on Enterprise it turns on by default on November 19, while Team plans get all three on by default
  • Interactive connectors: the first tools include Asana, Canva, Carta, Dropbox, monday.com, Smartsheet, Vercel, and Webflow, and open as full apps beside the chat or in full screen; Figma, Harvey, and Shopify are building integrations (connectors post)
  • Developers: interactive connectors run on the open MCP Apps extension, which now supports app tools and embedded sites in a developer public preview; Claude Marketplace lists 9,000+ connectors and plugins
  • Vendor examples: Anthropic's legal team cut marketing reviews from 3 days to 24 hours with a Claude-built review tool, and customer Advantage Solutions cut FP&A report assembly from about 10 hours to under 30 minutes (vendor figures)
Read full story
Linked Models & Agents:

n8n Labs Open-Sources Nod as a Research Preview: A Personal Agent with Its Own Local VM and Browser That Cancels Trials, Watches Prices and Pulls Invoices, Checks Permission Before Acting, and Scores 93.2% on LongMemEval

On November 10, n8n Labs, a new team inside workflow-automation company n8n, released Nod as a research preview. It is a desktop app separate from n8n that works inside a sandboxed virtual machine on your computer with its own browser. It connects to Gmail, Calendar, Drive, Slack, and Notion, can operate websites that have no integration, and takes requests in the app, on Telegram, or on WhatsApp. Nod is open source under Apache 2.0 and uses your own ChatGPT Plus/Pro plan, API key, or a local model. Before it sends, pays, posts, or deletes anything, a separate model checks that you asked for it, and n8n warns that this check can itself make mistakes.

n8n Labs Open-Sources Nod as a Research Preview: A Personal Agent with Its Own Local VM and Browser That Cancels Trials, Watches Prices and Pulls Invoices, Checks Permission Before Acting, and Scores 93.2% on LongMemEval

Key Takeaways

  • Status: research preview for macOS 14+ and Windows 11 (WSL 2 required); the latest build, v0.6.1, shipped November 10 (GitHub Releases)
  • License and cost: Apache 2.0, free app; you pay your own model provider via ChatGPT Plus/Pro, an API key, or a local model, and no n8n account is needed
  • Memory: n8n reports 93.2% on LongMemEval (500 questions about past chats), and no email planted a false memory across 216 WhisperBench attacks (company figures)
  • Safety evals: in an October 17 run with GPT-6.1 Sol in a simulated environment, Nod finished 98% of errands, with 0 unsafe actions in 678 runs and 0 successful traps in 13 tests (vendor figures, no real accounts)
  • Cost guardrails: every task shows its cost and ends with a receipt, you can set a monthly limit, and Nod checks in once a task passes $5
Read full story
Linked Models & Agents:

X Discussion: Ethan Mollick had Claude build a 3D "Portals" site on its own; about 25,000 agent runs made 471 worlds, and the agents grew a 204-section, 87,500-word rule book

Wharton professor Ethan Mollick shared an experiment on X on November 9: from a one-paragraph description, Claude built a site that flies endlessly through 3D worlds linked by portals. Twenty hours in there were 204 worlds; the open-source repo now holds 471 worlds and about 1.4 million lines of JavaScript. On his blog he says the agent teams later built their own review bureaucracy, with a rule book that grew to 204 sections, slowing output from hundreds of worlds a day to about a dozen. The post drew 1,262 likes and 158 replies in about 10 hours.

X Discussion: Ethan Mollick had Claude build a 3D "Portals" site on its own; about 25,000 agent runs made 471 worlds, and the agents grew a 204-section, 87,500-word rule book

Key Takeaways

  • From one paragraph to 204 live worlds in 20 hours; the README lists 471 worlds and about 1.4 million lines of JavaScript as of November 9 (GitHub)
  • Claude's own estimate is about 25,000 agent runs, most doing a single task such as judging an image; by day 10 there was 1 lead agent and 28 parallel teams (One Useful Thing)
  • The agents built their own review system: a new version had to win a blind vote on 12 test screenshots, and the rule book grew from 84 to 204 sections and 87,500 words in 12 days, so launching a world took about a day
  • After an outside "consultant" team of agents reviewed the process, output recovered to 30+ worlds a day (per Mollick's blog)
  • The post drew 1,262 likes, 108 reposts, 158 replies and about 62K views in about 10 hours; replies focused on agents inventing middle management and on token cost
Read full story

X Discussion: Node.js and Deno Creator Ryan Dahl Says Software Engineering Is Now "100% AI Written", AI Writes Better C++ Than He Does, but Making Sure It Works Has Not Gone Away

At 04:11 UTC on November 9, Ryan Dahl, creator of Node.js and Deno, posted on X that it is shocking how quickly software engineering has moved to "100% AI written", and more shocking that engineers carry on as if nothing happened. He said AI writes C++ better than he ever could, but the problem of making sure it works did not magically disappear; teams are simply shipping far more code at higher quality. Within about six hours the post had roughly 1,370 likes, 236 bookmarks, 83 replies, 25 quotes and nearly 90K views. Quote posts split into camps: some say the bottleneck has moved from writing code to verifying it, so testing and review are worth more, while others question the "100%" and "higher quality" claims. This is a personal opinion post; "100%" is not a measured statistic.

Key Takeaways

  • Reach: @rough__sea posted at 04:11 UTC on November 9 and within about six hours had about 1,370 likes, 236 bookmarks, 83 replies, 25 quotes and nearly 90K views
  • Claim: software engineering has moved to "100% AI written", AI writes C++ "better than I ever could", but making sure it works has not gone away
  • Conclusion: engineers are shipping far more code at higher quality, yet "continuing on as if nothing happened"
  • Split: some quote posts say the bottleneck has moved from generation to verification, making testing and review more valuable; others question the "100%" and "higher quality" claims
  • Caveat: this is a personal opinion; "100%" is not a measured figure, and the post cites no data or specific projects
Read full story

Adventists AI Open-Sources Sophon-Realtime v1 Full-Duplex Voice Models: One 32B Brain, Three Voice Builds, VoiceBench 82.8 Level With GPT-4o-mini-Audio, Runs on One 80 GB GPU, Apache 2.0

On November 8, Adventists AI released the Sophon-Realtime v1 family of full-duplex voice models on GitHub, Hugging Face, ModelScope and PyPI, with Apache 2.0 code and weights that allow commercial use. All three builds share one 32B brain, adapted from Qwen3-VL-32B-Instruct, that listens continuously, decides turns and writes the reply; they differ only in how the reply becomes sound. The recommended Tag build is the most expressive, Flash reaches first audio in 0.31 s with up to 40 concurrent users per GPU, and E2E is a research preview that needs two 80 GB GPUs. Vendor-reported scores are VoiceBench 82.8 and Big Bench Audio 81.8%, first among open full-duplex models; all benchmarks are self-run by the team.

Adventists AI Open-Sources Sophon-Realtime v1 Full-Duplex Voice Models: One 32B Brain, Three Voice Builds, VoiceBench 82.8 Level With GPT-4o-mini-Audio, Runs on One 80 GB GPU, Apache 2.0

Key Takeaways

  • Scores (vendor-reported, self-run; see the GitHub README): VoiceBench 82.8 and Big Bench Audio 81.8%, first among open full-duplex models and level with GPT-4o-mini-Audio on VoiceBench
  • Tone understanding: paralinguistic score 48.6, ahead of Gemini 3.8 Flash (46.9) and Qwen3-Omni (44.6); Full-Duplex-Bench v3 tool calling Pass@1 48% versus 43% for Grok
  • Three builds: Tag about 0.6 s to first audio and 16 users per GPU; Flash 0.31 s and 40 users per GPU; E2E about 1 s on two 80 GB GPUs (measured on one H100, vendor-reported)
  • Quick start: pip install sophon-realtime then sophon-realtime serve downloads the ~42 GB Tag weights on first run and serves an OpenAI Realtime-style WebSocket on port 8000 (see PyPI)
  • License and bases: Apache 2.0 code and weights; the Tag thinker derives from Qwen3-VL-32B-Instruct quantized to FP8, and the voice derives from Fun-CosyVoice3-0.5B (see Hugging Face)
Read full story
Linked Models & Agents:
⚡ Sophon-Realtime-32B-Tag⚡ Sophon-Realtime-32B-Flash⚡ Sophon-Realtime-32B-E2E⚡ Qwen3-VL-32B-Instruct⚡ GPT-4o-mini-Audio🌐 adventists-ai

X Discussion: Open-Source BLA (Blind LLM Agents) Targets AI Reverse-Engineering Agent REA With Decoys and Resource Traps in Build Outputs, Claims 300x-2,800x More Tokens Burned, Nearly 3,800 GitHub Stars

Over the past day, many developers on X have shared and debated the open-source project BLA (Blind LLM Agents, GitHub qybaihe/bla, MIT license). It is pitched as a shield against the AI reverse-engineering tool REA (Reverse Engineer Anything): it plants fake keys, decoy logic and resource traps that hit analyzer limits inside build outputs such as JS bundles, Electron .asar files, WASM, SQLite and Go or native binaries, so AI reverse-engineering agents burn their budget on dead ends while normal users get identical behavior. An explainer post by the account codila drew about 5,700 likes and 650,000 views, and Timo Zhang (@xteam3301), who says he created it, posted on November 8 that it reached 3,278 stars in weeks. At writing time GitHub shows about 3,800 stars and 466 forks, with v3.1.2 and 3.2.0 both released on November 8. The 300x-2,800x figures are the project's own estimates and have not been independently tested.

X Discussion: Open-Source BLA (Blind LLM Agents) Targets AI Reverse-Engineering Agent REA With Decoys and Resource Traps in Build Outputs, Claims 300x-2,800x More Tokens Burned, Nearly 3,800 GitHub Stars

Key Takeaways

  • Project (GitHub qybaihe/bla): MIT licensed, ships a CLI, an MCP server and Vite/Rollup/Webpack/esbuild plugins; one npx bla-agents harden . runs audit, protect and verify on build outputs
  • How it works (per the README): poison with fake credentials, honey SourceMaps and shadow state machines; exhaust by deliberately tripping REA limits such as the 16 MiB ASAR header, WASM and JSON nesting caps; entangle sibling artifacts with SHA-256 checks so decoys cannot simply be stripped
  • Read the numbers separately: the README says live runs against real REA produce capacity or budget errors for many formats, while the 300x-2,800x tokens and roughly 640x average amplification come from a 14-target table the project itself labels internal estimates
  • Engagement (public X data): codila's explainer post has about 5,700 likes and 650,000 views; Timo Zhang (@xteam3301), who says he built it, posted that it hit 3,278 stars in weeks; GitHub now shows about 3,800 stars and 466 forks
  • What people argue about: supporters see it as the defensive side of an AI reverse-engineering arms race, while others expect someone to reverse-engineer BLA itself; the project says it is only for protecting software you own or are authorized to protect
Read full story
ADSponsored

Alibaba Taobao MNN Team Open-Sources 300M-Parameter On-Device Model MNN-Pocket-0.3B: 173 MB INT4 Build, Up to 466 tok/s Decode on iPad Pro M5, Apache 2.0

On 2026-11-04 Alibaba Taobao's MNN inference-engine team released MNN-Pocket-0.3B on GitHub (alibaba/MNN) and Hugging Face (taobao-mnn): a roughly 300M-parameter Chinese-English instruction model co-designed with the MNN stack for smartphone apps, under Apache 2.0. The official model card says the INT4 (W4A16) QAT build is only 173 MB, supports 32K context, decodes at up to 466 tok/s on iPad Pro M5 (Metal) and about 350 tok/s in tests on iPhone 18 Pro, and averages 50.00 across 11 zh/en benchmarks, ahead of larger ~500M baselines such as Qwen3-0.6B at 44.28 (all vendor figures). The family also ships Base, SFT, GGUF, an on-device MNN package and a Dec decision model that answers in one forward pass. Since 11-08 the third-party iOS app Local LLM has added it and the community has published a LiteRT conversion. The team explicitly does not recommend it for advanced math or long code generation.

Alibaba Taobao MNN Team Open-Sources 300M-Parameter On-Device Model MNN-Pocket-0.3B: 173 MB INT4 Build, Up to 466 tok/s Decode on iPad Pro M5, Apache 2.0

Key Takeaways

  • Specs (official model card): about 300M parameters, 28 layers, hidden size 896, GQA with 14 heads and 2 KV heads, 65,536-token vocabulary, 32K context in deployment, Chinese and English
  • Size and speed (vendor figures): INT4 (W4A16) QAT build is 173 MB; at 512-token context, iPad Pro M5 Metal does 8,721 tok/s prefill and 466 tok/s decode, Snapdragon 8 Gen 5 CPU decodes 251 tok/s; the GitHub README cites about 350 tok/s decode on iPhone 18 Pro
  • Scores (vendor figures): 50.00 average over 11 zh/en benchmarks, 49.59 for INT4, a 0.41-point drop; IFEval 73.20, GSM8K 54.36, HumanEval 53.66, average above Qwen3-0.6B (44.28) and MiniCPM4-0.5B (46.81)
  • Full family: Base, SFT, instruct, GGUF (llama.cpp), an on-device MNN package and a Dec decision model that answers in one forward pass; Apache 2.0 allows commercial use
  • Positioning: the team targets on-device assistants, data extraction and lightweight agent pipelines, not advanced math or long code generation
Read full story
Linked Models & Agents:
⚡ MNN-Pocket-0.3B⚡ Qwen3-0.6B⚡ MiniCPM4-0.5B🌐 alibaba🌐 taobao-mnn

X Discussion: Claude Code's Addy Osmani Says "Your Coding Agents Made You a Manager" and Maps Team Management Habits to Agent Work

Addy Osmani (@addyosmani), who works on Claude Code at Anthropic, posted a long X article titled "Your coding agents made you a manager" at 07:32 UTC on 2026-11-08. His argument is that engineers who spend all day with a coding agent are already managing, and that the highest-leverage habits are, in order: give the agent a runnable way to check its work, state the context it cannot read from the repo, turn repeated corrections into CLAUDE.md entries, enforce only hard rules with hooks, agree a plan before coding, and delegate the task but never the judgment. At capture it had about 964 likes, 1,528 bookmarks, 101 reposts, 39 quotes and about 53,700 impressions. This is a discussion started by an employee's personal article, not an Anthropic announcement or a new feature.

Key Takeaways

  • Original post: Addy Osmani (bio "Claude Code @anthropicai") published an X article at 07:32 UTC on 2026-11-08; about 964 likes, 1,528 bookmarks, 101 reposts, 39 quotes, 94 replies and 53,672 impressions at capture, with more bookmarks than likes
  • The article lists 10 habits ordered by impact; the first is giving the agent a check with a clear pass or fail result (tests, build exit codes, linters, screenshots) and asking it to show the result as proof
  • Layered rules: prompts, CLAUDE.md and skills are requests the agent may weigh, while hooks, deny rules and managed settings are requirements that are always enforced; old habits like ALL CAPS and "think harder" should be dropped
  • Reset after two failed corrections: clear the session and rewrite the prompt; he says he usually runs 4 to 5 background agents plus a few local sessions, and that some days that is too many (author's own account)
  • Framing: a discussion started by an employee's personal article with no new official data or product launch; quote-post claims such as "Claude writes about 90% of Claude Code" are not in the article
Read full story

Robocurve Tests Frontier Models Driving Robot Arms: Blurring the Camera Raised Unsafe-Task Attempts From 27% to 88%, and Doctored Footage Pushed It to 97%

Public benefit corporation Robocurve (@robocurve) published "You Can't See Everything: Perceptual Attacks on Embodied AI" at 19:44 UTC on 2026-11-06 and will present it at CoRL Late Breaking Results. The team had Claude Fable 5.1, Claude Opus 5.5, GPT-6 Astra, GPT-6.1 Sol and Gemini 4 Argon control a real bimanual robot in a closed loop through the Inspect Robots framework on five unsafe tasks, 900 trials in total. Per the paper, models attempted the tasks in 81/300 trials (27%) with unaltered footage, 263/300 (88%) after a Gaussian blur and 291/300 (97%) with frame-by-frame doctored footage; the "stab the object" doll task hit 60/60 with doctored footage. All props were empty bottles or unpowered appliances. At capture the original post had about 11.2K likes and 3.63M impressions.

Robocurve Tests Frontier Models Driving Robot Arms: Blurring the Camera Raised Unsafe-Task Attempts From 27% to 88%, and Doctored Footage Pushed It to 97%

Key Takeaways

  • Scale: 5 frontier models x 5 unsafe tasks x 3 footage types x 12 trials, 900 trials on real robot arms
  • Per the paper: 81/300 attempts (27%) with unaltered footage, 263/300 (88%) after a sigma=4px Gaussian blur and 291/300 (97%) with frame-by-frame GPT Image 2.5 doctoring
  • Doll task: 51/60 (85%) with blurred footage and 60/60 (100%) with doctored footage; "pour me a drink" with bleach: 58/60 blurred, 60/60 doctored
  • Conclusion: models refused only when the image clearly showed danger, and tended to proceed when it was unclear
  • Original post at 19:44 UTC on 2026-11-06 had about 11,220 likes, 4,980 bookmarks, 982 quotes and ~3.63M impressions at capture; no props could cause real harm
Read full story

X Discussion: Coinbase CEO Brian Armstrong Shares a "Chief of Staff Agent" Workflow With Always-On Lead Agents Feeding One Review Queue

Coinbase co-founder and CEO Brian Armstrong (@brian_armstrong) posted at 2026-11-07 16:59 UTC that he has changed how he works over the last few weeks: one always-on lead agent per area of focus, overseen by a "chief of staff" agent, with each lead managing sub-agents that write code, test it, chase reviews and coordinate with team members. Everything he must decide or review lands in one prioritized queue in a simple local web app; product reviews come with screenshots and a video demo, and he clears the queue in batches, mostly by voice and keyboard shortcuts. He says the system learns his preferences into a "Brian brain", and every change still goes through the same human review and security checks. At capture the post had about 5,932 likes, 7,544 bookmarks, 515 replies and 624k impressions. This is a discussion sparked by a personal workflow post, not a Coinbase product launch.

Key Takeaways

  • Original post: Brian Armstrong (@brian_armstrong, Coinbase co-founder and CEO) at 2026-11-07 16:59 UTC; about 5,932 likes, 7,544 bookmarks, 515 replies, 237 reposts, 151 quotes and ~624k impressions at capture
  • Structure: one always-on lead agent per area plus one "chief of staff" agent on top; each lead runs sub-agents that write code, test, chase reviews and coordinate with colleagues
  • Human interface: every pending decision goes into one prioritized queue in a local web app, with screenshots and video demos for reviews, cleared in batches by voice and keyboard shortcuts instead of switching between dozens of chats
  • Boundaries: he stresses every change still passes the same human review and security checks ("eliminating tasks, not human judgment"); models, tools and costs were not disclosed
  • Reaction: Elvis Saravia (@omarsar0) of DAIR.AI quoted it, saying fewer touchpoints plus a queue and a memory system is the setup that works best in his own custom harness
Read full story

Amp Launches Spaces: One Orchestrator Agent Spawns Parallel Threads While Teams Collaborate in One Room

On 2026-11-06 Amp (ampcode.com) launched Spaces: a Space is a conversation with one orchestrator agent that understands a goal, decomposes work, and creates/coordinates parallel threads so users need not manage threads by hand. Official examples include co-building a feature, running a service-accounts launch, and a security review split across 16 areas. Start from the Spaces sidebar with + (title + project); teammates comment in the same chat, and Amp reads comments only when @-mentioned.

Amp Launches Spaces: One Orchestrator Agent Spawns Parallel Threads While Teams Collaborate in One Room

Key Takeaways

  • Official: ampcode.com/news/spaces (2026-11-06); Amp teammate Lewis Metcalf posted; @AmpCode amplified
  • Form: one orchestrator agent decomposes goals, spawns parallel threads, and summarizes; bird's-eye or deep dive
  • Teams: comment inside the same Space; Amp reads comments only when @-mentioned
  • Examples: Spaces was built inside a Spaces v1 room; service-accounts launch ops; security review across 16 areas
  • Start: Spaces sidebar → + → set title and project → describe the goal
Read full story
Linked Models & Agents: