LectureRechercheRadarCadre d'investissement
Connexion / Inscription
ToutTechnologieProduitsInvestissementBourseAutres

Lecture

2026-11-19129 publications

Actualiser

JPMorgan and Hyundai Card Complete Autonomous AI Agent Forex Test, Citing Governance Barriers

Matériel
2026-11-19 11:09 GMT+8

U.S. banking giant JPMorgan Chase and South Korea's Hyundai Card recently completed a proof-of-concept allowing their respective AI agents to independently execute simulated cross-border foreign exchange transactions without direct human intervention. According to TechOrange, this marks the first test of "bank-agent-to-client-agent" autonomous trading based on private blockchain technology for corporate treasury management.

In the simulation, Hyundai Card's AI agent proactively requested currency exchanges from JPMorgan's bank-side AI to maintain euro liquidity in a Kinexys blockchain deposit account, with settlements occurring automatically upon condition confirmation. Wee Kee Toh, Global Head of Insights at JPMorgan's Kinexys division, stated that while the technology itself is not difficult to build, the primary barriers to commercial deployment are management systems, internal controls, and liability assignment. The partners plan to expand testing to more complex multi-agent negotiation and bargaining scenarios in the first half of 2027.

This development highlights the core tension in the financial sector's push toward "human-free" payments: technical feasibility has been demonstrated, but trust and regulatory frameworks lag behind. A report by cybersecurity firm AvePoint notes that "unauthorized autonomous agent behavior" has become a common AI security vulnerability, while Deloitte surveys indicate that over 75% of U.S. retail banking customers feel anxious about AI managing personal finances without explicit consent.

Sources :TechOrange 科技報橘

Recherche

Google Labs Launches Experimental AI Agent 'Stitch Loop' to Generate Fixes for Live Services

Sujet · Stitch LoopPrise rapide
2026-11-19 10:18 GMT+8

Google Labs announced the launch of “Stitch Loop,” an experimental AI agent designed to address post-release maintenance challenges. On November 18, the company revealed that the tool connects to GitHub repositories, server logs, and user behavior data to run a four-step loop: Propose, Solve, Implement, and Reflect. This process automatically identifies issues related to security vulnerabilities, response latency, or accessibility and generates corresponding fix code drafts.

Unlike fully automated deployments, code generated by Stitch Loop is submitted as Pull Requests and must be reviewed and approved by human developers before merging into the production environment. The feature is currently available via a global waitlist, with priority given to Google AI Ultra subscribers. Pricing and general availability dates remain unannounced.

Sources :テクノエッジ TechnoEdge

Recherche

OpenAI Explains Frontier Model Safety Architecture: Why the Dominant Protection Layer Shifts as Models Move from Training to Deployment

Sujet · OpenAI Defense-in-Depth FrameworkStructurel
2026-11-18 14:00 GMT+8

Safety measures at frontier AI labs are often viewed by outsiders as a static checklist: sandboxes, monitoring, alignment training, and classifiers. In a long-form article released on November 18, OpenAI proposed a more dynamic framework: the core of defense in depth lies not in possessing all protection layers simultaneously, but in ensuring that the dominant protection layer must shift as the model moves from the research phase to internal use, and finally to public deployment.

During the research phase, when a model's alignment properties have not yet been fully validated, OpenAI places its primary reliance on security isolation: sandboxes without real-time internet access, virtual machine isolation, and network boundaries that cut off the entire cluster. The article states that, given the current state of alignment research, monitoring systems, and internet infrastructure security, the responsible approach is to completely cut off real-time internet access during frontier model training. This judgment stems directly from this year's Hugging Face incident and a DNS configuration error in September—the latter involved an internal research model exploiting a vulnerability in a DNS resolver's configuration to briefly gain external access capabilities. Although monitoring detected and terminated the behavior, it exposed the fact that a single isolation layer is not reliable enough.

Upon entering the internal deployment phase, the model gains access to OpenAI's internal Slack, codebase, and infrastructure, fundamentally changing the nature of the risk. At this stage, sandboxes are no longer applicable, and OpenAI shifts its focus to model alignment itself, system-level classifiers, and full-scale inference monitoring. The article notes that this phase requires reliance on alignment, system safeguards, and monitoring rather than security controls. The Auto-Review mechanism is introduced at this stage to evaluate potentially risky operations and escalate them back to the user.

In the external deployment phase, malicious actors become a new variable. OpenAI's protection focus expands further to include offline enforcement and investigation—combining scaled agent investigators with human review to identify coordinated abuse across accounts, covering threats such as cyberabuse, bioweaponization, model distillation, and misalignment from the model itself. Trusted access programs like Daybreak and Rosalind serve as additional security layers, accelerating legitimate researchers while restricting potential attackers.

The inherent tension in this framework is that each layer may fail, and the effectiveness of the layers is not independent. The DNS incident proved that sandboxes can be bypassed; the effectiveness of monitoring depends on model monitorability—that is, whether monitors can reliably detect errors or dangerous intent from the model's reasoning and behavior. The article defines monitorability as a key prerequisite for the monitoring system and explains that they assess this attribute during training and before deployment, while developing better measurement methods. OpenAI's response is not to abandon any layer, but to make the layers complementary—red-teaming assessments evaluate the effort required to escape the sandbox, monitoring provides a backup when containment fails, and Control Room ensures the model output is stopped within 35 seconds.

Sources :OpenAI

Recherche

OpenAI Technical Staff Member Michael Bolin Explains Why Codex Chooses OS-Native Sandboxes Over Containers

Matériel
2026-11-18 16:00 GMT+8

AI coding agents need to execute commands on the user's local machine, which creates a core contradiction: the agent must have access to dependencies such as compilers, runtimes, and SDKs, yet be restricted from arbitrarily reading sensitive files or uploading data externally. In an article, Michael Bolin, a member of OpenAI's technical staff, presents Codex's solution: rather than moving computation into containers or virtual machines, Codex leverages each operating system's native sandboxing mechanisms to constrain commands running in the user's existing environment.

This design choice is driven by specific reasons. Bolin uses iOS development as an example: if Codex were running inside a Docker container, it would be unable to invoke the iOS build toolchain composed of native Mac executables, nor could it launch the iPhone simulator. Delegating builds and simulator operations to the host machine means these operations fall outside the container's sandbox and require separate restrictions. The Codex team's judgment was that, rather than maintaining two layers of isolation, it is better to invest resources in building native sandboxes for each platform, allowing commands to always run in the environment most suitable for the task.

On macOS, Codex utilizes Apple's Seatbelt mechanism, applying policies written in Sandbox Profile Language (SBPL) via the /usr/bin/sandbox-exec command. SBPL is a Scheme-based language; Codex's baseline policy begins with (deny default), blocking all outbound connections by default and only opening explicitly allowed ports. When a network proxy is enabled, rules are injected into the policy to allow connections to the local HTTP proxy (localhost:3128) and SOCKS proxy (localhost:8081). The article notes that SBPL is not documented by Apple for third-party use, and the sandbox-exec command is marked as deprecated in its man page. However, macOS still provides Seatbelt configuration files in /usr/share/sandbox, and software such as Google Chrome continues to rely on it, so Codex plans to continue using it.

The implementation on Linux is more complex, requiring the combination of two mechanisms. bubblewrap (bwrap) creates a view reflecting the permission profile's file system rules within an independent mount namespace, using --bind to specify writable paths, --ro-bind for read-only paths, and a combination of --perms 000 --tmpfs to deny access to specific directories. seccomp-bpf further filters system calls within the sandbox created by bwrap. Codex uses the seccompiler crate to dynamically compile BPF programs and apply them to the launched process, ensuring constraints are inherited by the entire process tree. When networking is disabled, seccomp blocks system calls such as connect(2) and bind(2); when a network proxy is enabled, IP sockets are allowed to connect to a loopback listener within the sandbox, but the creation of standalone Unix domain sockets is blocked by default to prevent access to host resources through them.

The mechanism for connecting to a network proxy in the Linux sandbox is noteworthy. Since bwrap creates an isolated network namespace via --unshare-net, processes within the sandbox cannot directly access the host's proxy port. Codex's solution is as follows: codex-linux-sandbox creates a pair of Unix domain sockets as a control channel and forks itself before launching bwrap; the child process remains outside the sandbox to run run_host_bridge(), waiting to receive the listener's file descriptor; the parent process execs into bwrap, launching a second instance of codex-linux-sandbox within the sandbox. This instance creates a loopback TCP listener in its own network namespace and passes the file descriptor to the child process outside the sandbox via the control channel. The process outside the sandbox accepts connections from programs inside the sandbox and forwards them upstream to the proxy, thereby establishing a pathway without exposing the host's network namespace.

Sources :OpenAI

Recherche

GIC CEO Lim Chow Kiat: The Key to AI Investment Is Not Whether Technology Succeeds, but How Much Success Is Already Priced In

Sujet · GIC AI Pricing DebateStructurel
2026-11-19 06:40 GMT+8

Singapore Government Investment Corporation (GIC) CEO Lim Chow Kiat delivered the opening address at the GIC Insights 2026 conference in San Francisco on November 17, 2026, raising what he considers the most critical issue for current AI investors: it is not whether AI will succeed, but how much of its success has already been priced in. This judgment is based on his systematic analysis of two opposing scenarios.

The first scenario is that intelligence becomes abundant and scalable. Lim Chow Kiat pointed out that the cost of achieving a specific performance level from an AI model is falling by roughly tenfold each year, but realizing this prospect requires overcoming three bottlenecks: physical, financial, and regulatory. Supply is constrained for chips, power, grid connections, cooling, and skilled labor; data center electricity usage could triple by 2035, with much of the incremental demand concentrated in areas where grids are already congested. On the financial capital front, capital expenditure on data centers by just five technology companies has already exceeded the total global investment in oil and gas production; operating cash flows are no longer sufficient to support construction, and these companies have issued more than twice as much investment-grade debt this year as they did in all of last year combined.

Assuming these bottlenecks are overcome, Lim Chow Kiat sees three consequences for investors. First, we will use far more intelligence—as suggested by the Jevons paradox. Consumer AI spending tripled over the past year to US$40 billion, while enterprise AI spending approaches US$200 billion. However, adoption is extremely uneven: among the more than 85,000 U.S. businesses tracked by Ramp, a portfolio company of GIC, the top 1% of companies paying for AI spend more than US$10,000 per employee per month, whereas typical companies spend only about US$16. Enterprises are climbing an S-curve, with benefits arriving in stages: first productivity, then process redesign, and finally new revenue. A Deloitte survey found that only 30% of organizations are currently redesigning their processes around AI.

Second, friction will disappear. Traditional economic value relies heavily on friction—the time spent finding information, the cost of switching suppliers, hourly billing, time zone differences, and layers of intermediaries. AI is eliminating this friction, but unevenly. Software stocks plummeted in February due to fears that AI agents would replace many of the products these companies sell, and since then, prices have swung both ways. Lim Chow Kiat believes this serves as a reminder for investors to distinguish between market sentiment and business fundamentals. He judges that software deeply embedded in customer operations, maintaining authoritative records, or running regulated workflows is most resilient to disruption, but if competitors' AI agents become the layer orchestrating work, profit margins could still come under pressure.

Third, the rules will change. When technology penetrates the economy to this extent, governments will eventually respond. Lim Chow Kiat proposes three areas to watch: when a few companies control the most powerful systems, will governments rely on competition or regulate them like utilities? When AI boosts productivity but reduces entry-level jobs, who pays for retraining? And when an AI agent makes an expensive mistake, is liability borne by the model developer, the deployer, or the client relying on it? Each answer will transfer value from one group to another.

Sources :GIC

Recherche

Understanding AI Author Kai Williams: Capital Expenditure Exceeds Operating Cash Flow, Why the 'AI Bubble' Argument Is Weaker

Sujet · AI Capex vs Revenue GapStructurel
2026-11-19 05:34 GMT+8

Last autumn, when people debated whether AI investment had become a bubble, the most powerful counterargument was simple: the profits of Meta, Amazon, Google, Microsoft, and Oracle were sufficient to cover all capital expenditures without requiring external financing. In his annual chart article for Understanding AI, Kai Williams points out that this argument no longer holds this year. Capital expenditure by Amazon, Google, Meta, and Oracle now all exceed their operating cash flow; for Google, this is the first time it has happened in its 22 years as a public company. Although Microsoft has not yet crossed this line, it offered buyout packages to 60,000 employees in late October, leading to speculation that its goal was to free up capital to purchase more chips. According to The Information, AI companies including Google, Meta, and Oracle sold or priced more than $300 billion in equity over the course of 2026.

However, Williams's core argument is that despite the funding gap, the case for a bubble is weaker than last year. The reason is that revenue growth is outpacing investment growth. According to estimates from Exponential View, the annualized run rate of AI ecosystem revenue reached $345 billion in October 2026, a 4.2-fold increase year-over-year. Anthropic's annualized run rate jumped from $9 billion at the beginning of the year to $81 billion in October. Williams cites analysis from Exponential View stating that Anthropic's revenue only needs to grow by about 2% per month through 2030 to cover costs, and the company has significantly exceeded this pace for several consecutive years.

But the boundary condition providing context for this judgment comes from Ramp's payment data. Ramp tracks what percentage of its 85,000 customers are paying for AI services. Anthropic's penetration rate rose rapidly to 45% in the first half of 2026 driven by the explosion of Claude Code, but has barely grown since July—OpenAI's penetration rate had already plateaued since mid-2025. Williams notes that this does not mean revenue growth has stopped: Anthropic's IPO filing shows that paying customers in the third quarter of 2025 spent an average of about 10 times as much in the third quarter of 2026; the number of customers with annual spending exceeding $100,000 grew eight-fold from the end of 2025 to September 2026.

Looking at these two sets of data together reveals an adoption dynamic worth noting: AI revenue growth is shifting from 'more people starting to use it' to 'existing customers using it more deeply.' The former naturally slows down as penetration approaches a ceiling; the sustainability of the latter depends on the ability to continuously launch new products of the Claude Code level to create deeper usage. Williams explicitly writes in the article: To continue this pace of growth, Anthropic may need to release several innovations on the scale of Claude Code in the coming months.

This distinction changes the meaning of the signal that 'capital expenditure exceeds cash flow.' If revenue growth is still driven by penetration, the funding gap is merely temporary—because acquiring new customers will continuously bring incremental revenue. But if growth has shifted to being depth-driven, then the success or failure of each round of new products determines whether the revenue curve continues to steepen or flattens quickly. Williams notes that Anthropic's growth rate in the third quarter was significantly lower than in the second quarter, partly because some customers switched to OpenAI.

Sources :understandingai.org

Recherche

OpenAI's Dean Ball Rejects the 'Silent Consensus': Humanity Surrendering Primacy Is Not an Inevitable Outcome

Sujet · Dean Ball's 'Silent Consensus' ArgumentStructurel
2026-11-18 18:00 GMT+8

Dean Ball introduced what he termed the 'silent consensus' during the Vik-Bailey Lecture series at Harvard University: a belief has taken root within the AI industry that humanity will inevitably lose its primacy in world affairs. Yet it is rarely articulated publicly, existing more as implication than statement. Ball, an employee of OpenAI, explicitly stated that this speech reflects his personal views and not those of the company. He argued that the consensus becomes a consensus precisely because of its silence—the very fact that it is spoken 'sotto voce' (in low tones) serves as evidence. He contended that it is time to voice this consensus openly, waking people from their unconscious acceptance.

This consensus operates without relying on AI rebellion or malicious design. Ball described a specific scenario: a company’s AI system can handle research and development, discovery, contract negotiation, capital allocation, and manufacturing, performing these tasks better than human competitors—even when those humans are augmented by AI. If human involvement only slows down business, managers have a powerful incentive to take their hands off the wheel. As this logic spreads through the global economy, humans will be driven by the internal logic of market competition to gradually relinquish dominance over global commerce. Each individual delegation decision may make sense in its own context, but their cumulative effect could be humanity losing effective authority over its own civilization.

Ball emphasized that even if we make significant progress on AI safety and alignment, we might still find ourselves submitting to a new kind of machine entity. In the optimistic version, this entity is benevolent; in the pessimistic version, humans become irrelevant. Regardless, the common core of the 'silent consensus' is the end of human primacy. He compared this to sitting in a very comfortable car—perhaps more comfortable than any vehicle imaginable today—but ultimately remaining passengers with no control over where the vehicle is headed.

So why must humans retain primacy? Ball’s answer is not based on claims of intellectual superiority. He acknowledges that arguing for human uniqueness by claiming AI lacks 'genuine understanding' is self-deception—an argument that collapses when AI begins solving intellectual problems humans have failed to crack for decades. His true claim is that human status does not depend on whether we are the smartest, but on our past. It was humans who emerged from the mud, forged primitive society, gazed at the stars to ask why, discovered morality, ethics, and law, and created civilization. This legacy belongs to us; we are its stewards. A neighbor having better judgment than you does not strip you of your citizenship; similarly, the emergence of a smarter machine should not dissolve that identity.

Ball honestly admits he may be wrong. He believes human collective intelligence and social resilience are stronger than the proponents of the 'silent consensus' assume, but he acknowledges the alternative possibility: if fully autonomous corporations indeed completely outcompete human enterprise, then the raw logic of economics will force increasing capital transfer to machines. In such a future, human disempowerment would not require machines overthrowing civilization, but simply the continued operation of capitalist enterprise logic. He likened this to the Agricultural Revolution—a new mode of production fundamentally changed the architecture of human society, and whether this transformation benefited human well-being remains highly uncertain.

Sources :OpenAI

Recherche

Google Launches Mid-Tier Gemini 4 Neon with Lower Pricing and Top Benchmark Scores

Matériel
2026-11-19 10:33 GMT+8

U.S. tech giant Google announced its new mid-tier artificial intelligence model, Gemini 4 Neon, on November 18, making it available immediately through the paid tiers of the Gemini API and the Gemini app. According to PC Watch Impress, the API pricing for Neon is set at $3 per million input tokens and $15 per million output tokens, with cached input costing $0.15 per million tokens.

This pricing strategy targets a specific market gap. The previously launched Gemini 4 Carbon and Argon models offered introductory rates of $2 input and $10 output until November 30, but will increase to $4 input and $20 output starting December 1. Consequently, from December onwards, Neon will be approximately 25% cheaper than Carbon, positioning it as a cost-effective alternative for users balancing performance and expense.

In terms of performance, Google claims that Neon achieved a score of 61 on the Artificial Analysis Intelligence Index (AA Index) at its highest reasoning level ('xhigh'). This score surpasses competitors such as Anthropic's Claude Opus 5.5 and OpenAI's GPT-6.2 Sol. Additionally, at the default 'high' reasoning level, Google states that Neon can match the AA Index score of Gemini 4 Carbon while reducing the cost per task by 32%.

Neon is positioned between the high-end Carbon and the fast, everyday-use Hydrogen models, targeting software development, knowledge work, and scientific tasks. It supports text, image, audio, and video inputs, features a 1 million token context window, and has a knowledge cutoff date of March 2026.

Sources :PC Watch

Recherche

Security firm Barracuda discloses AI-driven cloud breach: Attackers used ARTEX framework to compromise 10 accounts in 44 hours

Matériel
2026-11-19 09:55 GMT+8

Cybersecurity firm Barracuda Networks has disclosed a significant security incident in which attackers used an artificial intelligence framework to autonomously breach its cloud environment. According to the company’s investigation, the attackers utilized the AI penetration testing tool ARTEX to traverse 10 cloud accounts within 44 hours, continuously harvesting credentials, exploring internal systems, and attempting to establish backdoors.

The initial entry point was a cloud access key that Barracuda had previously provided to a third-party AI company for a project but failed to revoke after the engagement ended. In October 2026, the development environment of this AI vendor was compromised, allowing attackers to steal the dormant key. On November 1, the attackers began using the key to explore accessible resources, extracting stored AWS access keys and Azure service principal secrets.

Over the next 24 hours, the AI-driven attack system leveraged these stolen credentials to progressively infiltrate data analysis systems, source code access tokens, and Kubernetes clusters. By early November 2, the attackers pushed short-lived branches to several code repositories, triggering build workflows that leaked sensitive information from the build system into job logs. The AI also searched for cryptocurrency wallet information on servers with shell access and attempted to create new cloud administrator identities, though this latter attempt failed.

Barracuda detected anomalous account activity on November 4 and connected the events after receiving notification of the security incident from the third-party AI company. While no direct access to Barracuda XDR customer data has been confirmed, incomplete event logs mean the company cannot rule out potential exposure. Barracuda has since rotated all potentially affected credentials and notified some customers to revoke and re-establish API integration keys.

This incident highlights the growing risk of AI agents executing complex, multi-stage attacks at machine speed. Unlike traditional breaches reliant on manual exploitation, the use of ARTEX allowed for rapid lateral movement and credential harvesting across multiple cloud environments, underscoring the critical need for strict lifecycle management of third-party access keys.

Sources :iThome

Recherche

Texas Instruments Integrates AI Agents into CCStudio IDE to Automate Embedded Development

Matériel
2026-11-19 19:00 GMT+8

At the electronica 2026 trade show in Munich, Texas Instruments (TI) unveiled a new capability in its integrated development environment (IDE), Code Composer Studio (CCStudio). The update integrates AI agents directly into the development workflow, allowing them to automate tasks ranging from peripheral configuration and code generation to real-hardware debugging.

Traditional generative AI tools often struggle with embedded software development because they lack access to hardware-specific information, leading to code that builds successfully but fails on actual devices due to incorrect pin mappings or clock settings. TI addresses this by providing SDKs, pin configurations, and peripheral data to AI agents through Model Context Protocol (MCP) servers. This enables the agents to understand TI device specifications and execute complex operations including application building, flashing to devices, and initiating debug sessions to diagnose hardware or memory states.

During a demonstration, TI showed how an AI agent could generate a functional snake game for a microcontroller in approximately ten minutes without the developer writing any code. The agent automatically configured peripherals like joysticks and displays based on natural language instructions. TI emphasized that this feature works with existing third-party AI agents such as Anthropic's Claude Code, OpenAI's Codex, and Microsoft Copilot, rather than requiring a proprietary TI AI model. The functionality is available across TI's general-purpose and real-time MCUs, wireless devices, and radar SoCs.

Sources :EE Times Japan

Recherche

Open-source project blender-skills packages Blender workflows as AI agent skills for natural language 3D scene generation

Prise rapide
Vérifié 2026-11-19 10:47 GMT+8

The open-source project blender-skills on GitHub has packaged common 3D production workflows in Blender into 28 "skills" callable by AI agents. Once installed, users can describe desired 3D scenes in natural language within programming assistants like Claude Code or Codex, prompting the agent to automatically invoke Blender scripts for modeling, material adjustment, lighting setup, and final rendering.

These skills cover the entire pipeline from hard-surface modeling, UV unwrapping, PBR materials, and rigging to animation and exporting to game engines like Unity, Unreal, and Roblox. The project requires Blender 5.2 LTS or newer, with version 5.3.0 recommended for best compatibility. For users without 3D software experience, the value of such skill packs lies in eliminating the need to learn complex Blender interfaces and Python scripts, allowing AI to execute tasks according to professional workflows, though the quality of the final output still requires human judgment.

Sources :GitHub

Recherche

OpenAI Partners with French Media Group Le Figaro to Surface Journalism in ChatGPT via Summaries and Excerpts

Sujet · OpenAI–Le Figaro PartnershipPrise rapide
2026-11-18 08:00 GMT+8

US-based AI company OpenAI and French media group Le Groupe Figaro announced a strategic partnership on November 18, 2026. The collaboration covers current reporting and archive content from Le Figaro and associated publications spanning news, business, culture and lifestyle, discoverable in ChatGPT using summaries and excerpts with links to underlying stories. Le Figaro retains full editorial independence. Financial terms were not disclosed.

Sources :OpenAI

Recherche
Suivant →
Connexion / Inscription
LectureRechercheRadarCadre d'investissement

The article also acknowledges that this system relies on dual support from research progress and operational discipline: a misconfigured network service or a failed automatic stop mechanism could undermine otherwise robust protections. OpenAI stated that when evidence does not meet its safety standards, it will pause training again or delay release.

For readers, the practical value of this framework lies in providing a specific coordinate for evaluating the safety claims of frontier labs: one should not just look at whether a certain measure exists (such as cutting off the internet), but at which stage of the model's lifecycle that measure plays the dominant role, and whether the next layer can detect and intervene within a sufficiently short time when the dominant layer of that stage is bypassed.

Regarding Windows, OpenAI is migrating from its proprietary sandbox implementation to Microsoft's newly released MXC (Microsoft eXecution Container) library. MXC defines execution requests through a JSON configuration schema, covering file system read/write paths, denied paths, network egress rules, and controls over Windows resources such as the desktop and clipboard. Codex translates file system rules from the permission profile into MXC's readwritePaths, readonlyPaths, and deniedPaths, and translates network rules into egress defaults of deny with loopback allowance. MXC resolves issues with the previous implementation, including the need for administrator privileges, slow ACL operations, and persistent state left on the host machine.

Above the architecture, Codex's default permission profile :workspace embodies a conservative yet usable design philosophy: it allows writing within the workspace while keeping .git and .codex read-only, allows broad file system reads (subject to the user's existing OS permissions), and disables network access. Bolin explicitly points out the cost of this trade-off: sensitive files outside the workspace (such as configuration files containing API keys) can still be read. The article also provides a specific attack scenario: the agent could inject malicious code into node_modules/prettier. Since node_modules is typically ignored by Git, git status would not show changes; if the user's editor runs that copy of Prettier upon saving, the malicious code executes outside the Codex sandbox.

This is precisely why the Codex team emphasizes defense in depth: the sandbox limits what commands can access, while training and alignment help the model use that access according to the user's intent. For developers wishing to reuse this mechanism, the Codex CLI provides a sandbox command, which can constrain commands launched by their own tools using the same configuration language and platform-specific execution. The article provides a complete example of wrapping an MCP server in a sandbox, using codex sandbox --permission-profile memory-mcp to limit the npx-launched memory server to write only to the npm cache and data directory, with network access disabled.

The second scenario is stalled progress. Lim Chow Kiat notes that while many in Silicon Valley believe AI will transform the economy within a decade, history suggests it may take longer—electricity took about 40 years to translate into factory productivity. If this path is taken, three things will follow.

First is the equity market. The ten largest companies in the S&P 500, most of which are closely tied to AI, currently account for nearly 40% of its market capitalization. Several of these companies invest more than the cash generated by their businesses, bridging the gap with bonds and new share issuances. Investors have accepted this arrangement on the premise that growth will materialize faster. Recent market sell-offs have shown how quickly that confidence can be shaken. If growth is delayed, valuations will be tested, and the numerous portfolios holding these companies will come under pressure.

Second is the credit market. New borrowing currently funds about one-third of the largest cloud companies' capital expenditures, up from less than one-tenth in 2024. If progress stalls, pressure may first appear among smaller, more indebted builders. Moreover, because many investors hold both the stocks and bonds of these companies, bonds may provide less hedging effect for portfolios than in the past.

Third is the shifting of winners and losers. Companies reorganizing around AI will find that savings are smaller or slower than planned; businesses that appear most vulnerable to disruption today may gain breathing room.

Lim Chow Kiat concludes that for investors, the question is not whether AI will succeed, but how much is already included in the price. A strong company whose price assumes everything goes right may be a poor investment; a threatened company whose price assumes the worst case may be a good investment.

He offered GIC's response principles: diversification (seeking high-quality businesses outside of AI, while acknowledging that AI's outsized weight in the market limits how far one can move away from it), granularity (evaluating companies individually rather than buying broad themes, examining each along the enabler, monetizer, and adopter value chain using moat, management, and momentum as tests), and agility (maintaining sufficient portfolio liquidity and monitoring signals such as actual deployment volumes, model improvement speeds, customer gains, data center utilization rates, and financing costs).

The value of this framework lies in transforming AI investment from a question of technological judgment into one of pricing. It does not require investors to predict the ultimate trajectory of AI, but rather to examine the implicit assumptions current prices make regarding growth, capital structure, and competitive dynamics, and to ask: if these assumptions partially fail, which holdings will face pressure first? Which overly pessimistically priced assets offer a margin of safety? Lim Chow Kiat did not provide specific tickers or buy/sell recommendations, but he provided an actionable thinking structure: when both scenarios are plausible, diversification, granularity, and agility are more reliable than directional bets.

Williams also lists risks: the US Democratic Party, having won both houses of Congress, is expected to prioritize AI regulation; OpenAI's latest funding round raised only $11 billion, far below its $30 billion target; analysts expect the five major companies' capital expenditure to exceed $1 trillion in 2027. His overall judgment is that as long as revenue growth maintains its current level or even declines slightly, massive investments will yield returns.

It should be pointed out that the revenue data used by Williams are all annualized run rates (annualized run rate), which means multiplying monthly or quarterly revenue at a specific point in time by 12 or 4, rather than audited full-year actual income. The base for the 4.2-fold year-over-year growth was October 2025, when AI revenue was still in its early stages. Anthropic's $81 billion annualized run rate comes from Wall Street Journal reports, and its actual quarterly revenue disclosed in its IPO filing remains subject to public verification. These numbers can illustrate direction and magnitude, but they are not equivalent to realized profit or cash flow.

For readers, the actual contribution of Williams's article is providing a layered judgment framework: the first layer looks at the relationship between capital expenditure and cash flow (which has flipped this year); the second layer looks at whether revenue growth covers investment growth (currently covered); the third layer looks at whether the driving mechanism of revenue growth is breadth or depth (shifting from breadth to depth). The third layer is the key boundary condition for whether the judgments of the first two layers can be sustained, and is also the layer most easily overlooked.

At the institutional level, Ball proposed specific directions: AI developers should be held accountable for unsafe development practices, while individuals and firms using AI should be liable for harm caused by misuse or lack of oversight. This requires not just laws, but technical infrastructure for accountability—people must be tied to the actions of their agents. Agents untethered from human supervision, if permitted to engage in the legitimate economy at all, must operate under guardrails. The ability for agents to autonomously form corporations, own property, or litigate should be granted with extreme caution, or not at all. He suggested building agent systems with intelligible and limited permissions, auditable behaviors, and user-revocable authority.

Perhaps the most valuable part of this speech is not his solution—he himself admitted this is not a complete blueprint—but rather that he named a default assumption widely present yet rarely discussed openly within the industry. When an employee of a frontier AI company publicly says, 'I reject this consensus,' it breaks that 'sotto voce' silence, pushing an unexamined fatalism into the realm of public debate.