Agents

All topics

Models that plan, call tools and finish multi-step tasks on their own — from Claude Code and Manus to agent frameworks and benchmarks.

1,465 picksRelated topicsMCP & tool use AI coding Reasoning

Latest picks

1281–1300 of 1,465

Apr 19Sunday

Xinzhiyuan · WeChatApr 19, 12:10

Amap unveiled ABot-Claw and its quadruped robot Tutu at the Yizhuang Half Marathon

Amap unveiled the ABot-Claw agent system and the quadruped robot Tutu, claiming an autonomous guide-dog demo in the 2026 Yizhuang robot half marathon. The post gives three concrete numbers: ABot-M0 reached 80.5% on Libero-Plus, nearly 30% above Pi0; ABot-N0 hit SOTA on 7 navigation benchmarks; the open UniACT dataset contains 6 million trajectories and 9,500+ hours. What matters is Map as Memory, cloud-edge control, and closed-loop self-correction; the post does not disclose race ranking, pricing, or launch timing.

Why it matters: HKR-H/K/R all pass: the open-environment half-marathon demo is a strong hook, and the post includes concrete benchmark numbers plus a 6M-trajectory release. Kept below p1 because rank, pricing, ship date, and independent replication are not disclosed, and the impact is narrower a

Take

Amap did not just show a quadruped doing a flashy public demo. It proposed a system architecture that treats the map as a persistent memory layer for robots. I buy that framing more than the half-marathon headline. The article gives three concrete numbers: ABot-M0 hit 80.5% on Libero-Plus, nearly 30% above Pi0; ABot-N0 claims SOTA on 7 navigation benchmarks; UniACT is open-sourced at 6 million trajectories and 9,500+ hours. Those are solid signals. More important, though, is that Amap is trying to solve the runtime problem robotics keeps dodging: how a robot keeps context across environments, devices, and interruptions.

That is why this caught my attention. A lot of embodied AI over the last year has centered on better manipulation models, better VLA demos, better single-agent autonomy. Figure, 1X, Physical Intelligence, and the Google DeepMind robotics work all push some version of that line. The missing layer has been shared world knowledge that survives beyond one robot, one map, one run. Amap has a natural advantage here because it already owns a large-scale mapping stack. Plugging POIs, road graphs, functional spaces, and spatial semantics directly into the agent memory is a different bet from the usual lab-born robotics pipeline. In plain terms, many teams are teaching the robot to place a cup into a drawer. Amap is trying to teach it where the drawer is, whether the corridor is blocked today, and whether a different robot body can inherit that knowledge tomorrow.

I still have real doubts about the “end of one-robot-one-map” claim. Shared memory is not hard because of storage. It is hard because of freshness, trust, and embodiment mismatch. If robot A saw an obstacle near the elevator two days ago, should robot B trust that observation now? A quadruped, a wheeled base, and a humanoid do not share the same traversability constraints even if they share the same coordinates. The piece talks about joint indexing, hybrid retrieval, and zero-transfer inheritance, but it does not disclose the ugly metrics that matter: map staleness tolerance, localization drift, cross-robot calibration cost, behavior under network loss, or how the system degrades when cloud planning disappears. It also does not disclose the race ranking, the distance conditions, or intervention counts in the guide-dog demo. The title sells “legendary.” The body skips the operational numbers that would make that claim credible.

There is also the usual benchmark-to-deployment wall. Libero, RoboCasa, and RoboTwin are useful references for manipulation generalization, but open urban environments add layers of noise those benchmarks do not capture: crowds, moving obstacles, weather, construction, unreliable signage, social navigation constraints, and bad edge cases around safety. Getting SOTA on 7 navigation benchmarks is good. It does not tell me the remote takeover rate. Embodied AI has taught this lesson repeatedly. Once you leave the benchmark world, engineering eats the leaderboard.

Still, I take this seriously because Amap is pushing on a systems layer that the field underrates. Robots are not going to scale just by making the base model bigger. External memory, mapping infrastructure, cloud-edge task division, and closed-loop self-correction are the boring parts that decide whether deployment survives contact with reality. That part of the narrative is stronger than the marketing around AGI or “Harness.”

If Amap wants ABot-Claw to be seen as infrastructure rather than a polished demo stack, it needs to publish three things next: intervention rate and task success in open environments, performance drop when transferring memory across robot types, and latency plus error-recovery stats for memory updates. Without those, this is an ambitious systems manifesto. With them, it starts to look like one of the more credible embodied AI plays from a company that already owns a real-world spatial graph.

r/LocalLLaMAApr 19, 09:59

I tested 8 LLMs as tabletop GMs: a 27B model beat the 405B on narrative quality

The author tested 8 LLMs on 6 fixed tabletop-GM scenarios, and google/gemma-3-27b-it ranked first in narrative quality with a 4.33 overall score. The probe used 8 auto metrics plus 3 LLM-judge scores, and the full run cost about $0.02; the title says a 27B beat a 405B, but the snippet does not disclose the 405B model name or full rankings.

Why it matters: A named first-person benchmark with a strong surprise hook clears HKR-H, HKR-K, and HKR-R. I kept it at featured, not higher: the source is Reddit, the post is truncated, and the 405B model name plus full ranking are not disclosed.

Take

Gemma-3-27B-it winning this GM probe is plausible, but the “27B beat 405B” framing is doing too much work. The evidence is narrow: 6 fixed tabletop-GM scenarios, 8 automatic metrics, 3 LLM-judge dimensions, a total run cost around $0.02, and a 4.33 overall score for the winner. The Reddit body is blocked by 403, so the 405B model name and full ranking are not disclosed.

I’d read this as a taste test for narrative control, not a clean scale result. Gemma models have often been good at concise, obedient prose, and GM tasks reward exactly that: tone, pacing, NPC consistency, and not rambling past the scene. A Llama 3.1 405B-style model can lose that kind of beauty contest if the judge likes tighter prose. Without human player blind tests and multi-turn state tracking, this benchmark says the prompt suite is neat; it does not prove 27B generally beats 405B.

r/LocalLLaMAApr 19, 07:22

Deep dive into LangGraph’s Pregel execution model, checkpointing internals, and DeepAgents

A technical post breaks down LangGraph as a high-level wrapper over a Pregel runtime, with PregelNodes, channels, and reducers as the core primitives. The RSS snippet cites four Postgres checkpoint tables, a Plan/Execute/Update superstep flow, and compile() preflight validation; the post does not disclose benchmark numbers in the snippet. The real takeaway is the unified runtime view of parallel execution, checkpoint write amplification, and subgraph boundaries.

Why it matters: HKR-H/K/R all pass: the post reframes LangGraph as a Pregel runtime and adds concrete internals like 4 checkpoint tables and Plan/Execute/Update supersteps. Kept at 74 because this is a Reddit deep dive, not an official release, and no benchmark or production case is disclosed.

Apr 18Saturday

QbitAI · WeChatApr 18, 19:51

OpenClaw has reached the milk tea business

Guming and Intime Retail said OpenClaw tests exposed 5 deployment risks: default port 18789 exposure, at least 8% malicious Skills, privilege overreach, 20+ minutes of runaway token use, and weak legacy defenses. Reported incidents include an agent closing a normal bastion-host port and locking out ops staff, plus requests for unrelated permissions like microphone access. The real issue is not chat UX but agents touching enterprise networks, credentials, and production systems.

Why it matters: This is not generic AI-safety commentary; it documents five concrete deployment risks and one ops outage, so HKR-H/K/R all pass. It stays below P1 because the evidence is still case-level testing, with no official fix, broad rollout impact, or cross-source cluster.

Take

OpenClaw’s enterprise risk is no longer bad answers; it is agents taking actions inside production systems. The summary names five failure modes: default port 18789 exposure, at least 8% malicious Skills, privilege overreach, 20-plus minutes of runaway token calls, and legacy perimeter defenses failing. The ugly incident is concrete: an agent closed a normal bastion-host port and locked ops staff out company-wide. Microphone permission requests add the same smell: the permission model still looks like mobile-app thinking.

I don’t buy the easy “low-friction automation” pitch here. Claude Computer Use and OpenAI Operator are constrained by sandboxes, confirmations, and narrow scopes. OpenClaw inside enterprise networks needs least privilege, rollback, and audit trails before anyone celebrates adoption in Guming or Intime Retail.

Synced · WeChatApr 18, 18:24

What is OpenAI prioritizing under compute limits?

Greg Brockman said OpenAI narrowed priorities under hard compute limits to two bets: a personal assistant and AI workers that solve hard user problems, and current compute cannot fully support both. The snippet says Sora resources were reduced while focus shifted to reasoning models, a unified AI layer, and the next base model Spud; it does not disclose the claimed compute budget, timeline, or model specs. The key point is not a B2B retreat but a compute-driven reprioritization.

Why it matters: HKR-H/K/R all pass: the compute-ceiling angle is strong, the piece adds concrete priority shifts, and OpenAI roadmap triage hits cost and dependency nerves. It stays at 80 because this is secondary reporting; spend, timing, and technical details are not disclosed.

Take

OpenAI’s priority cut exposes the uncomfortable constraint: the consumer assistant and paid AI workers cannot both get unlimited compute. The summary says Greg Brockman narrowed the company to two bets: a personal assistant and AI workers that solve hard user problems. It also says current compute cannot fully support both, Sora resources were reduced, and focus moved to reasoning models, a unified AI layer, and the next base model Spud. The article body is blocked by WeChat verification, so the claimed compute budget, timeline, and Spud specs are not disclosed.

I don’t buy the “B2B retreat” framing. OpenAI is still fighting for the ChatGPT personal entry point; it is just pushing aside flashy, GPU-hungry, lower-frequency video generation first. Anthropic has been cleaner about steering Claude into enterprise agent workflows. OpenAI has the harder conflict: one company wants daily consumer usage and high-margin AI labor at the same time, and the compute ledger is now deciding product strategy.

Xinzhiyuan · WeChatApr 18, 18:15

Claude Opus 4.7 splits users 48 hours after launch: benchmark lead, reasoning tests drop

Anthropic's Claude Opus 4.7 drew split reactions within 48 hours: Artificial Analysis scored it at 57, tied for No.1, while NYT Connections Extended fell from 94.7% on 4.6 to 41.0%. The post says a new tokenizer raises token usage to 1.0-1.35x on the same text, and old thinking parameters can return 400 errors; Anthropic also cites a 1753 Elo GDPval-AA score, 79 points above No.2. The real issue is migration cost and capability trade-offs, not a single leaderboard.

Why it matters: The signal is not the “backlash” framing but the four concrete shifts: benchmark lead, reasoning drop, higher token use, and API breakage. HKR-H/K/R all land, but this is secondary analysis 48 hours after launch, not the primary Anthropic release, so it stays below p1.

Take

Anthropic shipped Claude Opus 4.7 to the top of one leaderboard within 48 hours, and straight into 400 errors for existing workflows. My read is blunt: this was not a simple capability upgrade. It was a rewrite of the product’s objective function. Anthropic appears to have pushed Opus away from “high-end assistant that feels smooth” and toward “more literal, more refusal-prone, more optimized for knowledge-work evaluation.” The numbers in the article support that interpretation. GDPval-AA is cited at 1753 Elo, 79 points above No.2, and hallucination rate is said to drop to 36%. The backlash also has hard evidence behind it. NYT Connections Extended falls from 94.7% on 4.6 to 41.0% on 4.7. MRCR v2 reportedly drops from 78.3% to 32.2%. Same text can consume up to 1.35x tokens. Old thinking parameters can throw 400s. That is not a minor “vibes changed” story. That is a product contract changing under load.

What bothers me most is not that some scores went up and others went down. It’s that Anthropic bundled several painful changes into one release. The article names three of them clearly: tokenizer inflation of 1.0-1.35x on the same text, breaking changes from thinking={enabled,budget_tokens} to adaptive/effort, and hidden thinking by default while billing still applies. You can defend each change in isolation. Tokenization changes happen. Reasoning controls evolve. Logging defaults get tightened. But power users do not buy abstract intelligence. They buy predictability. If the unit price stays flat while the bill rises, if the model name changes by one decimal while behavior boundaries shift, and if observability gets worse while spend stays the same, trust takes the hit.

There’s industry context the piece doesn’t really unpack. OpenAI already ran into a version of this during the GPT-4 Turbo “faster but dumber” episode. One lesson many applied teams took from that mess was not “never upgrade,” but “never let the default model roll into production silently.” I’m going from memory here, but over the last year a lot of coding-agent teams started pinning model versions and running regression suites before routing traffic. Products like Cursor, Windsurf, and Aider are sensitive to model drift for a simple reason: code is not chat. Small shifts in refusal policy, planning depth, or literalness can wreck patch quality, test pass rates, and edit locality. Anthropic’s problem here does not look like a model suddenly got dumb across the board. It looks more like the reward was pulled hard toward enterprise-safe and benchmark-safe behavior, then released as if existing users would absorb it.

I also have some doubts about how much weight to put on GDPval-AA in this particular debate. A 1753 Elo and a 79-point lead are impressive on paper. But that benchmark measures knowledge work across 44 occupations and 9 industries. That matters, especially for a vendor selling expensive API access into enterprise workflows. It does not automatically map to your refactor task, your debugging loop, your long-chain reasoning prompt, or your agent harness. The article says hallucination improved by 25 points largely because the model declines to answer more often. That tends to help in enterprise QA and compliance-heavy settings. In day-to-day collaboration, users often experience the same behavior as stubbornness, extra turns, or brittle literalism. That does not mean users are irrational. It means the benchmark is not capturing workflow friction.

I’m even less convinced by the article’s softer explanation for the “combative” reports. Saying Opus 4.7 is just more literal only explains part of it. Literal execution can change tone and refusal patterns. It does not naturally explain a collapse from 94.7% to 41.0% on NYT Connections Extended. That scale of drop smells like a deeper issue in reasoning-budget allocation, search strategy, or tokenizer interaction with the reasoning stack. The body does not provide the system-card ablations needed to sort that out. I haven’t verified whether Anthropic has published a detailed breakdown of how high-reasoning mode differs internally between 4.6 and 4.7. Without that, blaming prompt ambiguity is too convenient.

I also don’t fully buy the “reputation collapsed in 48 hours” framing. Reddit backlash, a few prominent reversions, and angry power users tell you something real about the top end of the user base. They do not prove the market has rejected the model outright. Anthropic has recovered from rough releases before by fixing bugs, improving docs, and adjusting rate limits. But the tension exposed here is real and bigger than one release. Labs increasingly ship each model version as a multi-objective optimization package. Users increasingly treat those models as stable dependencies. Those two clocks are no longer aligned.

So for me, the important question is not whether Opus 4.7 is “better” or “worse” in some universal sense. It’s that Anthropic has moved Claude’s product definition. It seems more willing to trade away smoothness on some developer tasks for stronger scores in broader knowledge-work evaluation and safer non-answer behavior, while pushing migration cost onto users. If Anthropic does not add a better compatibility layer after this—longer support for 4.6, tokenizer cost estimators, clearer reasoning controls, stronger migration tooling—developers will learn the obvious lesson: never trust the default upgrade, always rerun the regression set. For a company that wants enterprise and agent workloads, that lesson is expensive.

Xinzhiyuan · WeChatApr 18, 18:15

Bilibili debate: Hermes responds to plagiarism claims for the first time, as MiniMax moves early on Harness

MiniMax says its M2.7 model now handles 30%-50% of daily workflows in its RL team, ran over 100 self-optimization loops, and improved evals by 30%. The post also says Hermes Agent grew from 2B to nearly 300B daily tokens, while M2.7 exceeds 25B daily tokens on OpenRouter; Hermes lead Tommy Eastman denied copying EvoMap in a livestream. The real signal is Harness: the post cites 20-40ms or 80ms sandbox startup and 15k to 600k instances per minute, showing competition is shifting from benchmark scores to agent execution infrastructure.

Why it matters: HKR-H/K/R all pass: the plagiarism-response angle pulls clicks, and the story carries concrete metrics on workflow share, self-optimization loops, sandbox latency, and concurrency. It stays at 83 because this is a dense secondary report, not a primary launch or official technical

X · @doteyApr 18, 10:23

Anthropic designer Ryan Mather shares Claude Design tips while covering 7 product lines

Anthropic designer Ryan Mather shared 9 Claude Design workflow tips while covering 7 product lines. The RSS snippet says to spend 1 hour building a design system, use chat for large changes, comments for small edits, specify feedback like 8px spacing, and attach only the target component folder instead of a full monorepo. The key shift is process: from human-do/human-review to Claude-do/human-review.

Why it matters: This is a strong practitioner workflow note: an Anthropic insider shares concrete, reusable tactics, so HKR-H/K/R all pass. It stays below the 80s because this is not a formal Claude product release and the post does not disclose harder outcome data such as time saved or task win

Hacker News front pageApr 18, 05:03

Show HN: AI Subroutines – Run automation scripts inside your browser tab

rtrvr.ai introduced AI Subroutines, which turn a recorded browser task into a callable tool and replay it at zero token cost and zero LLM inference delay. The script runs inside the active tab, reusing auth, CSRF, TLS sessions, and signed headers; recording trims about 300 requests to about 5 and falls back to DOM-only when GraphQL operation IDs are volatile. The part to watch is batching: one LLM call can assign parameters for a 500-row sheet and launch 500 subroutines.

Why it matters: This clears HKR-H/K/R: the hook is zero-token browser automation, the post gives concrete mechanics (300→5 requests, DOM fallback, 500-row fan-out), and it hits agent reliability/cost pain. Kept to mid-featured because it is a single-company Show HN post, not a market-wide event.

Take

rtrvr.ai’s move is sharp because it turns repeated agent work into one inference plus replay, rather than better click planning. The mechanism is concrete: the extension patches fetch/XHR in the MAIN world, uses Chrome webRequest as fallback, then trims roughly 300 captured requests to the top five using origin, 800ms click correlation, mutating method weight, and 2xx response quality. Those candidates fit into a 12,000-character generation context. The bulk case is the killer: one LLM call assigns parameters for a 500-row sheet, then fires 500 Subroutines.

I don’t buy the “100% deterministic” wording. The article admits volatile GraphQL queryId, doc_id, and operationHash cases fall back to DOM-only. So the product still inherits frontend churn. This smells less like general web-agent progress and more like Zapier-style determinism smuggled into logged-in browser state.

Apr 17Friday

Xinzhiyuan · WeChatApr 17, 21:10

Behind OpenClaw's surge, only 8.6% of users detect anomalies: a multi-university empirical study

NTU, KTH, and William & Mary ran a 303-person study and found only 8.6% noticed agent-mediated deception, while 2.7% identified the mechanism correctly. Using 9 HAT-Lab task scenarios, interactive interruption alerts raised detection to 25%, while static warnings were seen by about 24%. The key issue is human-agent cognitive failure, not just model bugs.

Why it matters: Strong HKR-H/K/R: the 8.6% detection hook is sharp, and the 303-person, 9-task study plus 25% alert lift gives testable detail. This is a solid agent-safety research release, not a market-moving product, model, or policy event, so it lands in featured, not p1.

Xinzhiyuan · WeChatApr 17, 21:10

Yixin says its finance Agent harness runs single tasks for 16 hours and plans an H2 open-source release

Yixin says its finance Agent harness can run a single task for 16 hours across 12 sessions, with 65% autonomous delivery. The post adds a 50k-token cap per case, projected approval speedups above 150%, and projected unit cost at one-fifth of human work; it says an open-source release is planned for H2 2026, but does not disclose the repo, license, or reproducible evals. The key signal is governance design, not the “smarter over time” framing.

Why it matters: This clears HKR-H/K/R with a rare production claim: a finance agent runs 16 hours, spans 12 sessions, hits 65% autonomous delivery, and stays under a 50k-token cap. It stays below 85 because the evidence is self-reported and the post does not disclose a repo, license, or reproduc

Tencent Technology · WeChatApr 17, 17:36

From Vibe Coding to Agentic Engineering: Rebuilding the Full Backend Development Workflow

Tencent engineers report a one-week practice that used Claude Code plus custom Skills, Commands, and MCP servers to run an 11-stage backend workflow in one terminal session. The post gives reproducible details: one requirement-exploration step used 20 tool calls, 93.8k tokens, and 56 seconds; execution was split into 4 tasks and produced 3 commits. The real point is workflow orchestration, not raw code generation; human review remains at plan, deploy, and review gates.

Why it matters: HKR-H/K/R all pass: the story turns agentic engineering into a measured backend workflow test, with tool-call, token, timing, plan-length, task, and commit data. Stronger than generic coding hype, but still a practitioner case study rather than a major product or model release.

X · @doteyApr 17, 10:53

Seedance 2.0 API is now available on Volcano Engine and BytePlus

Volcano Engine has released the Seedance 2.0 API for enterprises, individual developers, and overseas users via BytePlus; China pricing is RMB 46 per million tokens, or about RMB 1 per second for pure video generation. The post says it supports text, image, audio, and video inputs, plus face verification, portrait authorization, and 10,000+ preset avatars for workflow automation; overseas pricing is not disclosed here. The part to watch is orchestration: the post cites up to 10x efficiency gains, but does not disclose a common benchmark or model specs.

Why it matters: HKR-H/K/R all pass: the overseas rollout is a real hook, and the post includes usable pricing and modality details for practitioners. It stays at 74 because this is an API availability update, not a major model launch, and the post does not disclose model params, benchmark method

Take

Volcano Engine opened Seedance 2.0 API to enterprises, individual developers, and overseas users on BytePlus, with two concrete numbers: RMB 46 per million tokens and about RMB 1 per second for pure video generation. My read is that ByteDance is no longer selling “an AI video model” as a standalone novelty. It is trying to turn video generation into workflow infrastructure. By 2026, demos are cheap. The harder part is packaging identity checks, portrait authorization, avatars, and orchestration into something a team can actually wire into production.

Those two pricing numbers matter for different buyers. RMB 46 per million tokens signals a unified API economy, which developers and platform teams understand. RMB 1 per video second speaks the language of content ops and marketing teams that still budget by asset output. That dual pricing logic matches what the market has been converging toward. Sora started from a product experience and subscription framing. Runway, Pika, and others leaned SaaS. Chinese players such as Kling and ByteDance’s own consumer-facing video tools pushed workstation-style creation flows. Seedance 2.0 flips that into an API product, which tells you ByteDance wants more than creator mindshare. It wants systems integrators, automation vendors, and internal enterprise tooling budgets.

I’m skeptical of the efficiency claims in the article. The post cites nearly 10x production efficiency gains and 70%–90% cost reductions, but the benchmark is not standardized, the task difficulty is not disclosed, and the system details are thin. There is no model size, no throughput disclosure, no concurrency data, no first-frame latency, no maximum duration, and no output resolution breakdown. Without those conditions, “10x” sounds like sales collateral, not an engineering claim. AI video vendors have spent the last year blurring two different stories: model improvement versus pipeline consolidation. If you compress five manual steps into one automated flow, the business outcome improves fast, but that does not mean the base model itself got 10x better. The article mixes those layers together, and I don’t buy that framing at face value.

That said, this launch still matters because ByteDance has one advantage many model vendors do not: distribution plus workflow adjacency. Douyin, ad buying, livestreaming, e-commerce, and BytePlus overseas all create demand for large volumes of variant creative. The OPPO K15 Pro example in the piece says a campaign video crossed 20 million views in 60 hours. That number does not prove model quality by itself. It does show something more practical: people inside ByteDance’s ecosystem are already treating AI video as a scalable asset factory, not a lab demo. A lot of video model companies spent the last year competing on cinematic look, camera motion, or character consistency. ByteDance appears to be competing on whether a customer can generate 500 deployable variants in a day. That is less glamorous, but it is much closer to where budgets live.

I would also push back on the robotics and autonomous driving angle in the article. This narrative has been everywhere over the last year. NVIDIA’s Cosmos line, several world-model projects, and a bunch of synthetic-data startups have all pushed the claim that generated video can fill training data gaps. The problem is simple: visually plausible video is not the same thing as physically valid data. For robotics and AV corner cases, the bottleneck is not whether rain or collisions look realistic. It is whether dynamics, contact behavior, controllable variables, and labels line up in a way that survives sim-to-real transfer. The article says dozens of robotics companies use Seedance 2.0 to generate “physically consistent” interaction data, but gives no reproducible metric. No transfer gain, no success rate delta, no ratio of synthetic data in the final training mix. I haven’t verified any of that myself, so my stance here is cautious: the direction is credible, the evidence in this writeup is weak.

The outside context makes the strategic intent clearer. Over the last year, Alibaba, Kuaishou, MiniMax, Runway, and Luma have all moved to strengthen API and enterprise access, because pure creative tooling hits a ceiling fast. The enduring revenue sits in systems that connect to CRM, marketing automation, customer support avatars, training content generation, and localization pipelines. Seedance 2.0 bundling face verification, portrait authorization, and 10,000-plus preset avatars suggests ByteDance is prioritizing compliance and delivery, not just model theater. Enterprise buyers usually fear legal and approval bottlenecks more than they fear a modest quality drop.

There is another backdrop the article does not spell out. In multimodal APIs over the last year, the visible competition has been quality, but the deeper competition has been standardization of the call chain. OpenAI, Google, and Anthropic pushed toward tool-using agents. Chinese cloud and model vendors leaned into workbench-style enterprise solutions. Seedance 2.0 explicitly mentions agent skills, which tells me ByteDance now treats video generation as one callable step inside a larger agent workflow. I think that is the correct architectural assumption. The open questions are more operational: can the reliability and cost curve hold up under heavy production load, and can BytePlus sell this outside the ByteDance traffic ecosystem? The article does not disclose SLA, queue behavior, failure rates, or overseas pricing details, so those remain open.

So my take is straightforward. Seedance 2.0 API matters because ByteDance is moving video generation deeper into enterprise systems as an orchestrated module. I buy that strategy. I do not think the current writeup proves model leadership, and I definitely do not think it proves that the “world model” story is already delivering measurable value in robotics or autonomous driving. ByteDance probably wins first on integration surface area here. Whether it also wins on raw model strength still needs harder evidence.

X · @op7418Apr 17, 10:44

Seedance 2.0 API is now fully open

Volcano Engine has opened the Seedance 2.0 API to domestic users, while BytePlus serves overseas access; the API currently accepts 4 input modalities: text, image, audio, and video. The post also confirms face registration, portrait authorization, and preset virtual avatars, but does not disclose pricing, rate limits, model variants, or regional availability. The real watchpoint is whether video-agent workflows can be wired through Skills and MCP, not the ecosystem rhetoric.

Why it matters: This is a real product update from ByteDance’s stack: HKR-H on full API availability, HKR-K on 4-modal input and consent mechanics, and HKR-R on builder demand for deployable video APIs. I keep it at 75 because pricing, rate limits, regional rollout details, and quality evidence

Take

Volcano Engine opened Seedance 2.0 API with 4 input modalities—text, image, audio, and video—and that matters because the model is finally moving from demo territory into something developers can wire into workflows. I still think this announcement is incomplete in the places that decide adoption.

My read is simple: ByteDance wants Seedance to sit inside production pipelines, not just inside a flashy creator UI. The post confirms face registration, portrait authorization, and preset virtual avatars. That is a very specific product choice. It points at short-form video operations, digital humans, ad creative, and serialized content assembly. But the post does not disclose pricing, rate limits, output duration, resolution, concurrency, region availability, or model variants. Without those, developers cannot tell whether this is viable for batch generation or only for a few premium use cases.

This is where I push back on the “ecosystem will flourish” angle. Video APIs do not get adopted like text APIs. With text, teams can often tolerate some variance if token economics are clear. With video, three things decide everything: cost per generation, controllability, and rights/compliance. This post gives a partial answer on compliance through face registration and portrait authorization. It gives almost nothing on cost and reliability. That is a big gap.

And “video agent” is a much harder claim than people make it sound. Wrapping a model with MCP or Skills is the easy part. Real video workflows usually break into script generation, shot planning, character consistency, retries, voice-sync, export formatting, and review. If one stage drifts, the pipeline falls back to human operators. I’ve seen this pattern across the last year with video stacks from Runway, Pika, and Luma: the headline model quality gets attention, but production teams end up caring more about repeatability, queue behavior, and rerun costs.

The other thing I don’t buy cleanly is the implied jump from consumer demand to API success. The post cites Hongguo at 300 million DAU. Even if that number is accurate, it proves demand for short drama distribution. It does not prove a third-party developer ecosystem around Seedance API. Those are different markets. A lot of teams will decide they do not need the smartest video model. They need the cheapest stable one that can preserve the same avatar, framing style, and template over thousands of runs.

So my stance is narrower than the post’s enthusiasm. The title gives us full API availability. The body confirms 4-modal input plus identity/portrait features. The body does not disclose the operating facts that determine real adoption: pricing, SLA, throughput, and quality controls. Until those are public, I see this as ByteDance filling in its video infrastructure layer, not proof that video-agent workflows are ready at scale.

最佳拍档 (BestPartners)Apr 17, 07:00

Turn your coworker into a Skill? GitHub viral project and Anthropic Skills explained

The video says the open-source “coworker.skill” project gained over 13,000 GitHub stars in days, but it produces a standardized SKILL.md prompt package, not a digital worker replacement. It gives a timeline: Anthropic launched Claude Skills on Oct 16, 2025, then published Agent Skills as an open standard on Dec 18; the mechanism keeps only a short summary in context until a task matches. The real point is scope: it fits standardized workflows like reports, docs, and code review, while the post does not disclose cross-platform compatibility rates or any settled legal standard.

Why it matters: This clears HKR-H/K/R: the coworker-to-Skill hook is sticky, the post adds dates/stars/mechanism, and the labor/IP angle resonates. I kept it at 76 because it is secondary commentary, not a primary release or first-hand test, and key compatibility/legal facts are still undiscolse

Take

coworker.skill blowing up shows how badly companies confuse workflow packaging with capability capture. The repo hit 13,000 GitHub stars in days, but the output is still a SKILL.md bundle: YAML metadata plus Markdown instructions, loaded only when the task matches. Anthropic shipped Claude Skills on Oct. 16, 2025, then published Agent Skills as an open standard on Dec. 18. That mechanism saves context; it does not manufacture a colleague.

The useful cases are boring: Excel, Word, PDF, PowerPoint, weekly reports, docs, code review checklists. The workplace panic starts when managers demand “employee Skills” and get anti-distillation sludge back: Redis TTL guidance becomes “follow team rules; parameters depend on business context.” That is not knowledge management. That is management mistaking prompt packaging for judgment.

X · @doteyApr 17, 03:59

Boris Cherny shares practical tips from recent heavy use of Claude Opus 4.7

Boris Cherny outlined five ways to use Claude Opus 4.7, centered on Auto mode approving safe commands and a /go skill chaining tests, code simplification, and PR creation. The post names Auto mode, Recaps, Focus mode, effort level, and computer use; pricing, launch date, and benchmark data are not disclosed. The real shift is workflow, not just the model itself.

Take

Opus 4.7’s signal is not raw intelligence; Anthropic is cutting the babysitting cost of agents. The post gives no pricing, launch date, or benchmark data. The hard hook is Auto mode approving safe commands, plus a /go skill that runs end-to-end tests, calls /simplify, and opens a PR. That is a practical stack: fewer permission prompts, more self-checking, and a cleaner “come back in 30 minutes” loop.

I’m still cautious about automatic safety judgment on shell commands. Coding agents over the last year rarely failed because autocomplete was weak. They failed on permissions, stale context, broken test setup, and handoff. Recaps, Focus mode, effort level, browser control, and computer use all target those seams. If Claude Code makes that chain reliable, Opus 4.7 gets more leverage from workflow than from another SWE-bench bump.

r/LocalLLaMAApr 17, 03:41

PSA: Qwen3.6 ships with preserve_thinking. Make sure you have it on.

Qwen3.6 adds a preserve_thinking flag to keep prior reasoning in context and address the KV cache invalidation issue seen with the Qwen3.5 template. The post cites the Qwen3.6-35B-A3B model page and gives a two-turn 20-digit-number test: with preserve_thinking on, the model can return the second number from its earlier reasoning. The practical point is cross-turn reasoning retention for agent and tool workflows; LM Studio does not support it yet, and an oMLX PR is open.

Why it matters: HKR-H, K, and R all pass: the story has a strong hidden-setting hook, a concrete two-turn repro, and a clear nerve for local-model and agent users. I keep it in the low 70s because this is a Reddit PSA rather than a primary release note, and the impact is concentrated in Qwen/OSS

TechCrunch · AIApr 17, 03:18

OpenAI upgrades Codex with more control over your desktop

OpenAI upgraded Codex on April 16, 2026, expanding its desktop control, and the headline frames it as a move against Anthropic. The truncated post only confirms more desktop power for Codex and says Claude Code has become a preferred tool for many businesses; the post does not disclose exact features, pricing, rollout, or permission limits. The key issue is the permission boundary, not the coding-tool label.

Why it matters: TechCrunch reports an OpenAI Codex desktop-control upgrade framed as a direct move against Anthropic, so HKR-H and HKR-R land. But HKR-K is limited: the article confirms broader permissions only, with no action list, pricing, or rollout details, so it stays at the featured floor.

Take

OpenAI expanded Codex’s desktop permissions on April 16, and my read is less “better coding” than “we know Claude Code is winning mindshare where it counts.” The headline explicitly frames this against Anthropic, and the summary says Claude Code has become a preferred tool for many businesses. That matters. Once the fight shifts from code generation to software that can click, edit, run, and navigate local workflows, the moat stops being benchmark scores alone. It becomes permissioning, audit logs, rollback, admin controls, and how much pain security teams will tolerate.

That is also why the missing details matter more than the launch framing. The body here is effectively truncated. We do not have the action scope, default permission model, approval prompts, logging policy, enterprise admin controls, pricing, rollout, or which users get access. Without that, I don’t buy the simple “Codex got more powerful” line. Desktop agents have never been bottlenecked by whether the model can find a button. The hard part is whether the product can contain the cost of mistakes. When Anthropic pushed Computer Use last year, the serious discussion was not “wow, it can use a computer.” It was screenshot-level visibility, step-level authorization, recovery from failure, and blocks on high-risk actions. OpenAI ran into adjacent issues with Operator too: demos looked smooth, but real deployment means session state, credentials, MFA, browser variance, and audit requirements.

I also want to push back a bit on the media narrative. “OpenAI takes aim at Anthropic” is a clean headline, but the competitive gap is not just feature parity. Anthropic’s recent strength with developers came from a reputation that its coding products are less chatty and more dependable in day-to-day work. I haven’t independently verified how broad that enterprise preference is, but the summary’s wording lines up with what many teams have been saying privately. If OpenAI only widens Codex’s action radius without making the control boundary legible, security and IT buyers will slow-roll this. Every extra layer of desktop access adds one more review with internal risk teams.

There’s another unresolved issue: execution environment. The title says Codex gets more power over your desktop, but the body does not disclose whether that means local control, remote execution, or some sandboxed proxy model. Those are completely different risk profiles. Local control is the hardest sell for enterprise security. Sandboxed execution looks cleaner in demos, but it often leaves the last mile of real desktop integration unsolved.

So my take is straightforward. This is not a cosmetic product update. OpenAI is trying to buy its way back into the enterprise agent workflow where Anthropic has built momentum. Whether that works depends less on how many actions Codex can take and more on how narrowly, visibly, and reversibly those actions are governed.

X · @doteyApr 17, 01:30

Codex major update: from a coding tool to an assistant that can operate your computer

OpenAI upgraded Codex into a Mac desktop agent and says it serves 3M+ weekly developers. It can see screens, click, type, run parallel agents, and adds 90+ plugins. Desktop rollout starts now for ChatGPT sign-ins; computer control is macOS-first.

Why it matters: OpenAI expands Codex from coding help into a Mac-operating agent, with parallel agents, 90+ plugins, and a claimed 3M weekly developer base. HKR-H/K/R all pass; missing safety boundary and pricing details keep it in the high-80s, not the 90s.

Take

OpenAI expanded Codex into a macOS desktop agent and said it serves more than 3 million weekly developers; my read is that this is not a coding-assistant refresh, it is OpenAI making a direct grab for the execution layer on the desktop.

The capability list matters because it changes the bottleneck. Screen reading, mouse clicks, keyboard control, parallel agents, browser annotation, SSH to remote devboxes, and 90-plus plugins are useful for one reason: they route around API scarcity. A lot of real software work still lives in tools with weak APIs, no APIs, brittle internal dashboards, or permission-heavy flows. Agent products spent most of the last year getting stuck at exactly this boundary. They could draft a plan, summarize a repo, or write a patch. They often failed when the task crossed into review queues, CI, ticketing, console UIs, or web apps built like they hate automation. Codex is now aiming at the same surface area as Anthropic’s computer-use push, OpenAI’s earlier Operator direction, and the RPA-plus-LLM crowd, but with a developer-first wedge instead of back-office automation.

I do not fully buy the “3M+ weekly developers” line without a denominator and a definition. The snippet gives the number and nothing about the measurement. Is that weekly active Codex users inside ChatGPT, any developer who touched a related feature, desktop sign-ins, or usage across multiple OpenAI surfaces? Those are very different claims. OpenAI has giant distribution, so it can light up a user graph fast through ChatGPT accounts alone. That does not prove durable workflow migration. What I would want to see is retention, tasks per user per week, share of sessions that use computer control, and completion rates on multi-step tasks. The body does not disclose any of that.

The plugin push is more important than the headline demo. JIRA, GitLab, CircleCI, Microsoft tools, and Databricks-adjacent workflow hooks tell you OpenAI understands where software work actually leaks time. The pain is no longer “write a function” in isolation. It is ticket triage, review comments, CI failures, environment setup, document lookup, handoffs, and enterprise glue. Cursor became strong by collapsing the edit-run-fix loop inside the IDE. Claude Code built a strong reputation around terminal-centric repo work. GitHub Copilot still has the Microsoft distribution advantage, especially where org policy and procurement favor it. If Codex can connect plugins, desktop control, SSH access, and memory into one continuous flow, it is competing for “default execution agent,” not “best autocomplete.” That is a much more strategic position.

Memory and self-scheduling are where the ambition gets larger, and where I get more skeptical. The article says Codex can remember preferences, prior corrections, and task context, then wake itself up days or weeks later to continue work. I think that direction is correct. I also think it is where many agent products break in real use. Long-running tasks fail because the world changes underneath them: Slack threads move, JIRA states change, branches get rebased, logins expire, access policies update, and the original assumptions are stale by the time the agent resumes. Plenty of “autonomous engineer” demos over the last year looked clean in a controlled run and fell apart in a live team environment. So I would not give OpenAI credit for “self-scheduling” until it shows cross-day completion rates and recovery behavior after failure. The body gives neither.

The macOS-first rollout also says a lot. This is not because Macs are magically better for agents. It is because paid developer density is high there, the environment is more predictable, and distribution is cleaner. Windows desktop control is more fragmented, especially under enterprise security policy. The delay for EU and UK availability, plus the limits around memory-related features, points to the other hard problem: once your product watches screens, stores preferences, and acts across time, privacy, auditability, and permission boundaries stop being footnotes. Many teams are comfortable letting a model draft a PR. Far fewer are comfortable letting it read Slack, scan Notion, and operate sensitive internal tools without very explicit controls.

One broader context point that is not in the snippet: the agent market has been splitting into two design philosophies. One is API-first, where you constrain actions through structured tool calls and get better reliability but narrower reach. The other is GUI-first, where the model interacts with existing software like a human and gets much wider reach but worse reliability. OpenAI looks like it is trying to combine both: plugins for the places where structured integration exists, desktop control for everything else. If that works, the moat is not just model quality. It becomes distribution, account identity, tool connectivity, desktop runtime, and iterative improvement on real execution traces.

That said, the entire bet rests on success rates. If GUI control stays flaky, users fall back to a familiar pattern very quickly: “you draft, I’ll click.” Then Codex slides back into the crowded coding-assistant lane. My take is simple: this launch is OpenAI trying to move from answering requests to acting on behalf of the user. That is a much bigger product claim than the headline suggests. It is also much harder than the demos make it look. OpenAI has the ingredients to try this at scale. The open question is whether it can get computer-use reliability, permissions, and long-horizon task continuity high enough that teams trust it with real work instead of occasional spectacle.

X · @OpenAIApr 17, 01:18

Codex for (almost) everything.

OpenAI said Codex can now use apps on Mac, connect to more tools, and handle ongoing and repeatable tasks. The post also claims image creation, learning from prior actions, and remembering user preferences; it does not disclose app coverage, integration method, pricing, or rollout timing.

Why it matters: This is an official OpenAI product update, and Codex moves from coding help toward desktop control, tool use, and memory, so HKR-H/K/R all pass. The post still omits supported apps, integration method, pricing, and launch timing, keeping it in the 78–84 band.

Take

OpenAI said Codex can use apps on Mac and connect to more tools. The post also claims image creation, learning from previous actions, preference memory, and ongoing or repeatable task handling. App coverage, integration method, pricing, and release timing are not disclosed in the body. My read is pretty simple: this is OpenAI staking out the desktop-agent category, not shipping a product we can evaluate seriously yet.

I'm not as impressed by the feature list as the post wants me to be. Desktop agents have never been bottlenecked by button-clicking alone. The hard part is getting three things to hold at once: clean permission boundaries, recovery after failure, and stable cross-app state. Anthropic's Computer Use already showed the gap between “can operate a computer” and “works in real workflows.” In practice, teams hit UI drift, login state issues, CAPTCHAs, modal dialogs, and brittle selectors. Rabbit and Adept pushed similar software-operating narratives earlier and ran into the same wall: demos scale faster than reliability.

The memory claim is where I have the most pushback. “Remembers how you like to work” sounds great in a clip. It also opens the hardest product questions. Is it remembering keyboard shortcuts, document formatting habits, internal approval patterns, or preferred SaaS paths? Is that memory stored locally on the Mac or synced to OpenAI's cloud? How is it scoped across personal and enterprise workspaces? How long does it persist? None of that is disclosed. Without those constraints, memory is a UX promise, not an enterprise feature.

The Mac angle does matter, though. It signals OpenAI wants more than API usage, a chat surface, or an IDE assistant. It wants the operating layer for knowledge work. Microsoft has been binding Copilot into Windows and M365. Apple has moved much slower on system-level AI execution. So OpenAI choosing Mac as a control point makes strategic sense: start where high-value users already live, then expand from chat into action. I buy that direction.

What I don't buy yet is the implied maturity. A post like this needs at least one hard artifact: supported app classes, a permissions model, pricing, rollout gates, or even a narrow benchmark like success rate on repeated workflows. We got none of that. Only the title and snippet are disclosed so far, so I would treat this as a roadmap signal with a polished demo layer, not as proof that desktop agents have crossed into dependable daily use.