The planning layer for Windsurf.
The Hamster CLI syncs Briefs, Plans, and team decisions into your repo so Windsurf can work from your team's requirements alongside the code.
Free for 10 briefs a month.
Give Windsurf the requirements before it starts building.
Sessions start without requirements
You open Windsurf with a rough idea. The AI generates code, you course-correct, and the result needs cleanup. Requirements were never in the loop.
Context lives outside the editor
When product decisions stay outside the repo, someone has to supply them to the coding session and may lose detail while summarizing.
No coordination across team sessions
Developers working on the same feature can duplicate changes or create conflicts when their coding sessions have no shared task boundaries.
Hamster brings structure to Windsurf.
Hamster drafts a Brief from your intent and generates a Plan with scoped Tasks. The CLI syncs that work into .hamster/ so Windsurf can read the requirements and acceptance criteria before building.
Requirements before prompts
Hamster briefs define the outcome, scope, and constraints so Windsurf sessions stay on-target from the first prompt.
Session-sized tasks
Hamster decomposes features into tasks that fit a single focused Windsurf session, preventing scope creep and wasted iterations.
Always-on context via the CLI
The CLI keeps the Briefs, Tasks, and Plans in .hamster/ current as your team makes changes, so Windsurf can pick up the latest requirements without manual copying.
How teams use Hamster with Windsurf
Feature implementation
Before
Requirements supplied only in a prompt can leave the scope unclear, requiring more explanation and corrections as the agent builds.
After
The agent reads the Brief and task details from .hamster/, so its work can be reviewed against the requirements your team agreed on.
Team coordination
Before
Developers working in separate coding sessions can duplicate work when they have no shared requirements or task boundaries.
After
Hamster gives the team a shared Brief and scoped Tasks, so each developer can choose work with clear acceptance criteria.
Multi-session work
Before
Resuming a feature requires someone to explain what was completed and which work remains when that context is missing from the repo.
After
The CLI keeps task status and requirements in sync, so the next session can pick up the remaining work from the shared Plan.
Bring your next Brief into Windsurf.
Your coding agent can work from the shared Brief and scoped Tasks, giving you clear acceptance criteria to review its changes against.
The Free plan includes 10 Briefs a month for you and your team.
Related pages
Hamster CLI
Install the CLI, sync briefs and plans into your repo, and give your coding agent full project context.
Hamster for Cursor
Plan outside the editor, build inside it with scoped Cursor sessions.
Hamster for Copilot
Give Copilot structured requirements alongside your code.
Hamster for Developers
Implementation-ready task specs for developers who ship with AI agents.