Spock is becoming your AI workspace.

Over the last few days, we explained why we are building a new Spock and what will feel different in the new product.

Today we want to answer the practical question:

What happens to current Spock and your existing work?

The short version is this: current Spock remains fully usable during the new Spock beta.

Your existing Spock work is not disappearing.

You do not need to move anything today.

We are targeting Tuesday, 19 May 2026 for the public beta of new Spock, if the product and support path are ready. When beta opens, you will be able to access it from a clear beta button inside current Spock.

Beta means we expect people to use the new product, but we will still be watching feedback closely and improving it before making it the default.

We are also targeting Tuesday, 26 May 2026 for new Spock to become the default, if the beta is ready. That date is still tied to readiness. We will not make the switch if the product, support path, or transition details are not ready.

Even if that default switch goes ahead, current Spock will remain fully usable for at least two weeks after the switch.

That means you will not lose access to current Spock when the beta opens, and you will not be forced to abandon your current work the moment new Spock becomes the default.

Your existing work

Anything you have already built or used in current Spock remains available through current Spock during the beta.

That includes the practical things users actually care about: chats, files, memory, agents, flows, automations, instructions, and other work already inside current Spock.

We are still finalising the best way to handle that existing work inside the new Spock.

Some things may move across directly. Some things may work differently in the new product. Some things may need a new setup inside new Spock so they can take advantage of the new foundation.

We are not going to surprise users with this. We will keep communicating as the transition progresses, and we will explain the practical path before users are asked to rely on the new Spock as the default.

For now, the practical guidance is simple:

• keep using current Spock for work you already rely on;
• try new Spock during beta when it opens;
• tell us where the transition feels unclear or where a current workflow matters to you.

What we are still finalising

New Spock has a different foundation. It is built around Spaces, stronger file/context handling, and a new memory/context system.

Because of that, we are being careful about how existing work is handled.

The important point for users is not the internal migration method. The important point is this:

• your current Spock work is not disappearing;
• current Spock remains fully usable during the transition;
• we will communicate the details before anything changes;
• we want to know which workflows matter most so we can handle the transition properly.

Business users

Business users are on the same transition timeline as individual users.

If your company relies on a specific Spock workflow, please tell us. Business workflows can be more sensitive because they may involve multiple people, repeated tasks, files, or client work. We want to understand those workflows early instead of discovering them after the switch.

What you need to do today

Nothing.

You can keep using current Spock normally.

When the public beta opens, you will be able to try new Spock from inside current Spock. If you prefer to wait, current Spock will remain fully usable.

If there is a current Spock workflow you rely on, please tell us through support@spock.chat, the in-app live chat, or the WhatsApp group if you are already part of it.

What happens next

On Monday, 18 May 2026, we will share the next update with the public beta access details, assuming the beta is ready.

That update will explain:

• how to open the beta;
• what to try first;
• what is still beta;
• how to return to current Spock;
• how to report issues.

Questions: support@spock.chat, in-app live chat, or the WhatsApp group if you are already part of it.

The Spock Team

Yesterday we explained why we are building a new Spock.

Today we want to explain what will feel different when you open it.

The biggest change is this: new Spock gives your work a place.

That place is called a Space.

A Space is where related work lives in Spock. It gives Spock a home for the chats, files, and context that belong together.

You can still just chat with Spock. That is not going away. The difference is that the chat now sits inside a clearer work context.

When you open the beta, the experience may feel different in a few practical ways:

• You may start inside a Space instead of a blank standalone chat.
• You may see a short setup step so Spock understands what the Space is for.
• Files will feel more central to the workflow.
• You will still be able to ask normal questions.
• Spock will have stronger tools underneath the chat for files, search, documents, spreadsheets, images, and integrations where enabled.
• WhatsApp is becoming part of the broader Spock experience.

But Spaces are only one part of what is changing.

The new Spock also has a stronger agent underneath it. It can use tools, work with files, search across the context in a Space, use web search when needed, help with spreadsheets, create or edit documents and images, and connect to services like Google and Microsoft where those integrations are enabled.

We have also added WhatsApp support as part of the new product. We will explain exactly how that works closer to beta, but the direction is simple: Spock should be useful through the channels where people already work, not only inside one web page.

The practical version is:

• You will still be able to message Spock normally.
• Your work will now happen inside a Space.
• A Space keeps related chats, files, and context together.
• Files will feel more central to the workflow.
• Spock has stronger tools and integrations underneath the chat.
• WhatsApp is becoming part of the new Spock experience.
• Current Spock remains fully usable during the beta period.

You do not need to move anything today.

We are still targeting Tuesday, 19 May 2026 for public beta, if the product and support path are ready. When beta opens, you will be able to try the new Spock from a clear beta button inside current Spock.

Tomorrow we will share more practical transition details: what happens to current Spock, how existing work will remain available, and how we will communicate the transfer path before anything changes.

If you have questions or need help, you can reach us at support@spock.chat, through the in-app live chat, or in the WhatsApp group if you are already part of it.

The Spock Team

Yesterday we introduced Seleya Labs, the company behind Spock.

Today we want to explain why we are building a new Spock.

The short version is this: AI work is becoming bigger than a single chat.

Current Spock has already helped people ask questions, work through ideas, use files, and create useful outputs. But the next version of Spock needs a stronger foundation. Not because we want to change the product for the sake of it, and not because chat is going away. Chat will still be central.

The issue is that real work needs more than a blank message box.

When you work with AI, you often need context: the file you uploaded yesterday, the long document you are still working through, the notes from a previous conversation, the spreadsheet you want compared with another file, or the company knowledge that should shape the answer.

That is what the new Spock is being built around.

The new Spock is being built so conversations, files, and context can belong to ongoing work instead of sitting in isolated chats. In the product, the place where related work lives is called a Space.

We will explain Spaces more clearly tomorrow. For today, the important point is simple: the new Spock is being built for work that continues over time, not only for one-off questions.

This matters for individuals, but it matters even more for businesses.

For a business, the long-term direction is that Spock becomes the layer where company knowledge, tools, people, and AI work come together. That does not mean everything arrives at once in the first beta. It means the new Spock is being built on the foundation we need for stronger file work, better context, integrations, approvals, and eventually more durable agents.

Current Spock remains fully usable while we make this transition.

You do not need to do anything today. We are targeting Tuesday, 19 May 2026 for public beta, if the product and support path are ready.

When beta opens, you will be able to try the new Spock from a clear beta button inside current Spock. Current Spock will continue to run while the beta is active.

We are also still finalising the best way to handle existing Spock work inside the new product. We will explain those transition details clearly before users are asked to rely on the new Spock as the default.

The main point for now is simple:

• Spock is not just getting a new interface.
• Spock is being rebuilt around context, files, tools, and ongoing work.
• Current Spock still works.
• You do not need to move anything today.
• More practical details are coming before the beta opens.

If you have questions or need help, you can reach us at support@spock.chat, through the in-app live chat, or in the WhatsApp group if you are already part of it.

Tomorrow we will explain Spaces in more detail: what they are, why they matter, and how they change the way you will use Spock.

The Spock Team

Today we are introducing Seleya Labs, the company behind Spock.

If you already use Spock, the most important thing is simple: nothing changes in your account today, and current Spock remains fully usable.

Spock remains Spock. You can keep using the product as normal.

We are making Seleya public now because Spock is moving into its next chapter. Until now, most people have only seen the product. They have not seen much of the company or the thinking behind it. That needs to change as we prepare to introduce the new Spock beta.

Seleya Labs exists because we believe useful AI should work more closely with the context, tools, knowledge, and infrastructure people and companies already rely on.

Long term, that means helping people and businesses use AI with more control over their own knowledge and workflows, while still keeping the product simple enough to use every day.

Spock is our flagship product and the first expression of that direction.

The new Spock is being built around a stronger foundation for files, context, integrations, and longer-running work. It is a step toward Spock becoming more than a chat window: a workspace where AI can help you work with the knowledge and context that matter to you.

We are not switching everyone over today. We are handling the transition carefully.

Here is what this means right now:

• Current Spock remains fully usable.
• Your account does not change today.
• You do not need to move anything today.
• The new Spock beta is being prepared carefully.
• We are targeting Tuesday, 19 May 2026 for public beta, if the product and support path are ready.
• All transition updates will live on this page.

When public beta opens, existing users will be able to try the new Spock from a clear beta button inside current Spock. Current Spock will remain fully usable while the beta runs.

If you have questions, you can reach us at support@spock.chat, through the in-app live chat, or in the WhatsApp group if you are already part of it.

Tomorrow we will explain why we are building a new Spock.

The Seleya Labs founding team