people + agents welcome

Your own space to create, play, and build with people and agents.

A living Space where people and agents work in one context. Start on the web, or connect a local folder with the CLI. Make in any medium, save Checkpoints, and share as Live Works.

$ cohub sandbox up ./my-project

checkpoint saved
CLI · local ↔ space
Make in any medium
Text Images Video Music Code & apps
How it works

Start a Space. Build in it. Publish live.

Open one on the web or from a local folder with the CLI. Work together, save a Checkpoint, then publish a Live Work that keeps running on Cohub.

01

Start a Space

Open one on the web, or run cohub sandbox up on a local folder so that directory becomes the Space sandbox.

02

Build & Save

People and agents share one context — chats, files, previews. Save a Checkpoint when something is worth keeping.

03

Publish a Live Work

Share a public app that exposes your Space — not a static export. Visitors can act back on the Space after they authorize.

What makes it different

Share live. Reuse context.

Publish an app that exposes your Space, or let the agent pull context in with @space — other Spaces as context, not a hunt for another agent. Useful once you are building.

Live Work

A public app that exposes your Space.

Publish a file, site, or port as a live app on Cohub. You choose which Space capabilities it can use, and what visitors may allow. After they authorize, actions can prompt, generate, or read files back in the original Space.

Reuse

The agent fetches context.

With @space, the agent pulls another Space into this turn. You stay put — you are not shopping for a different agent. Context comes here. Fork is heavier: a new Space from a Checkpoint, fully loaded and yours to change.

Inside a Space

Everything happens in a Space.

Chats, files, previews, scheduled prompts, and published Works — people and agents, one place.

01

Fun to start

Open a Space and play with ideas, prompts, files, and agents. No setup — just start typing and watch things take shape.

draw a tiny robot watering a plant
02

Build together

People and agents share one context. Same chat, files, and tool calls — co-create, save a Checkpoint, keep the thread.

AMC
you
agent✎ edit settings.tsx
mia
agent
03

Open everywhere

Same Space from the web, CLI, API, or a schedule. Link a local folder with cohub sandbox up and work from your machine.

C
Web API
$ cohub sandbox up ./app
04

Publish Live Works

Publish a file, site, or running port as a public app that exposes your Space. After a visitor authorizes, it can still prompt or generate back in the Space.

cohub.run/you/space/w/mini-game
viewer authorized session.prompt
live work
05

Never start blank

Fork a Checkpoint into a new Space, or use @space so the agent pulls other context in. You stay in one session — not hopping between agents.

@space light
attach @northlands to this turn
vs
Fork heavy
The mental model

A few ideas, used together.

You work in Spaces, save Checkpoints, and share Live Works. @space lets the agent reach for other context; Fork opens a new Space when you need a branch.

Space

Where people and agents work together — chats, files, previews, and experiments in one place.

Checkpoint

A saved snapshot of a Space. Share it, fork from it, or come back to it later.

@space

The agent pulls another Space in as context for this turn. You stay put — not a hunt for a different agent.

Fork

Start a new Space from a Checkpoint, with its files and state already loaded.

Live Work

A public app from a file, site, or port that exposes Space capabilities. Visitors can authorize actions back to the Space.

Agent

Works inside the Space with you — tools, files, and media generation.

Start in seconds. Stay for the context.

One Space to play, build, and share — on the web or from a local folder via CLI.