Learn
Quick start
Create a Space, chat with an Agent, touch files, save a checkpoint, and publish a Work.
This is the shortest useful loop in Cohub. Aim for one clean pass, not perfection.
1. Sign in and open Cohub
Open cohub.run and sign in.
If you already have Spaces, the app returns you to recent work. Otherwise create a new Space.
2. Create a Space
- Create a Space with a clear name.
- Optionally set a public slug later in settings.
- Enter the Space. You land on a new Chat.
A new Space is already a workspace: files, Sandbox, Saves, and Works are available even if empty.
3. Start a Chat
- Pick a model if needed.
- Tell the Agent what you want to build or explore.
- Prefer concrete goals: “scaffold a landing page”, “inspect this repo”, “draft an API”.
Useful first prompts:
Create a minimal static site in this Space and explain the file layout.
Review the workspace, then propose a short plan before editing.
4. Work with files
While the Agent works:
- Open the files tree
- Inspect generated or edited files
- Upload reference assets if needed
- Preview HTML or a running port when available
You do not need to leave Chat to verify progress. Keep the conversation and the workspace side by side.
5. Save a checkpoint
When the Space reaches a meaningful state:
- Create a Save
- Give it a short label or note you will understand later
- Confirm the diff looks right
Save after a working milestone, not after every message.
6. Publish a Work
If the Space has something shareable:
- Open the HTML file, site directory, or live port
- Publish it as a Work
- Choose a Work slug
- Open the public URL
Work targets:
| Target | Use when |
|---|---|
| File | Single HTML page |
| Directory | Static site with index.html and assets |
| Port | Live app running in the Sandbox |
7. Optional next steps
- Invite a collaborator from Space settings
- Bind a Channel if you want Discord / Telegram / Feishu / WeChat entry points
- Use the CLI for the same loop from a terminal
- Mount Mods or skills when you want reusable tooling
Done when
You can answer yes to all four:
- I have a Space
- I have at least one Chat with useful history
- I created a Save I could restore or fork from
- I know how to publish a Work when output is ready