AI Engineer World's Fair 2026

Open Source Is Dead. Long Live Open Source.

Loading slides…

Read the talk

Open Source Is Dead. Long Live Open Source.

Cheap code strains the trust behind open-source contributions, while expensive inference makes open weights increasingly valuable as a foundation for competition.

From a talk by Saoud Rizwan

Why trust mattered when every request cost money

Before prompt caching and coding-agent subscriptions, an agent that could finish a developer’s work could also generate an alarming bill. Saoud Rizwan recalls some early Cline users spending hundreds of dollars a day on individual API requests. He describes Cline as the first coding agent, preceding Claude Max and Codex subscriptions. For those users, watching an LLM perform work end to end was compelling enough to keep paying.

Open source made that expense easier to trust. Developers could inspect the code and connect their own API provider, seeing what the agent did and where their money went. The community also shaped the product: Rizwan credits conversations with contributors for custom rules and plan mode, features he says Cline introduced first. Openness supported both adoption and product development because users could understand the system and help improve it.

0:180:37
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:18 · section reference included

When contributions stop building contributors

The same technology now puts pressure on the relationships that helped Cline grow. Generating a pull request, issue or security report is cheap; determining whether it deserves attention still consumes a maintainer’s judgment. Rizwan describes a community increasingly skeptical of whether strangers have used AI responsibly. Projects that depend on third-party contributions inherit that uncertainty with every submission.

Zig, the language used to build Bun, provides the sharpest example. The displayed code of conduct highlights a strict prohibition on LLM and AI use; Rizwan describes its scope as pull requests, issues and comments. His explanation is that Zig values developing contributors more than acquiring individual contributions. Reviewing a patch is an investment in someone who can eventually become a trusted collaborator. If AI assistance obscures what that person understands, the review no longer serves the same purpose.

Zig Code of Conduct page with a red outline around “Strict No LLM / No AI Policy.”Open full source frame
Zig’s code of conduct highlights a “Strict No LLM / No AI Policy.”

Other projects have restricted the incoming work itself. Rizwan cites curl’s flood of AI-generated security reports and the possibility of ending its bug bounty. That account describes an earlier stage: Daniel Stenberg’s subsequent update says the bounty ended in February 2026. The tldraw contribution policy temporarily closes external pull requests automatically, with selective reopening, while retaining issues, bug reports and discussions. GitHub also introduced controls to disable pull requests entirely or restrict their creation to collaborators with write access. These are different degrees of restriction, rather than a single decision to abandon all community participation.

The part of open source under pressure is the cultivation of trust. Rizwan’s claim that open source is dying concerns the economics of maintaining those relationships when producing software becomes cheaper but evaluating unfamiliar contributors remains costly. It does not mean that published source code has stopped being useful.

1:281:45
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

1:28 · section reference included

One compromised dependency reaches downstream

Trust also extends through the software supply chain. An application can depend on a long sequence of maintainers, build tools and publishing systems; compromising one of them can deliver malicious code to downstream users. Rizwan uses the LiteLLM Python package to make this exposure concrete, describing roughly 3.5 million daily downloads and a malicious-release window of about three hours. Download volume indicates the package’s reach, not the number of infected users.

The attack crossed several trust boundaries. The documented entry point was compromised Trivy tooling in LiteLLM’s CI pipeline, refining Rizwan’s shorthand description of a GitHub app compromise. Stolen PyPI publishing credentials allowed attackers to distribute malicious releases. Once installed, the payload collected API keys, SSH keys and cryptocurrency credentials, and attempted to establish persistent access for remote command execution. The diagram follows that path from a security tool through publishing access to users’ machines.

Six connected steps show compromised Trivy, LiteLLM’s CI/CD pipeline, secret exfiltration, stolen publishing access, malicious packages, and theft of user keys with backdoor installation.Open full source frame
A diagram traces the compromise from Trivy through LiteLLM to credential theft and a backdoor.

Discovery depended on a defect in the malware. Rizwan describes a Cursor crash involving MCP; the discoverer’s account more precisely identifies a Cursor MCP plugin that pulled LiteLLM as a transitive dependency, followed by recursive Python startup that crashed the machine. A researcher investigated the failure and uncovered the payload. For enterprise users operating internal LLM gateways, the potential exposure extended beyond a disposable development environment to credentials for other systems. Rizwan characterizes the quick discovery as luck, rather than evidence that the dependency chain reliably caught the attack.

3:564:14
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

3:56 · section reference included

The value that survives: using and building on the work

The ability to use someone else’s work and build on it remains valuable even as contribution channels become harder to maintain. That freedom comes through the applicable license; open source does not necessarily mean public domain. For model weights, openness has an additional economic consequence: more organizations can participate in serving and optimizing the same model. The reason to care becomes clearer when inference bills reach organizational scale.

Rizwan cites an anonymous CFO account alleging that an unnamed company spent $500 million on Claude in one month after failing to set usage limits for thousands of employees. The anonymous account cannot establish a typical enterprise bill, but its failure mode is straightforward: broad access without spending controls can turn individual usage into an organization-wide liability.

In a separate report attributed to Uber’s CTO, Rizwan cites 95% engineer adoption, 70% of committed code coming from Claude, monthly spending of up to $2,000 per user, and exhaustion of the entire 2026 budget in four months. These are reported figures, not independently established measurements here. Together they illustrate the transition from experimenting with an assistant to budgeting for infrastructure that engineers use throughout their work.

5:225:36
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:22 · section reference included

Subscription value can become application dependence

Subscription pricing can conceal how much inference a workflow consumes at retail API rates. Rizwan describes SemiAnalysis experiments that ran long-horizon coding tasks in Claude Code and Codex until their weekly subscription limits were exhausted. He reports the following API-equivalent values:

SubscriptionReported API-equivalent usage
$200 Claude planAbout $8,000
$200 Codex planAbout $14,000

These figures describe retail API-equivalent usage under that workload, not measured provider costs or losses. The account does not resolve the measurement period, extrapolation or caching assumptions behind the totals.

Rizwan interprets this pricing as a subsidy intended to establish dependence. Agents in CI, background agents and looping agents introduce more places to spend tokens, and each new workflow can make a particular application harder to replace. His predicted next step is higher prices once developers cannot comfortably work without the tools; that prediction is separate from the subscription experiment.

The audience gets a more immediate test of dependence: who stops working during a Claude or GPT outage? Rizwan includes himself among those affected. In his reading, Anthropic and OpenAI’s investment in applications gives them a potential moat even if competing models converge in capability. The durable asset would be the workflow surrounding the model, rather than exclusive access to intelligence.

6:276:43
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

6:27 · section reference included

Put more intelligence into the development system

That application moat may prove weaker than expected if developers can obtain adequate results for less money elsewhere. Rizwan acknowledges that many open-weight contenders, including models developed in China, have historically trailed the leading closed models. His proposed inflection point is practical sufficiency: a business does not need the strongest available model for every task, and better CLI features may not outweigh a large difference in operating cost.

Model capability is only one part of an agent’s result. The surrounding system determines what information the agent sees, what it can do and what counts as completion:

  • Context and tools: Give the agent the project information and operations needed to solve the task.
  • Skills and rules: Encode project conventions and reusable procedures instead of relying on the model to infer them each time.
  • Verification and quality gates: Require checks of the resulting work before accepting completion.

Rizwan argues that this infrastructure can help a less capable model produce results similar to a stronger one.

The tradeoff may be more tokens: extra investigation, tool use and verification can compensate for weaker initial judgment. If those tokens are cheaper, the additional work can still cost less. Placing expectations and checks in the system also reduces reliance on each developer remembering to use the model responsibly. The goal is to make successful completion a property of the development process, not merely the agent’s confidence.

8:068:24
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:06 · section reference included

The same bug, different definitions of done

Skeptical of benchmarks placing GLM ahead of Opus, the Cline team tried both on a real bug in the Cline repository. Rizwan presents this as a single-task anecdote. Both models addressed the issue, but their cost and completion behavior differed.

DimensionGLMOpus
Tokens usedTwice as many as OpusHalf as many as GLM
CostAbout half of OpusAbout twice GLM
Completion speedSlowerFaster
Tool callsTwice as many as OpusHalf as many as GLM
Verification and cleanupRemoved dead code; checked compilationLeft type errors; broke the production build

Rizwan reports these results for the same Cline repository bug. The completed slide labels the runs GLM-5.2 and Opus 4.8, with costs of $0.41 and $0.81 respectively. Its build outcomes make the practical distinction visible: addressing the reported issue was not sufficient if the resulting project could not build.

Slide titled “Fixing the same bug. Half the cost.” Purple GLM-5.2 bar reads $0.41 and “builds clean”; orange Opus 4.8 bar reads $0.81 and “breaks the build.”Open full source frame
The bug-fix comparison shows GLM-5.2 at $0.41 with a clean build and Opus 4.8 at $0.81 with a broken build.

The team inferred that GLM had been trained to spend more tokens verifying its output. The observed behavior supports the narrower conclusion that this run did more verification; it does not establish the training cause. For the workflow, however, the economic point remains useful: a slower run with more tool calls can be preferable when it costs less and leaves a working build.

9:289:45
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

9:28 · section reference included

An internal gateway makes switching practical

The same economics can shape enterprise defaults. Rizwan cites Coinbase CEO Brian Armstrong as saying that Coinbase’s internal LLM gateway defaulted to GLM and Kimi, nearly halving AI spending while token usage continued to grow. In that account, lower spending did not require using AI less; it came from changing which models served the work.

An internal gateway gives the organization a place to make those routing decisions without standardizing every workflow on one model vendor’s application. Rizwan expects businesses to build internal tooling around dollar efficiency, even when that means forgoing a newly released Claude Code feature. The relevant comparison becomes the cost of getting the organization’s work done through its own system.

10:1810:38
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:18 · section reference included

Open Compute changed what suppliers manufactured

Rizwan’s historical analogy is the Open Compute Project. In his account, Facebook developed data-center infrastructure around 2011, but Amazon and Google had already built enough of their own that the work no longer provided a distinctive competitive advantage. Facebook released designs for servers, data centers, networking and cooling hardware, including schematics and CAD files. Publishing the designs let other buyers and manufacturers build around the same work.

The mechanism is a change in production economics:

Before shared designsWith a shared standard
Buyers specify proprietary hardwareBuyers order common designs
Manufacturers make small custom runsManufacturers make larger standardized runs
Custom components support vendor premiumsInterchangeable supply constrains premiums

As demand converged, manufacturers could spread their effort across larger production volumes. Rizwan credits the resulting market with lowering costs for the wider industry and saving Facebook billions of dollars. Giving away the design could therefore reduce the originator’s own future purchasing costs.

The lesson he draws is that the industry can standardize on something it can build upon even when it is not the strongest option in every technical dimension. For open weights, the corresponding opportunity is to let many providers invest in making the same models cheaper and easier to serve.

10:5711:13
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:57 · section reference included

More capacity, more ways to lower inference cost

Rizwan cites forecasts of nearly $3 trillion in AI infrastructure spending and more than 100 GW of new data-center capacity by 2030, roughly doubling global capacity relative to the talk’s present. These are projections rather than completed investments. His expectation is that the build-out will give inference providers more infrastructure on which to compete.

Providers such as Baseten and Fireworks can compete to serve open weights more efficiently through several complementary mechanisms:

  • Dedicated hardware: Match the serving environment to a known workload.
  • Caching: Reuse eligible computation rather than repeating it.
  • Batching at volume: Combine work to improve hardware utilization.
  • Inference-specialized silicon: Use hardware designed around inference requirements.

Open weights allow multiple hosts to pursue these improvements for the same model, exposing more of the efficiency gains to competitive pricing.

A further forecast cited by Rizwan puts inference for a one-trillion-parameter LLM at 90% lower cost by 2030 than at the time of the talk. The originating assumptions are not specified, so the forecast supplies a direction and scale for his argument rather than a dependable price schedule.

12:3412:54
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:34 · section reference included

Cloud competition moved beyond raw compute

Cloud pricing supplies a second precedent. Rizwan recalls Google’s March 2014 GCP Live announcement cutting compute prices by 32% and storage prices by 68%, followed within days by what he describes as AWS’s 42nd price cut. In his account, competition from 2015 onward increasingly shifted toward databases and serverless services as basic compute and storage became commodities.

He expects open-weight inference to follow a similar path: hosts compete aggressively on serving efficiency, customers adopt the models that make economic sense, and differentiation moves elsewhere. His prediction is that foreign open-weight models will gain broad adoption as closed-lab API premiums become harder to justify for much knowledge work. That outcome depends on adequate task performance as well as price; cheaper tokens alone do not complete the job.

13:2013:39
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

13:20 · section reference included

Release weights without giving away the research lead

The strategic concern follows from standardization. If the infrastructure now being built converges on foreign open-weight models, later marginal improvements in GPT, Claude or Gemini may provide too little reason to switch. Rizwan urges American labs to take open weights more seriously while adoption and developer mindshare remain contestable.

He also connects leadership to the values of the organizations and countries developing the technology. He worries that losing Anthropic and OpenAI’s influence would diminish the role of their safety-research investment. This is his rationale for wanting those labs to remain central to the ecosystem, rather than a technical finding about the safety of particular models.

His proposed distinction is between releasing model weights and releasing the research that produces the next model. He regards the latter as the source of a continuing lead. Weights can make it easier to extract traces and train imitation models, but he argues that this does not by itself give a competitor the ability to leapfrog the originator. In his proposal, broader hosting competition, adoption and customer value would help preserve leadership by making the models useful foundations for the rest of the industry.

14:2214:39
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:22 · section reference included

Cline’s bet on competing providers

Cline’s closing announcement applies that thesis to its own offering. Rizwan says the team launched an open-weight subscription earlier that week, using volume discounts and partnerships with inference hosts to offer lower costs than direct API usage. The slide names the offering ClinePass. He says Cline plans to increase usage quotas as serving costs fall, and points to GLM and DeepSeek as models developers can try through it. No numerical subscription price or quota is given in the presentation.

ClinePass slide with the text “The best open weights subscription,” cline.bot/pass, and surrounding DeepSeek, Qwen, Kimi, GLM, MiMo, and Minimax labels.Open full source frame
ClinePass presents an open weights subscription at cline.bot/pass.

The subscription sits alongside Cline’s open-source agent and bring-your-own-key access to other providers. Rizwan lists CLI, VS Code and JetBrains interfaces; the current Cline site labels JetBrains support Early Access. Provider choice remains part of the product rather than requiring every user to adopt the subscription.

Cline also continues adding newly released models so developers can compare what improved capability means for their own work, including open-weight models outside Claude and ChatGPT subscriptions. That is the concrete version of the closing economic argument: keep the development environment usable across providers, and let models compete on the results and value they deliver inside it.

16:0116:18
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:01 · section reference included

Resources

From the talk

Updates since the talk

Transcript download
Full transcript

Loading transcript…