Skip to main content
Hops is a multiplayer AI workspace built around one agent — Hops — extended by installable, shareable skills. Your team and Hops share the same memory, context, and workspace.Instead of everyone using a separate private chatbot and re-explaining the same context, Hops gives the whole team one shared context for getting work done together.
Most AI tools are single-player: one person, one private chat, one isolated context window. Every session starts from zero.Hops is multiplayer. Hops knows what the team knows. It reads from threads, docs, and connected tools your whole team has built up. Skills package repeatable playbooks so everyone’s Hops runs them the same way. No one re-explains the brief.
Hops is one AI agent that lives in your workspace and every Space. Tag @Hops in a thread and it responds from the Space’s shared context. Extend Hops with skills — installable, shareable capabilities that give it role-specific behavior for marketing, sales, finance, support, or anything else.See Hops overview and Skills.
A Space is the shared workspace where your team and Hops work together. It contains threads, docs, the Space Context document, and artifacts. Everything relevant to a project or workflow.Everything that happens in a Space builds shared context Hops draws from. See What is a Space?.
Hops can read from 2,000+ tools, powered by the Pipedream integration catalog. Featured integrations include Amplitude, Gmail, Google Calendar, Google Drive & Docs, HubSpot, Jira, Linear, Miro, Notion, Sentry, and Stripe.You connect tools from Settings, then Connections. See Connections for details.
Hops reads from connected tools with the same permissions as the account you authorize. It doesn’t get elevated access. Your data is not used to train AI models.You can review and revoke any connection at any time from Settings, then Connections.
By default, any action that affects something outside Hops (sending an email, updating a CRM record, modifying a document) requires your approval before it happens.Skills that perform outbound actions should pause for approval by default — you can configure this when you build the skill.
Hops accesses only what you explicitly connect and authorize. Invite-only Spaces keep sensitive work from the broader workspace. You can scope each connection to limit what Hops can read.For particularly sensitive workflows (HR, Legal, Finance), we recommend scoping tool access tightly.
Yes. Skills let you package instructions, tone, and connections into a reusable, shareable capability for Hops. Build one for any workflow your team needs.See Build a skill to get started.
Connections are managed at the workspace level from Settings → Connections and are shareable across your team. They power @Hops for everyone in the workspace and any installed skills that need them.
Still have questions? Reach out at support@hops.ai.