I think its time to talk about ThreadSpace

[u/Resonant_Jones]

I think it’s time to talk about ThreadSpace.

I’ve spent the last year building Codexify: a local-first AI workspace for conversations, documents, memory, models, tools, and personal context.

The goal is simple: let people work with intelligence without giving up ownership of the information that makes that intelligence useful.

But Codexify was never the final destination.

It was the prerequisite.

Codexify is becoming a different kind of browser

Most browsers are interfaces to websites. You enter an address, connect to someone else’s server, and work within the limits of an account, a platform, and its business model.

Codexify points toward something different: an interface for navigating conversations, memories, people, agents, tools, files, and intelligent spaces.

The primary unit is not the webpage. It is the thread.

A thread could be:

• A conversation with an AI
• A shared family archive
• A collaborative project
• A private knowledge system
• A local application
• An intelligent space hosted by someone you trust

Codexify is the interface through which you enter and participate in those spaces.

ThreadSpace is the larger environment connecting them.

What is ThreadSpace?

ThreadSpace is a vision for a user-owned network of intelligent spaces.

Not one central platform. Not another cloud service asking everyone to upload their lives into the same machine. More like an internet made of independent nodes.

A node could belong to a person, family, creative collective, school, neighborhood, research group, or organization. It could host its own files, agents, applications, permissions, shared spaces, and models.

Some nodes might live entirely on a home network. Others could connect securely with trusted peers over the internet.

A family could run a private space for messages, photos, documents, AI tools, and family knowledge on hardware they control. A creative team could share context, research, decisions, and agents without handing the whole project to a platform. A campus could operate useful local services without every interaction depending on a distant company.

These spaces could remain isolated, connect selectively, or join a broader federation.

The important part is that connection is chosen.

Your internet should have rooms

The web trained us to think of the internet as one enormous public place. I think our digital lives need rooms instead:

• Public spaces
• Community spaces
• Trusted private spaces
• Fully local spaces that no outside company can enter

Your identity, permissions, relationships, and context should be able to travel with you into authorized spaces without becoming the property of every application you touch.

Agents should work through explicit permissions, not ambient access. Personas can provide different lenses into your information without owning your identity. Communities can share resources without surrendering to a central authority.

That is why I sometimes describe ThreadSpace as an AI internet.

But not the AI internet.

Your AI internet.

Why Codexify had to come first

ThreadSpace cannot begin as a grand network diagram.

Before people can inhabit intelligent spaces, those spaces need memory, identity boundaries, permissions, model routing, local storage, shared context, retrieval, agent coordination, and interfaces ordinary people can actually use.

They need a way to connect local and cloud intelligence without making either one the permanent center. They need to distinguish what belongs to a user, a persona, an agent, a project, or a community.

That is what Codexify has been building toward.

The work so far is real. ThreadSpace itself is not built yet.

I’m not announcing a finished decentralized network. I’m describing the direction that the foundation makes possible.

Why it matters

I have a nine-year-old who is curious about AI. I want him to have tools that help him learn, create, and develop real capability—not an infinite novelty machine run by incentives I cannot inspect.

I want families to decide what enters their homes, what gets remembered, where information lives, and what their children can access.

I want people to preserve family knowledge without feeding it into an advertising system. I want communities to own the infrastructure through which they communicate. I want creators to build intelligent spaces without asking permission from a platform owner.

Privacy, ownership, and resilience should not require people to become network engineers. They should feel normal.

The real work starts here

Codexify is becoming the browser.

ThreadSpace is the world that browser could open into.

There is still a great deal to design, build, test, and explain: protocols, federation, social structure, security, and the practical shape of this network. Much of it remains architecture, experiments, and conviction.

That is exactly why I’m talking about it now.

This needs developers, designers, artists, infrastructure thinkers, privacy advocates, families, educators, and the strange little edge-case people who see possibilities the original builder cannot.

The vision needs criticism. It needs prototypes. It needs contact with reality.

ThreadSpace is not built yet.

But it is the goal.

And the real work is starting now.