The planning layer for Aider.
The Hamster CLI syncs Briefs, Plans, and team decisions into your repo so Aider can work from your team's requirements alongside the code.
Free for 10 briefs a month.
Aider needs the requirements behind the conversation.
Chat-driven development lacks structure
An Aider conversation can drift from the team’s decisions when the session has no shared requirements to refer to.
Context is limited to the current session
Aider sees the files you add to the chat. It does not see the product brief, the team constraints, or what other sessions have completed.
Features need upfront decomposition
Handing Aider a full feature in one chat produces sprawling changes. Breaking work into focused chunks falls on you.
Hamster gives Aider structured context.
Hamster drafts a Brief from your intent and generates a Plan with scoped Tasks. The CLI syncs that work into .hamster/ so Aider can read the requirements and acceptance criteria before building.
Briefs as repo-local context
The Hamster CLI syncs briefs into .hamster/ as markdown. Add them to your Aider session for structured requirements alongside your code.
Task-scoped sessions
Hamster decomposes features into well-bounded tasks. Each Aider session focuses on one task with clear acceptance criteria.
Always-on context via the CLI
The CLI keeps the Briefs, Tasks, and Plans in .hamster/ current as your team makes changes, so Aider can pick up the latest requirements without manual copying.
How teams use Hamster with Aider
Structured pair programming
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.
Multi-session features
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.
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.
Bring your next Brief into Aider.
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 Claude Code
Give Claude Code structured context for every agentic coding session.
Hamster for Cline
Structured task specs for Cline autonomous sessions.
Hamster for Developers
Implementation-ready task specs for developers who ship with AI agents.