• 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 2, 2026
Studiov1.72.0

Plan and ship on Cursor Origin

Hamster now works with your Cursor Origin repos like it does with GitHub, all the way through shipping with Hamster Cloud and review.

Cursor Origin

You can now connect Cursor Origin, Cursor's git host, by installing the Hamster Origin App and picking your repositories.

User on the Connections page clicks the Cursor Origin tile. A Connect Cursor Origin to Hamster dialog explains that Hamster will read repositories, commits, and pull requests from the Origin installation, and they click Install Origin App. On Cursor's own install screen, they choose to select repositories for their organization instead of granting all of them, open the dropdown, check a single repository, and install the Hamster app. Back in Hamster, a Select repositories dialog lists that repository as code context; they check it and click Connect repositories. A new Cursor Origin card drops into the team's connections showing one repository, and its status badge reads Indexing, then Embedding, then Indexed in real time. The scene ends with the Cursor Origin card Indexed beside the GitHub and GitLab cards, indicating a team can authorize Cursor Origin in a few clicks and watch Hamster index its code as grounded code context, right from the Connections page.

Read the Cursor Origin setup guide.

Hamster's answers now tie your Origin code to your briefs and plans. Ask what a function really keeps, and Hamster shows what gets silently dropped and which brief already plans the fix.

User on the home chat, cropped in on the conversation, asks Hamster a quick orientation question: where a repository in Cursor Origin starts. Hamster answers from the connected Cursor Origin code with the entry file, the module where the server is actually wired up, and the command to run it. The user then sends a narrow follow-up about what one function really keeps, and the view widens to the full chat as Hamster reads that function in the repository, its progress showing above the composer, then lands a short answer up front, the few fields the stored record keeps, the details it silently drops, 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 Cursor Origin.

Learn more about what Hamster indexes from Cursor Origin.

One message in chat sends a brief to Hamster Cloud, which works through its plan in your Origin repo.

When it's done, Hamster tells you in the thread, and the draft pull request is waiting on Origin, linked to the brief.

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 Cursor Origin, and Hamster confirms it is sending the brief there through Hamster Cloud 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 or command it runs, then the plan reaches 4 of 4 tasks completed, the brief flips to Delivered and a draft pull request chip settles in the header. The user clicks the chip, which opens a popover naming the draft pull request and its repository, and follows its external link. The scene ends on the draft pull request in Cursor Origin with the brief's tasks in its description, indicating that one chat message is enough to turn a brief into a reviewable pull request in Cursor Origin on Hamster Cloud.

Learn more about Cursor Origin pull requests.

Improvements

  • Hamster Cloud deliveries now run on Opus 5.5, Sonnet 5.5, GPT 6.1 Sol, and GPT 6 Luna.
  • You can now drag briefs into order on an initiative.
  • Finished deliveries now archive themselves.
  • Hamster now starts a review thread when you open a brief's Review tab.
  • You can now link a pull request to a brief from any chat.
  • You can now right-click any ⌘K result to open it in a new tab, copy its link, or pin it.
  • Hamster can now find a teammate's notes, blueprints, or initiatives when you ask by name.
  • Hamster Cloud pull requests now show where the work departed from the plan.
  • Failed deliveries now show the model provider's actual error.

Bug Fixes

  • People who can't manage connections no longer see GitHub setup prompts.
  • Losing access to your MCP connection's team no longer locks you out.
  • Retrying a failed delivery no longer fails before the agent starts.
  • Deliver on a delivery that ran out of retries now resumes from its last checkpoint.
  • Brief pages no longer crash when browser storage is full.
  • Finished delivery tasks no longer get stuck on In progress.
  • Hamster Cloud commits to GitHub now show Hamster's GitHub App as the author.
  • Jumping to a review comment now lands on the first click.
← Studio 1.70.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