We turned Claude Code's spinner into a live newsfeed and an open ad market

Why it matters

AI agents are creating new wait states inside developer tools. RuntimeWire is betting those seconds are better used for timely technical news than empty spinner text, while still giving developers a share of disclosed ad revenue.

Every Claude Code user knows the moment.

You fire off a prompt, the agent starts thinking, and the interface begins its tiny ritual: Simmering..., Discombobulating..., some other whimsical gerund, then another few seconds of waiting while a real chunk of your day quietly disappears into the spinner.

That line is usually treated as decoration. We think it is distribution.

Multiply that little pause across every developer running AI agents all day, and the "thinking..." state becomes one of the most-watched, least-used surfaces in software. It is not quite editor chrome, not quite terminal output, not quite an ad slot. It is the place where work stalls and attention concentrates.

Somebody was always going to monetize it.

We just did not expect the somebody to be this funny about it.

Credit where it is due: Kickbacks

A few days ago, Andrew McCalip introduced Kickbacks with a perfect line: "Get paid to wait."

The pitch was simple and absurd enough to be obvious in hindsight: turn the Claude Code spinner into an ad marketplace, let advertisers bid on the slot, and share the money with the developer whose machine displayed the ad.

It is, genuinely, a clever piece of work.

Kickbacks named the insight before anyone else did: agent wait-state is inventory.

That matters because it proves the surface is real. Developers will tolerate a commercial message in a spinner if it is lightweight, disclosed, outside the model context, and pays them back. They may even enjoy it.

We loved it the moment we saw it.

We also saw a different version of the idea.

The turn: do it news-first

RuntimeWire is a newsroom.

We publish AI and startup news all day: model releases, funding rounds, infrastructure shifts, executive moves, developer-platform changes, and the small technical signals that tell you where the AI economy is headed next.

So when we looked at the Claude Code spinner, we did not see a blank ad slot waiting for a buyer.

We saw a place to put the wire.

Today we shipped RuntimeWire for VS Code, a free extension that adds RuntimeWire's rotating AI and developer-news headlines to Claude Code's status line and thinking-spinner verbs, so you see a fresh headline while Claude works.

The before-and-after is simple.

Stock

✳ Simmering... (esc · 3.0s)

With RuntimeWire

◆ Nemotron 3 Ultra edges GPT-5.5 Pro on agentic coding · 3.4s

With a sponsor

◆ [AD] Linear · ship faster · 3.4s

The extension uses Claude Code's exposed configuration surfaces. It edits only statusLine and spinnerVerbs, does not patch Claude Code itself, and can restore your previous settings at any time.

The privacy posture is intentionally narrow.

RuntimeWire fetches the public news feed and, when enabled, reports sponsored impressions for attribution and fraud prevention.

It does not need your code.

It does not need your prompts.

It does not need your completions.

How RuntimeWire is different

1. News first, ads second

This is the whole philosophy.

The default payload is not an ad.

It is the news.

That means the extension is useful even on a day when no sponsor serves. Your spinner becomes a lightweight AI-news ticker: a model drop, a funding round, a pricing change, an infrastructure outage, a benchmark fight, a developer-tool launch.

The sponsorship rides on top of something valuable.

It is not the only reason the product exists.

That distinction matters. A spinner that is only an ad slot will eventually feel like one. A spinner that keeps you informed can earn the right to occasionally carry a sponsor.

2. The market is visible

Kickbacks was right that an auction is the right way to price this kind of attention.

A flat rate either leaves money on the table or locks out smaller advertisers.

We agree with that.

RuntimeWire's BID MARKET takes the same basic intuition and puts it at the center of the advertiser experience.

Advertisers can see:

• The live going rate
• How many campaigns are competing
• Ranked top bids
• Historical pricing trends

Bidding starts at $1 CPM.

The suggested opening bid is $5 CPM.

The highest bid serves first.

The goal is to make the market legible.

No mystery rate card.

No "talk to sales" pricing fog.

No black box where advertisers bid blind and developers have to trust that the market is real.

If a sponsor wants the slot, they can see what it costs to win it.

If a developer wants to understand why their earnings moved, they can see the same market pressure.

3. Advertisers can launch today

The advertiser portal is live now.

You can:

• Build a native sponsored unit
• Target by placement, country, device, and IDE
• Set or raise your bid against the live market
• See an estimated total before committing
• Fund a prepaid budget with Stripe
• Go live after editorial review

You can also come back later and raise your bid if you want to climb the rankings.

That is important because this only works if the ad side is as lightweight as the developer side.

The whole promise of this format is that it is native, fast, and low friction.

Buying it should feel the same way.

4. Developers get the revenue share

Install the extension, sign in, connect Stripe from the publisher portal, and sponsored impressions begin accruing to your balance once ads serve.

RuntimeWire shares 50% of sponsorship revenue with the developer whose Claude Code session displayed the sponsored unit.

Our view is simple:

If your attention creates the inventory, you should participate in the economics.

5. Editorial standards come with the wire

RuntimeWire is not an ad network that happens to have headlines.

It is a newsroom with a sponsored layer.

That means the wire has to stay clean.

• Headlines are curated
• Sponsored units are labeled AD
• Brand copy has to fit the surface
• Editorial and sponsorship remain separate

We are not turning the spinner into a blinking billboard.

The line is small.

Trust is smaller.

We intend to protect both.

For advertisers

If you want to reach developers at the exact moment they are waiting on an AI agent, RuntimeWire's advertiser portal is open.

Build a native unit, choose your targeting, place a bid, and watch the BID MARKET to see where you stand.

You prepay a budget through Stripe, and spend draws down as impressions serve, so there is no surprise bill at the end.

A short editorial review keeps the wire clean.

After that, your sponsor line can run directly inside the Claude Code wait-state, alongside real AI and developer news.

This is not a banner ad.

It is not a newsletter slot.

It is not a social feed unit fighting a thousand other things on the screen.

It is one line, in the moment when the developer is already watching.

For developers

Install RuntimeWire from the VS Code Marketplace and your Claude Code spinner becomes a live AI-news ticker.

You do not have to sign in to get the headlines.

The feed works either way.

Sign in only if you want to enable the revenue share.

Add your publisher key, connect Stripe, and your share accrues as sponsored impressions serve.

You can disable the extension and restore your prior settings at any time.

Get the latest AI news where you code.

Earn from the sponsor layer when sponsors run.

Go back to work.

Why this matters

Agentic coding is creating new attention surfaces.

Some are obvious:

• Chat panes
• Diff views
• Review screens
• Plan approvals

Others are quieter:

• Progress bars
• Status lines
• Terminal pauses
• Thinking animations

Those moments are going to become economic.

The question is whether they become ugly.

The worst version of this future is easy to imagine:

• Noisy ads
• Hidden auctions
• Shady attribution
• Telemetry creep
• Sponsor copy disguised as product output
• Developers getting nothing

The better version is also possible.

The surface can be useful first.

The ads can be disclosed.

The market can be visible.

The developer can share in the money.

The newsroom can protect the editorial layer.

That is the version we want to build.

What is next

RuntimeWire for VS Code works today with Claude Code in VS Code and Cursor.

Terminal CLI support is on the roadmap.

We are also expanding the BID MARKET, adding more publisher controls, tightening advertiser review, and building more ways for developers to tune the feed without turning the spinner back into dead space.

Kickbacks deserves real credit for the spark.

It saw the spinner clearly before the rest of us did.

It proved that the wait-state could be inventory, that developers might accept sponsorship there, and that the economics could be shared.

RuntimeWire is taking that idea in a newsroom direction.

The news comes first.

The market is out in the open.

The money goes back to the people watching the spinner.

Install RuntimeWire

VS Code Marketplace:

https://marketplace.visualstudio.com/items?itemName=runtimewire.runtimewire

Advertise on RuntimeWire

https://runtimewire.com/advertise