• Pricing
  • Latest
Sign InGet started free
  • Pricing
  • Latest
Home
Product
Studio overview

Plan the work

  • Goals & Initiatives
  • Research Agents
  • Briefs
  • Plans

Deliver together

  • Cloud Agents
  • CLI
  • Collaboration
  • Issue tracker sync

Share knowledge

  • Context Graph
  • Blueprints
  • Skills & Methods
  • Routines
  • Connections
PricingLatest
GuidesDocsResearchCareersAboutThe Hamster Method
Sign InGet Started
October 23, 2026
Studiov1.79.0

Build on Bitbucket from your briefs

Hamster now works with your Bitbucket repos. Plus, the Getting started chat helps new teammates find their first piece of work.

Bitbucket

Talk through your Bitbucket code with Hamster, then turn your briefs into pull requests. Bitbucket joins Jira and Confluence, so Hamster can draw on your code, issues and docs as you plan.

User on the Connections page clicks the Bitbucket Repos tile. A Connect Bitbucket to Hamster dialog lists what Hamster will be able to do, and they click Continue to Bitbucket. Bitbucket's own Atlassian consent screen says Hamster is requesting access to their account, and they click Accept. Back in Hamster, a Select repositories dialog lists a Bitbucket repository as code context; they check it, its main branch shows beside it, and they click Connect repositories. A Bitbucket is Connected dialog explains that plans and specs follow the codebase once it is indexed, and they click Got it. The scene ends with a new Bitbucket card at the top of the team's connections showing one repository with its status moved from Indexing to Indexed, indicating a team can authorize Bitbucket in a few clicks and have Hamster index its code as grounded context, right from the Connections page.

Read the Bitbucket setup guide.

Ask how a feature works today, then talk through the change you have in mind. Hamster answers from your code and points you to related briefs.

User on the home chat, cropped in on the conversation, asks Hamster a pointed code question: how a repository in Bitbucket records a webhook delivery that is retried. Hamster answers from the connected Bitbucket code, citing the source files where each retry is counted and what every attempt overwrites. The view widens to the full chat as the user types a narrow follow-up about whether a retried delivery is signed, and Hamster searches the repository again, its progress line naming what it is looking for, then lands a short answer up front: no, neither the first delivery nor a retry is signed yet, with a link to the planned brief that covers signature verification. The scene ends with that answer and the brief link settled on screen together, indicating Hamster keeps one code conversation going through a precise follow-up, answering from the real source of a Bitbucket repository and pointing to the work already planned.

Learn more about what Hamster indexes from Bitbucket.

Send the brief to Hamster Cloud when you're ready to build. It works through the plan and opens a Bitbucket pull request linked to the brief.

You can also link an existing pull request to a brief and check the change against what you asked for. Once you've signed in with Bitbucket, your comments in Review appear on the pull request under your name.

User on a brief with a linked Bitbucket pull request opens the Review tab, where the pull request's changed files sit beside the brief. They click the comment control on one of the changed files, type a review question to the teammate who will review it, and send it. The comment lands in the review thread on the left and a toast confirms Comment posted to Bitbucket. They click the pull request pill and follow it out to Bitbucket, and the scene ends on the pull request in Bitbucket with the same comment under the user's name, indicating a team can review a Bitbucket pull request beside its brief while every comment still reaches Bitbucket under the reviewer's own name.

Learn more about reviewing Bitbucket pull requests.

Getting started chat

Help teammates new to Hamster find their first piece of work. After accepting your invite, they choose their role in a Getting started chat, and Hamster walks them through the goals, initiatives and briefs your team has underway.

User on the Getting started chat a new teammate lands in after accepting an invite, where Hamster has greeted them by name above a Make Hamster yours card. They pick Developer and click Continue, and the card folds into a one-line summary while Hamster works on a reply. Hamster's first reply then lands with a short note for their role, the team's goals, and its active initiatives and briefs in flight as links with live status dots, and closes by offering to help them pick up a first piece of work. The scene ends on that reply, indicating a new teammate starts from the team's real work in flight, framed for their role.

For a new workspace, share your website or a doc and Hamster builds your Blueprints from it. It'll suggest a first brief or initiative, then draft it when you say yes.

User on the Getting started chat of a brand-new workspace, where Hamster has just greeted them by name above a Make Hamster yours card with Founder already picked. They choose a team size, type their company website and click Continue, and the card folds into a one-line summary. A Building your Blueprints card lands and the side panel opens beside the chat, then the card ticks its rows off one by one and collapses to its finished count while Hamster explains it is building the workspace's blueprints from that website. Hamster reports the blueprints as links and offers to draft a first initiative drawn from them. The user answers with a short yes, Hamster replies that it is drafting it, and the scene ends with the initiative marked ready in the chat, with a link to it and a line on what it covers, indicating a new workspace goes from the company's own website to its first initiative in one conversation.

If you still have setup to finish, you'll find a Getting started chat pinned in your sidebar. Say yes to connecting your code, and Hamster brings up the connection options.

User on their workspace home, where a Getting started chat sits in the sidebar. They open it, and Hamster welcomes them back by name and offers the setup step still open, connecting their code repository. They reply with a short yes, and Hamster answers with a Connect your code card right in the chat, listing what connecting lets Hamster do and a button for each code host: GitHub, GitLab, Cursor Origin and Bitbucket. The scene ends with the card on screen and Hamster's note to pick the repositories to index and that it will follow up once indexing finishes, indicating a workspace that was only partly set up is offered its next step as a card in the same conversation.

Learn how the Getting started chat works.

Improvements

  • You can now click a brief's avatars to see who's involved.
  • You can now choose whether mentions reach you in Hamster, in Slack or by email.
  • Tour now calls out where a pull request strays from its brief.
  • You can now read and reply to a pull request's general discussion in Review.
  • File names now stay pinned while you scroll through a long diff.
  • Search and your private chat with Hamster now sit at the top of your sidebar.

Bug Fixes

  • Teammates you invite can now join your team after signing up through Claude or Cursor.
  • Text you delete and items you archive no longer turn up in Hamster's answers.
  • Shared documents now reconnect right away if the connection drops.
  • If an update interrupts a reply, Hamster now picks up where it left off.
  • Replies now fail less often when a model is busy or slow.
  • Hamster no longer stops after a quick first reply without doing the work.
  • Long replies from Hamster no longer get cut off.
  • Cursor and OpenAI deliveries now finish with a link to the pull request.
  • Hamster now posts your comment only once when you approve or request changes.
← Studio 1.75.0
Studio 1.83.0 →

Turn your team's goals into delivered work.

© 2026 Wheel Go Fast, Inc. All Rights Reserved.

GitHubEmail support
Product
  • Studio overview
  • Goals & Initiatives
  • Research Agents
  • Briefs
  • Plans
  • Cloud Agents
  • Plugin
  • Collaboration
  • Issue tracker sync
  • Context Graph
  • Blueprints
  • Skills & Methods
  • Routines
  • Connections
  • Pricing
  • Method
For
  • Developers
  • Founders
  • Product managers
  • Designers
  • Agents
Works with
  • Claude Code
  • Cursor
  • Codex
  • Copilot
  • Gemini CLI
  • Grok
  • Grok Bot
Resources
  • Guides
  • Research
  • Methods
  • Skills
  • Comparisons
  • Docs
  • Latest
  • Release media
  • Changelog
  • FAQ
  • About
  • Careers
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Trust Center

© 2026 Wheel Go Fast, Inc. All Rights Reserved.

GitHubEmail support
Sign In
Get Started

Turn your team's goals into delivered work.

© 2026 Wheel Go Fast, Inc. All Rights Reserved.

GitHubEmail support
Product
  • Studio overview
  • Goals & Initiatives
  • Research Agents
  • Briefs
  • Plans
  • Cloud Agents
  • Plugin
  • Collaboration
  • Issue tracker sync
  • Context Graph
  • Blueprints
  • Skills & Methods
  • Routines
  • Connections
  • Pricing
  • Method
For
  • Developers
  • Founders
  • Product managers
  • Designers
  • Agents
Works with
  • Claude Code
  • Cursor
  • Codex
  • Copilot
  • Gemini CLI
  • Grok
  • Grok Bot
Resources
  • Guides
  • Research
  • Methods
  • Skills
  • Comparisons
  • Docs
  • Latest
  • Release media
  • Changelog
  • FAQ
  • About
  • Careers
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Trust Center

© 2026 Wheel Go Fast, Inc. All Rights Reserved.

GitHubEmail support
Sign InGet started free
Sign In
Get started free