Skip to main content
A Space is a shared workspace for a team and Hops. Everything relevant to a project or workflow lives here: conversations, docs, the Space Context document, artifacts, and Hops activity. When your team works in a Space, Hops builds up shared context from it. The next question in that Space already has the background.
A Hops Space showing the sidebar with multiple Spaces, and a chat thread inside the selected Space.

​
How Spaces work

One Space, one shared context. Everything in a Space — decisions, drafts, threads, docs — contributes to the shared context Hops draws from. People and Hops work side by side. Tag @Hops in a thread. If your workspace has installed skills, Hops uses the right skill automatically when the request matches, and shows attribution like Hops · Pipeline watch on the response. Spaces are scoped. Hops working in one Space doesn’t automatically carry that context into another. You control what each Space contains and who can see it.
Set up the Space Context document early. It’s the single fastest way to make Hops sharper in the Space — one brief Hops reads before responding.

​
Space visibility

Every Space is either public or private inside your workspace. You pick when you create it and can change it later.
Private Spaces are hidden from search for people who aren’t invited. Hops scoped to a private Space only draws context from it.

​
Work with Hops in a thread

Every Space has Hops by default. Tag @Hops in a thread and it responds from the Space’s shared context. If a matching skill is installed, Hops uses it automatically and attributes the response like Hops · Pipeline watch.
Replies land in the same thread so the whole team sees the context.

​
Create a Space

Creating a new Space by clicking the + button and naming it.
1

Click the + button

At the bottom of the left sidebar, click + and select Space.
2

Name your Space

Give it a clear, specific name. The name tells your team and Hops what this Space is for.Good examples: Product launch Q3, Acme Corp account, Marketing team.
Your Space is ready. Start a thread, set up the Space Context document, or tag @Hops to get to work.

​
Extend Hops with skills

Every Space has @Hops by default. To give Hops role-specific behavior — a Legal reviewer, a Researcher, an SDR — install a skill rather than adding a separate agent.
Installing a skill so Hops runs a specific playbook in a Space.
1

Open Skills

From the left sidebar, go to Hops Agent → Skills.
2

Install what the Space needs

Pick a skill for yourself, or (as an admin) install it for the whole workspace so every Space’s Hops can use it.
3

Tag Hops in chat

Tag @Hops in the Space. When the request matches an installed skill, Hops uses it and shows attribution on the response.
Keep a small, focused set of skills installed. Fewer, sharper skills give better results than a long overlapping list.
See Hops overview, Skills, and Build a skill for more.

​
When to create a new Space

Create a Space for a distinct project, team, or ongoing workflow:
Keep one Space per topic. Mixing unrelated projects dilutes the context and makes agents less accurate.

​
What’s inside a Space

Chat

Threaded conversations with your team and your agents. Also where pins and meetings live.

Space Context

A standing brief every agent in the Space reads before responding.

Automation

Scheduled tasks that run on their own.

Members

People and agents in the Space, and their roles.
Docs, files, and tables created in a Space also show up in the global Artifacts tabs in the left sidebar.

​
Common Space setups

Not sure how to structure your first few Spaces? Start from a proven pattern.

Marketing

Campaign launches, content repurposing, and brand copywriting in one room.

Sales

Pre-call prep, post-call follow-ups, and clean deal handoffs.

Legal

Contract summaries, NDA prep, and compliance Q&A with a Legal helper agent.
See Teams & Use cases for every team’s playbook.