• 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 16, 2026
Studiov1.75.0

Ship with OpenAI's cloud agents

Hand off a brief to OpenAI, follow the work in Hamster, and get the code back for review. Hamster now reads and ships to your GitLab projects, too.

OpenAI Agents

Send your next brief to OpenAI's cloud agents. The finished work comes back as a pull request on GitHub.

User on the Connections page clicks the OpenAI Agents tile, picks their team in the Connect OpenAI Agents dialog and pastes an OpenAI Platform API key into the masked API Key field in one paste. They click Connect OpenAI Agents, which reads Connecting while Hamster checks the key with OpenAI, and a connected OpenAI Agents card lands with a Team badge. On a brief, cropped in on the header, they open the Deliver menu and pick OpenAI Agents, the last option under Install Hamster, Hamster Cloud and Cursor Cloud. Cropped in on the brief's delivery thread, a staged delivery finishes step by step: the last task status update, the git push, Branch pushed, then Draft pull request opened with a link to the pull request. The user clicks that link. The scene ends on the draft pull request in GitHub with the brief's tasks in its description, indicating a team connects its own OpenAI key once and any brief can then ship through OpenAI Agents to a draft pull request on GitHub.

You can steer the agents with a message in the delivery thread while they work.

Connect OpenAI Agents to start delivering.

GitLab

Get answers from your GitLab code and let Hamster build from your briefs, just like you can with GitHub and Cursor Origin.

User on the Connections page, where the team's GitHub code connection already shows Indexed, clicks the GitLab Repos tile. A Connect GitLab to Hamster dialog lists what Hamster will be able to do and notes that GitLab will ask them to sign in, and they click Continue to GitLab. GitLab's own consent screen on gitlab.com says Hamster is requesting access to their account, and they click Authorize Hamster. Back in Hamster, a Select repositories dialog lists a single GitLab repository as code context; they check it and click Connect repositories. A GitLab is Connected popup says plans and specs will be faithful to the codebase once the repo is indexed, and they click Got it. The scene ends with a new GitLab card beside the GitHub card showing one repository, its status badge reading Indexing, then Indexed, indicating a team can authorize GitLab in a few clicks and have Hamster index its code as grounded code context, right from the Connections page.

Read the GitLab setup guide.

Talk through the change you're planning. Hamster can answer from your GitLab code and point you to related briefs.

User on the home chat, cropped in on the conversation, asks Hamster a pointed code question: what one function keeps when a delivery fails in a repository in GitLab. Hamster answers from the connected GitLab code with what the function keeps, what it overwrites, and what it drops entirely. The user then sends a narrow follow-up about whether the next attempt wipes the error message too, and the view widens to the full chat as Hamster checks what a retry does to the stored record, its progress showing above the composer, then lands a short answer up front, the steps of a retry that clear the message, a one-line stopgap, and the planned work in a brief that closes the gap. The scene ends with the follow-up answer settled on screen, indicating Hamster keeps one code conversation going through a precise follow-up, answering both questions from the real source of a repository in GitLab.

Learn more about GitLab code context.

Ask Hamster in your brief's chat to deliver it, and Hamster Cloud works through the plan in your GitLab project.

When it's done, you'll hear back in the same thread, with the merge request ready for your review.

User on the Brief tab of a brief in Shipping, with the team's chat open beside it. They send an @mention asking Hamster to deliver the brief to the team's repo in GitLab, and Hamster confirms it is kicking off delivery as a Delivering brief step appears, the header Deliver button starts spinning and the chat switches to the delivery thread. In the delivery thread the agent's work lands step by step, each short status line followed by the file edit it makes, then the plan reaches 4 of 4 tasks completed, the brief flips to Delivered and a merge request chip settles in the header. The user clicks the chip, which opens a popover naming the open merge request and its repository, and follows its external link. The scene ends on the merge request in GitLab with the brief's tasks in its description, indicating that one chat message is enough to turn a brief into a reviewable merge request in GitLab on Hamster Cloud.

Look it over right in Hamster. Once you've signed in with GitLab, your comments and approvals show up on the merge request under your name.

Learn more about GitLab merge requests.

Improvements

  • Briefs and documents created from chat now draw on the recent conversation.
  • Fullscreen chat now lists the work your conversation started.
  • You can now remove a GitHub or GitLab connection in Hamster.
  • Tour in Review now opens much faster.
  • Comments in Review now notify the brief's owner and anyone you @mention.
  • Long chats now open quickly at your latest messages.
  • You can now delete your Hamster account.

Bug Fixes

  • Hamster's replies and your accepted edits no longer go missing after a connection drop.
  • Delivery no longer picks another repository because a word in your brief matches its name.
  • GitHub and your other tools now connect without false errors or install loops.
  • Stalled plans and deliveries now recover or let you retry.
  • Very large repositories sync again.
  • Code searches in chat now time out far less often.
  • Hamster in Slack now retries replies after short outages.
  • Skipping a question card no longer cancels Hamster's work.
  • @mentions now reach the person you picked when teammates share a name.
← Studio 1.72.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
Sign InGet started free
Sign In
Get started free

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