The context layer for Gemini CLI.
The Hamster CLI syncs Briefs, Plans, and team decisions into your repo so Gemini CLI can work from your team's requirements alongside the code.
Free for 10 briefs a month.
Bring product context into your Gemini CLI session.
Every prompt starts from scratch
Gemini CLI has no memory of what your team decided yesterday. You re-explain requirements, constraints, and context every session.
Product context lives outside the terminal
Requirements are in docs, tickets, and Slack threads. By the time you type a Gemini prompt, critical context has been lost or simplified.
No traceability from decision to code
Code generated from a standalone prompt can be difficult to trace back to the product decision that led to the change.
Hamster gives Gemini CLI the full picture.
Hamster drafts a Brief from your intent and generates a Plan with scoped Tasks. The CLI syncs that work into .hamster/ so Gemini CLI can read the requirements and acceptance criteria before building.
Structured briefs for speed
Hamster Briefs give Gemini CLI the requirements, constraints, and acceptance criteria behind the requested change.
Scoped tasks for focused sessions
Hamster decomposes features into well-bounded tasks. Each Gemini session works on a single scoped unit with clear outcomes, reducing hallucinated scope.
Always-on context via the CLI
The CLI keeps the Briefs, Tasks, and Plans in .hamster/ current as your team makes changes, so Gemini CLI can pick up the latest requirements without manual copying.
How teams use Hamster with Gemini CLI
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.
Multi-model workflows
Before
Switching coding tools requires you to explain the same feature again when each tool receives its own separate prompt.
After
Both agents can read the same .hamster/ files, so you can choose a model for each Task while keeping the Brief with the repo.
Parallel team execution
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 Gemini CLI.
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 Codex
Spec-driven async tasks that Codex executes into review-ready PRs.
Hamster for Developers
Implementation-ready task specs for developers who ship with AI agents.