Thunders Copilot was the right name for where we began. It described an assistant-like experience that helped users author tests and move faster inside the product.

Thunders AI is the right name for where we’re going.

What we’re building is no longer a copilot. It is becoming the central way users interact with Thunders. A single interface through which users will increasingly be able to understand, investigate, manage, and execute within the product.

That is why “copilot” no longer describes the role this system plays.

Why we’re moving away from “Copilot”

There are practical reasons, and there are product reasons.

First, the term has become crowded. It is widely used, often associated with Microsoft, and increasingly generic across software. It does not give users a clear sense of what makes our product distinct.

More importantly, it understates the direction of the product.

What we are building is not a helper sitting on the side of Thunders. Users are not simply asking it to author tests. They are increasingly using it to work through Thunders itself.

That shift calls for a name that can grow with the product.

Why “Thunders AI”

Thunders AI is the simplest and most accurate name for what this product is becoming.

It is broad enough to encompass what exists today and what is coming next. It does not lock us into a narrow metaphor. And it creates a clearer product hierarchy: Thunders as the platform, and Thunders AI as the intelligence and conversational interface through which users increasingly operate it.

It is also the name that best matches the ambition.

What Thunders AI is becoming

Today, Thunders AI already helps users author tests, work from context, and interact more naturally with the platform.

Over time, its role expands.

It becomes a place where users can:

• understand what is happening in their workspace
• investigate issues and failures
• manage test assets and workflows
• execute actions directly through conversation

Our ambition is for Thunders AI to become the colleague you can tag anywhere to get your testing work done.

What stays the same

The mission does not change.

We still believe that if something can be tested, Thunders should help make that possible with more intelligence, less friction, and a more natural way to work.

What changes is the name. It now reflects the scope of that vision more clearly.

Looking ahead

We are not building a copilot feature.

We are building a new way to interact with Thunders.

And that is why Thunders Copilot is becoming Thunders AI.

‍