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 issue tracker 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.
Each team workspace gets a dedicated context store. When you add a Connection, the service's data is synced into that store. The AI searches across all your connected sources when responding, pulling in the most relevant content automatically.
Some connectors use live federated search — the AI queries the service directly at the time you ask a question, so you always get current data. Others sync data into the context store on Connection and can be re-synced at any time. Some services (like Slack) offer interactive features where the AI can respond directly within the tool.
Multi-account support: Many Connections support multiple accounts for the same service. For example, you can connect several Composio integrations (Slack, GitHub, Salesforce, etc.) with different credentials. When you use these Connections in Briefs or chats, you can specify which account to use.
Some Connections go beyond read access. Two-way sync services like Linear and Jira keep Tasks automatically synchronized between Hamster and the external tool, so updates flow both directions without manual updating. Slack's bot lets you interact with Hamster from inside your team's conversations. These bidirectional Connections keep your tools in lockstep.
Your team's Connections are shared. One person sets up the GitHub Connection; everyone in the workspace benefits.
When a Connection's OAuth token expires or credentials become invalid, Hamster notifies you with a Reconnect required badge on the Connection card. This typically happens when:
To reconnect:
If a Connection encounters an error during sync (rate limits, missing permissions, network issues), you'll be notified and can troubleshoot from the Connection card. Many errors auto-resolve once conditions improve; persistent errors may require reconnecting or adjusting the external service's settings.
Click any active Connection card and select Remove. This:
Credentials are encrypted at rest using AES-256-GCM encryption. Access tokens and personal access tokens are never exposed to the browser after initial setup. All Connections request only the minimum permissions required to read data.