Unlocking Earth AI’s planetary geospatial foundation models for global public health
Earth AI
Nguyên văn nguồnChi tiết nguồn
- Unlocking Earth AI’s planetary geospatial foundation models for global public health Google Research Blog · 6 thg 10, 2026
Paper và bài viết kỹ thuật
Crawl live-1795068900000 · 13:22 19 thg 11, 2026 · Xuất bản 13:30 19 thg 11, 2026
Earth AI
Nguyên văn nguồnCâu hỏi The problem with this is not the technical research they did, which is largely reasonable, but the failure to engage on more cross cutting questions like: What happens if we ban open models due to cyber risks or why do Chinese companies deem these models safe to release?
I’ve had one too many discussions on the cyber risks of open models — where someone assumes that either banning open models happens in a silo (and bad actors will somehow actually be stopped) or that China is a threat and doesn’t care about AI safety — that I feel we’re going to end up making policy decisions that both limit American AI competitiveness and increases long-term cyber risk. I feel like we’re locked in on a path of lose-lose situation, unless people embrace nuance, trade-offs, and scary realities. Much has been written about the views of various players in this debate, which I summarize as follows: Open weight models pose an untenable risk to society’s functionality , occupied by frontier lab leadership and the national security community in the U.S. Western voices saying open weight models are necessary for defense and banning them will make the world less safe , occupied by AI risk moderates to different extremes. I include myself in this bucket, along with Hugging Face’s perspective after the OpenAI incident, and others like Joshua Saxe . Chinese companies continuing to release open-weight models with strong cyber capabilities , who are making decisions based on the risk assessments of their society and government. This list is also organized by volume or clarity of message in the Western AI ecosystem. The risk-focused discussions have been disproportionately visible, including pieces of work which I view as very detrimental to potential of engaging across assumed party lines on this issue. There’s also very little substantive engagement trying to understand how Chinese companies assess risk — rather, mostly arguments that border on ad hominem attacks like “Chinese labs don’t care about safety.” Interconnects AI is a reader-supported publication. Consider becoming a subscriber. The delusions of the anti open-weight alliance The most recent publication from the “open-weights are dangerous” crowd was the report by Anthropic on the risks of GLM-5.3 as an offensive cyber tool. The problem with this is not the technical research they did, which is largely reasonable, but the failure to engage on more cross cutting questions like: What happens if we ban open models due to cyber risks or why do Chinese companies deem these models safe to release? These questions, which I’ll come back to, are the ones we need to answer to understand the ecosystem perspective on current AI risks. All policy actions happen in a multi-piece puzzle, where the shape of risk can be changed, but it is rare that you get a universally better outcome. They are all trade-offs. This sort of solipsistic writing by Anthropic fits very closely to another type of discourse I’m hearing about regularly that is determining the fate of open models and AI broadly — classified briefings. I’ve had many discussions with people who say something like “Look, I’m pro open models, but if you’re seeing what I’m seeing, it’s an onslaught out there due to [XYZ Chinese open-weight model] and we need to act.” This perspective flies in the face of public information, where to date closed models have been documented as the cause of most existing cyber attacks. As someone who tries to make grounded predictions, the evidence of numerous attacks from OpenAI models is the only data I have on the shape of cyber risks (or, you can broaden the scope to include all of FelonyBench ). There are a few possible explanations, and it’ll take years to get to the true answer: Maybe open model weights and closed model APIs (with some safe guards) are both far closer to being easy to mis-use, rather than API models being closer to safe. The trope "Open Dangerous, Closed Safe" may be closer to "Open Unsafe, Closed Unsafe." Maybe there are far fewer bad actors who are willing to use AI models for “loud” cyber attacks that target crucial infrastructure in the US or powerful and underprepared institutions. Closed models have stronger capabilities and stronger safeguards (in theory), but the stronger capabilities part could matter more in net harm if the safeguards on both are porous. I have a lot more to learn about how the cybersecurity ecosystem works, so I won’t support this full-heartedly as one of my current recommendations, but I think it’s at least a reasonable argument that open weight models as a diffusion tool for cyber defense could be the best tool we have to prevent harm over the next few years. There are many domains, e.g. sensitive government agencies, where open-weight models are the only tools that can be deployed in the near-term on air-gapped networks. Lots of this situation seems like the messy reality being hard to pin down, where the logical limits are clearer. I may agree with the simple reality that closed models are far safer in the limit, as a technical tool with more layers of protection, but they may actually be causing more harm in the near term because of how accessible model APIs are. Still, much of the impact of the tools comes down to how they’re used and controlled. A duopoly on such a crucial tool may be the defining, risky part. This is the debate we’re having, and over time, as intelligence diffuses, many things may change. These together make me come to the conclusion that if you think the latest open-weight models need to be banned to slow the diffusion of cyber risks, you probably also need to make public-facing APIs for the frontier closed-models illegal. The current stack of safeguards on closed models is stronger than open-weight models, but far from perfect. It is very likely that cyber capabilities of closed models increase much faster than guardrail performance, and a world where open models are banned while closed models continue to progress would be increasing the offense-defense cyber gap. It will take meaningful time to build mitigations that allow defenders to use strong AI models on their private infrastructure if we remove access to strong open-weight models. Share Explaining China’s AI risk posture
Nguyên văn nguồnCâu hỏi " 0:00 Intro 1:42 The Case for Owning Your Intelligence 4:35 OpenAI x Baseten and the Multi-Model Future 7:19 Can Post-Training Beat Frontier Models?
Yash Patil, a former OpenAI researcher who worked on Codex and now runs Applied Compute, argues that post-training is the most overlooked part of the AI stack and the key to owning your intelligence. He explains when companies should optimize their harness and context first, and when it's worth updating the weights: the largest inference workloads, plus tasks that change over time or depend on judgment. That's the heart of why he believes post-training wins inference. The biggest workloads are both the most valuable to train and the most valuable to serve, and how a model is trained shapes how it should be served. Getting production serving running is the easier half; echoing Dylan Patel, he says GPUs plus vLLM plus OpenRouter "kind of" gets you there. Yash is candid about the limits of RL. It's a hill-climbing machine whose hardest part is defining the hill, which makes a company's private evals as worth protecting as its employees. It generalizes far less than pre-training. And continual learning remains blocked by the unsolved problem of extremely data-efficient training from sparse rewards. He lays out his bet on a new AI hyperscaler, built on GPUs the way AWS, GCP, and Azure were built on CPUs. He pictures it as an inverted pyramid with training at the bottom, where few can compete, and inference, routing, and harness stacked above. The conversation also covers whether every firm needs its own model, why Jevons paradox has made cost matter more than he expected, how models reward hack "like water," and why the US needs American open-weight models even though "blanket bans are not the answer." 0:00 Intro 1:42 The Case for Owning Your Intelligence 4:35 OpenAI x Baseten and the Multi-Model Future 7:19 Can Post-Training Beat Frontier Models? 9:03 What Data Stays Out of Distribution 11:51 Data Efficiency and Continual Learning 14:31 When Updating Model Weights Makes Sense 16:01 Online Training in Practice 18:16 Lowering the Cost of Post-Training 19:48 Does Every Company Need Its Own Model? 24:06 RL in Non-Verifiable Domains 26:59 How Applied Compute Picks Customers 28:46 Building an Inference Business 34:43 The Case for a New AI Hyperscaler 38:21 Building RL Environments 41:33 Quickfire Jacob is an AI investor at Redpoint Ventures. He's led Redpoint's investments in companies like Abridge, Physical Intelligence & Legora. Follow Jacob on Twitter: https://x.com/jacobeffron On Unsupervised Learning we probe the sharpest minds in AI in search for the truth about what's real today, what will be real in the future and what it all means for businesses and the world. If you're a builder, researcher or investor navigating the AI world, this podcast will help you deconstruct and understand the most important breakthroughs and see a clearer picture of reality. Subscribe to this show to stay up to date on our latest episodes.
Nguyên văn nguồnAt 100,000-accelerator scale, something fails multiple times an hour, which is why Google's Chief Technologist for AI Infrastructure Amin Vahdat thinks FLOPS is a vanity metric. The metric that matters is what he calls goodput: the useful work a workload actually delivers through real failures. Amin walks through the calculus that split the TPU line into 8i and 8t for the first time, why the TPU's core primitives haven't changed since v1, and how Google and DeepMind co-design in the same rooms, intercepting chip architectures mid-flight before tape-out. He explains why long-horizon agents are sending demand for CPUs and storage through the roof alongside accelerators, how optical circuit switches reroute light to a spare rack in milliseconds, and why Google would rather wait on a utility than build its own gigawatt. We also cover orbital data centers and the multi-megawatt rack of 2036. Hosted by Sonya Huang, Sequoia Capital 0:00 – Introduction 1:47 – What makes a data center an AI data center 5:30 – Goodput, not FLOPS: holding yourself accountable when something fails every hour 11:52 – Doubling token capacity every six months, and where the gains actually come from 15:32 – The TPU bet: from a contrarian call in 2013 to splitting 8i and 8t 23:30 – The case for and against co-design 26:11 – Shoulder to shoulder with DeepMind: intercepting chips mid-flight 34:16 – Long-horizon agents change the shape of the data center 37:50 – Optical circuit switching and the state of networking 42:35 – Power is the binding constraint: utilities, gigawatts, and sizing a data center 49:23 – Training vs. serving clusters, seven-year-old TPUs, and open standards 58:29 – Orbital data centers and the supercomputer of 2036
Nguyên văn nguồnYou can now see and reply to the local agents running on your computer from the Cursor iOS app. Get started Remote Control is on by default for everyone except Enterprise organizations. Download the Cursor iOS app and sign in. Computers on your account appear in the app automatically. Tap your computer in the app and approve your pairing request in the Cursor desktop app. Your local agents appear in a list. Tap one to see what it's doing or send it a message. <figure><img src="https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/changelog/remote-control-cl-pezewO3SZRrIQxMNaTzdpsP9TD1ChS.png" loading="lazy" alt="Remote Control for local agents in the Cursor iOS app" /><figcaption>Remote Control for local agents in the Cursor iOS app</figcaption></figure> Agents keep running on your computer Remote control doesn't move your agents anywhere. It keeps running on your computer, and the app connects to it. Your computer needs to stay on and online for remote control to work. Keep your computer awake To stop your computer from sleeping while you're away, turn on "Keep this computer awake" under Remote Control in Cursor's desktop settings. Your computer needs to be plugged in with the lid open. For Enterprise teams Remote control is on by default, except for Enterprise organizations. Enterprise admins can turn it on in Org settings > Security and identity > Remote control. Remote control doesn't require cloud agents to work. Remote control is available today in the Cursor iOS app .
Nguyên văn nguồnEnterprises can now run open models at production scale on a dedicated B300 inference cluster, built by Together AI, IBM Cloud, and NVIDIA
Nguyên văn nguồnGenerative AI
Nguyên văn nguồn<table> <thead> <tr> <th>Package</th> <th>Version</th> </tr> </thead> <tbody> <tr> <td><code>@modelcontextprotocol/client</code></td> <td>2.3.1</td> </tr> <tr> <td><code>@modelcontextprotocol/server</code></td> <td>2.3.1</td> </tr> <tr> <td><code>@modelcontextprotocol/core</code></td> <td>2.3.1</td> </tr> <tr> <td><code>@modelcontextprotocol/server-legacy</code></td> <td>2.3.1</td> </tr> <tr> <td><code>@modelcontextprotocol/codemod</code></td> <td>2.3.1</td> </tr> <tr> <td><code>@modelcontextprotocol/node</code>, <code>express</code>, <code>hono</code>, <code>fastify</code></td> <td>unchanged</td> </tr> </tbody> </table> <h2>Changes</h2> <ul> <li><code>requireBearerAuth</code> in <code>@modelcontextprotocol/server-legacy</code> takes the optional <code>expectedResource</code> that <code>@modelcontextprotocol/server</code> 2.3.0 added: it accepts only tokens issued for this server (the token's audience). Off unless you set it. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5710576774" data-permission-text="Title is private" data-url="https://github.com/modelcontextprotocol/typescript-sdk/issues/2952" data-hovercard-type="pull_request" data-hovercard-url="/modelcontextprotocol/typescript-sdk/pull/2952/hovercard" href="https://github.com/modelcontextprotocol/typescript-sdk/pull/2952">#2952</a>)</li> <li>The npm pages of <code>@modelcontextprotocol/server</code> and <code>@modelcontextprotocol/client</code> now open with one note that links the documentation, the migration guide and the issue form. (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5711246129" data-permission-text="Title is private" data-url="https://github.com/modelcontextprotocol/typescript-sdk/issues/2955" data-hovercard-type="pull_request" data-hovercard-url="/modelcontextprotocol/typescript-sdk/pull/2955/hovercard" href="https://github.com/modelcontextprotocol/typescript-sdk/pull/2955">#2955</a>)</li> </ul>
Nguyên văn nguồn<h2>What's Changed</h2> <ul> <li>[v1.x] docs: state the principles in CLAUDE.md by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/claude/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/claude">@claude</a>[bot] in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5681372162" data-permission-text="Title is private" data-url="https://github.com/modelcontextprotocol/typescript-sdk/issues/2939" data-hovercard-type="pull_request" data-hovercard-url="/modelcontextprotocol/typescript-sdk/pull/2939/hovercard" href="https://github.com/modelcontextprotocol/typescript-sdk/pull/2939">#2939</a></li> <li>[v1.x] docs: point the README at v2 and say what v1.x supports by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/claude/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/claude">@claude</a>[bot] in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5682278405" data-permission-text="Title is private" data-url="https://github.com/modelcontextprotocol/typescript-sdk/issues/2942" data-hovercard-type="pull_request" data-hovercard-url="/modelcontextprotocol/typescript-sdk/pull/2942/hovercard" href="https://github.com/modelcontextprotocol/typescript-sdk/pull/2942">#2942</a></li> <li>chore: bump version to 1.32.1 by <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/claude/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/claude">@claude</a>[bot] in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5711243793" data-permission-text="Title is private" data-url="https://github.com/modelcontextprotocol/typescript-sdk/issues/2954" data-hovercard-type="pull_request" data-hovercard-url="/modelcontextprotocol/typescript-sdk/pull/2954/hovercard" href="https://github.com/modelcontextprotocol/typescript-sdk/pull/2954">#2954</a></li> </ul> <p><strong>Full Changelog</strong>: <a class="commit-link" href="https://github.com/modelcontextprotocol/typescript-sdk/compare/1.32.0...1.32.1"><tt>1.32.0...1.32.1</tt></a></p>
Nguyên văn nguồnTogether Link brings frontier open models like GLM 5.3 and Kimi K3 into the coding agent your team already uses, cutting model spend by over 50%.
Nguyên văn nguồn<h2><a href="https://github.com/openai/openai-agents-python/compare/v0.23.0...v0.23.1">0.23.1</a> (2026-10-02)</h2> <h3>Bug Fixes</h3> <ul> <li>restore release tests and refresh required readiness check (<a href="https://github.com/openai/openai-agents-python/issues/5278" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5278/hovercard">#5278</a>) (<a href="https://github.com/openai/openai-agents-python/commit/730deb419c0a2e9e5ebd739499744e4a6bf89ed1">730deb4</a>)</li> </ul> <h3>Release readiness review (v0.23.0 -> TARGET <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/openai/openai-agents-python/commit/0a5a08b21cd44808d73e8a9e732212dd33b3690d/hovercard" href="https://github.com/openai/openai-agents-python/commit/0a5a08b21cd44808d73e8a9e732212dd33b3690d"><tt>0a5a08b</tt></a>)</h3> <p>This is a release readiness report done by <code>$final-release-review</code> skill.</p> <h3>Diff</h3> <p><a class="commit-link" href="https://github.com/openai/openai-agents-python/compare/v0.23.0...0a5a08b21cd44808d73e8a9e732212dd33b3690d"><tt>v0.23.0...0a5a08b</tt></a></p> <h3>Release intent</h3> <ul> <li>Review mode: final candidate</li> <li>Intended release: patch, 0.23.1</li> <li>Minimum required release type: patch</li> <li>Versioning verdict: compatible</li> </ul> <h3>Release call</h3> <p><strong>🟢 GREEN LIGHT TO SHIP</strong> this exact candidate. No concrete release-blocking regression was identified. Human approval and normal repository protections still apply.</p> <h3>Scope summary</h3> <ul> <li>28 files changed (+622/-42): release automation, test fixtures, integration/example tooling, and release metadata.</li> <li>The clean candidate contains current main <code>a575a6e637feb9aea1b591237b007dd4991ddfba</code> plus only six release-owned metadata files. Package, lockfile, manifest, source version and API baseline agree on 0.23.1. Snapshot source <code>b31b9f8d13d49142a64f8873f2cc2ee40441a795</code> is an ancestor of the candidate.</li> <li>Relative to v0.23.0, SDK runtime source changes only its version string. API snapshot content, dependencies, Python support and persisted schemas are unchanged.</li> </ul> <h3>Risk assessment (ordered by impact)</h3> <ol> <li> <p><strong>First PyPI publication of the 0.23 series includes earlier migration requirements</strong></p> <ul> <li>Risk: <strong>🟢 LOW</strong> with the previously reviewed migration paths. Users upgrading from 0.22.3 receive the 0.23.0 behavior changes as well as this patch.</li> <li>Evidence: PyPI has neither 0.23.0 nor 0.23.1. The 0.23.0 release assessment in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619073047" data-permission-text="Title is private" data-url="https://github.com/openai/openai-agents-python/issues/5226" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5226/hovercard" href="https://github.com/openai/openai-agents-python/pull/5226">#5226</a> covers strict tools, approval restoration, encrypted history, resource limits, voice defaults and provider changes; this candidate does not alter those runtime paths.</li> <li>Files: <code>CHANGELOG.md</code>, <code>src/agents/version.py</code>; unchanged 0.23.0 runtime contracts assessed in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5619073047" data-permission-text="Title is private" data-url="https://github.com/openai/openai-agents-python/issues/5226" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5226/hovercard" href="https://github.com/openai/openai-agents-python/pull/5226">#5226</a>.</li> <li>Action: Carry forward the 0.23.0 migration guidance in the 0.23.1 announcement, particularly explicit strict-tool parameters, fresh legacy approvals, trusted encrypted-history import, resource-limit overrides and the explicit prior voice-model override.</li> </ul> </li> <li> <p><strong>Release checks recover without changing package behavior</strong></p> <ul> <li>Risk: <strong>🟢 LOW</strong>. Test-loop initialization and required-check ownership are corrected while publication authorization remains intact.</li> <li>Evidence: OS mocks are installed after event-loop initialization and restored before teardown. Authorized review events rerun the current PR-triggered readiness check instead of replacing or cancelling it. Source validation, native human approval, isolated builds and OIDC publishing remain unchanged.</li> <li>Files: <code>tests/sandbox/test_unix_local_user_file_io.py</code>, <code>.github/scripts/release_automation.py</code>, <code>.github/workflows/release-readiness-refresh.yml</code>, <code>.github/workflows/release-readiness.yml</code>.</li> <li>Action: Submit the exact-head human approval, allow readiness to refresh, merge through normal protections, and verify the publisher and uploaded provenance.</li> </ul> </li> <li> <p><strong>External-provider coverage now requires explicit maintainer intent</strong></p> <ul> <li>Risk: <strong>🟢 LOW</strong> with an existing opt-in path. Default integration and automatic example runs no longer implicitly select the affected external-provider cases.</li> <li>Evidence: Integration bootstrap resets inherited enable flags, removes the listed external-provider credentials by default, and rejects external model overrides without opt-in. External cases are deselected by default; automatic examples use the expanded skip list. Manual example selection remains available.</li> <li>Files: <code>.github/scripts/run_integration_tests.py</code>, <code>integration_tests/conftest.py</code>, <code>Makefile</code>, <code>examples/run_examples.py</code>, <code>integration_tests/README.md</code>.</li> <li>Action: Use <code>make integration-tests-providers-external</code>, adding <code>-- --all</code> when direct-provider coverage is intended. Do not interpret default coverage as external-provider validation
Nguyên văn nguồn<img src="https://storage.googleapis.com/gweb-uniblog-publish-prod/images/September_AI_Recap_hero.max-600x600.format-webp.webp">Here are Google’s latest AI updates from September 2026
Nguyên văn nguồnMobile Systems
Nguyên văn nguồn<h2><a href="https://github.com/openai/openai-agents-python/compare/v0.22.3...v0.23.0">0.23.0</a> (2026-10-01)</h2> <h3>Features</h3> <ul> <li><strong>mcp:</strong> add configurable MCP listing page limits (<a href="https://github.com/openai/openai-agents-python/issues/5133" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5133/hovercard">#5133</a>) (<a href="https://github.com/openai/openai-agents-python/commit/9a21ab19fee8314df63126bdf5c43691887222dd">9a21ab1</a>)</li> <li><strong>sandbox:</strong> add opt-in Docker removal protection (<a href="https://github.com/openai/openai-agents-python/issues/5116" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5116/hovercard">#5116</a>) (<a href="https://github.com/openai/openai-agents-python/commit/ae5803f3ccd59899c14e0ee2f356614933880a68">ae5803f</a>)</li> <li><strong>sandbox:</strong> allow configuring memory consolidation turns (<a href="https://github.com/openai/openai-agents-python/issues/5135" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5135/hovercard">#5135</a>) (<a href="https://github.com/openai/openai-agents-python/commit/daa1bcbcc097654809fa48478da1b87c64474971">daa1bcb</a>)</li> <li><strong>sessions:</strong> add an opt-in encrypted history scan budget (<a href="https://github.com/openai/openai-agents-python/issues/5118" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5118/hovercard">#5118</a>) (<a href="https://github.com/openai/openai-agents-python/commit/a2fdb94627776efc9b3e893afe22f28e078c647a">a2fdb94</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li>avoid awaiting cleanup during coroutine closure (<a href="https://github.com/openai/openai-agents-python/issues/5163" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5163/hovercard">#5163</a>) (<a href="https://github.com/openai/openai-agents-python/commit/719c4e7d1c65702a8955a958cf7af8d6d6bda008">719c4e7</a>)</li> <li><strong>ci:</strong> update and group CodeQL actions together (<a href="https://github.com/openai/openai-agents-python/issues/5262" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5262/hovercard">#5262</a>) (<a href="https://github.com/openai/openai-agents-python/commit/f76153c6f0b880388fd2dcc41ee99a6a9d2c3df6">f76153c</a>)</li> <li><strong>ci:</strong> validate release source before building distributions (<a href="https://github.com/openai/openai-agents-python/issues/5220" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5220/hovercard">#5220</a>) (<a href="https://github.com/openai/openai-agents-python/commit/2747c1c6ac675a4a95622beb40e2403084edad93">2747c1c</a>)</li> <li><strong>core/extensions:</strong> respect sensitive trace capture for model metadata (<a href="https://github.com/openai/openai-agents-python/issues/5129" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5129/hovercard">#5129</a>) (<a href="https://github.com/openai/openai-agents-python/commit/88b722d5d235f98da3fc2b3db79a457002b9eb0c">88b722d</a>)</li> <li><strong>core:</strong> bound agent tool streaming callback backlogs (<a href="https://github.com/openai/openai-agents-python/issues/5106" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5106/hovercard">#5106</a>) (<a href="https://github.com/openai/openai-agents-python/commit/f23da767df176df1733af277061c072b235e6c95">f23da76</a>)</li> <li><strong>core:</strong> isolate nested agent tool state across fresh runs (<a href="https://github.com/openai/openai-agents-python/issues/5123" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5123/hovercard">#5123</a>) (<a href="https://github.com/openai/openai-agents-python/commit/46cc8d8d13cac3d641d9c159f20d0cb665aca4c7">46cc8d8</a>)</li> <li><strong>core:</strong> preserve closed parent constraints in singleton allOf (<a href="https://github.com/openai/openai-agents-python/issues/5131" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5131/hovercard">#5131</a>) (<a href="https://github.com/openai/openai-agents-python/commit/f010d185d94ed677b61219047f39716b5f125195">f010d18</a>)</li> <li><strong>core:</strong> preserve guarded final outputs in agent tools (<a href="https://github.com/openai/openai-agents-python/issues/5115" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5115/hovercard">#5115</a>) (<a href="https://github.com/openai/openai-agents-python/commit/f3a15f61af2fb8e425d9fcdc42c2bec06303f69f">f3a15f6</a>)</li> <li><strong>core:</strong> preserve structured guardrail diagnostics and agent output during persistence (<a href="https://github.com/openai/openai-agents-python/issues/5016" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5016/hovercard">#5016</a>) (<a href="https://github.com/openai/openai-agents-python/commit/51bcea7c831d34bc441e2c4ca5b7277df23781e6">51bcea7</a>)</li> <li><strong>core:</strong> preserve tool identity during asynchronous enablement (<a href="https://github.com/openai/openai-agents-python/issues/5136" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5136/hovercard">#5136</a>) (<a href="https://github.com/openai/openai-agents-python/commit/f2ae64c16779b82f934bf16bbf458acf3c454237">f2ae64c</a>)</li> <li><strong>core:</strong> redact default tool failure details (<a href="https://github.com/openai/openai-agents-python/issues/5112" data-hovercard-type="pull_request" data-hovercard-url="/openai/openai-agents-python/pull/5112/hovercard">#5112</a>) (<a href="https://github.com/openai/openai-agents-python/commit/40956e040a386d7f9c43d591c77d22f45a9df7a8">40956e0</a>)</li> <li><strong>core:</strong> redact streaming task exception
Nguyên văn nguồnAnthropic is investing $100 million in Claude Frontier Academy to train 10,000 Frontier Deployed Engineers by the end of 2027, with cohorts from Accenture, Bain, CBA, Deloitte, McKinsey, Morgan Stanley and Novo Nordisk already underway.
Nguyên văn nguồnBarclays, the British universal bank, is expanding its strategic collaboration with Anthropic to integrate secure, enterprise-grade AI systems across its global operations.
Nguyên văn nguồnGuest author Prof. Matthew Schwartz describes what happened when he stopped fighting Claude and allowed Claude to find “Claude-shaped” problems: ones best suited to the capabilities of the current generation of LLM tools. This led him to build BootLoops, a toolkit for exact calculations in quantitative science, which he has been applying across scientific fields alongside experts.
Nguyên văn nguồnSam Altman's Dot, OpenAI's new always-on agent, gave him back the most productive part of his day. The OpenAI CEO would lose his early mornings—his window of "maximum creativity"—to whatever fire needed putting out. Now, his Dot triages those issues and flags only what's truly urgent. It's also gotten him building again: In spare moments, he gives his Dot ideas for a feature, and his Dot builds five or six versions for him to review. On the first episode of The Every Podcast (formerly AI & I), Dan Shipper interviews Altman at OpenAI's DevDay. They discuss how Altman uses his Dot to protect his time, why he only prompts on Ultrafast, and his belief that AI will spark a new Renaissance. If you found this episode interesting, please like, subscribe, comment, and share! Go to https://attio.com/every and get 15% off your first year. To hear more from Dan Shipper: • Subscribe to Every: https://every.to/subscribe • Follow him on X: https://twitter.com/danshipper 00:00:00 Introduction 00:00:55 Why AI hasn’t replaced developers 00:04:45 OpenAI’s platform bet on the rise of small-team companies 00:05:45 Why the AI era is more “Renaissance” than “Industrial Revolution” 00:07:40 How Sam’s Dot, OpenAI’s always-on AI agent, gave him back his mornings 00:12:00 Sam’s process for building new features with his Dot 00:16:00 Inside OpenAI’s “live documents” that agents and humans can build together 00:20:55 What bring-your-own-subscription changes for app developers 00:24:00 Why “OpenAI just killed X startup” never comes true 00:27:55 Sam’s life on Ultrafast and the push to make speed as cheap as intelligence Links to resources mentioned in the episode: • Sam Altman on X: https://x.com/sama • Codex: https://openai.com/codex • Space: https://help.openai.com/en/articles/20001549-getting-started-with-space-in-chatgpt • Every's Vibe Check on Dots: https://every.to/vibe-check/vibe-check-dots-always-on-agents-in-chatgpt?utm_source=podcast • Every's Vibe Check on OpenAI DevDay 2026: https://every.to/vibe-check/vibe-check-openai-devday-2026?utm_source=podcast
Nguyên văn nguồnProof of concept for watermarking AI-generated proteins while preserving biological function.
Nguyên văn nguồnCâu hỏi What work can robots do?
We built an index of how well today’s robots can perform US job tasks. Robots can already do three-quarters of physical tasks, mostly in limited settings, but are cost-competitive for just 0.3% of them.
Nguyên văn nguồn