Give the AI access to the tools your team already uses, so it understands your project without being told every time.
Connections are integrations between Hamster Studio and the external services your team relies on. Setting up a connection once gives every member of your workspace access to that data source — making the AI more accurate and contextually aware without requiring manual input each time.

Connections are integrations between Hamster Studio and the external services your team relies on — code repositories, issue trackers, communication tools, and documentation platforms. When you connect a service, Hamster can read data from it and use that data as context when you interact with the AI.
Without connections, the AI only knows what you tell it in the current conversation. With connections, it has access to your actual project: the issues in your backlog, the messages in relevant Slack channels, the pages in your Notion workspace, the code in your repository.
Better answers. When you ask "what are we building in this sprint?" the AI can check your Linear workspace rather than asking you to paste in the tickets.
Richer briefs. When you generate a brief, the AI can reference real issues, real code, and real documentation rather than working from scratch.
Less manual context. You stop spending time re-explaining your project to the AI at the start of every conversation.
When you add a connection, the service's data becomes available to the AI. The AI searches across all your connected sources when responding, pulling in the most relevant content automatically.
Some connections (Slack, Jira, Google Drive) search the service in real time when the AI needs context, so you always get current data. Others (GitHub, Linear, Notion) sync data on connection and can be re-synced at any time.
Your team's connections are shared. One person sets up the GitHub connection; everyone in the workspace benefits.
Click any active connection card and select Remove. The connection is deleted from both Hamster and the connected service. The AI will no longer have access to data from that source.
Credentials are encrypted at rest and never exposed to the browser after initial setup. All connections request only the minimum permissions required to read data.