Point Claude Code, Codex, or Cursor at Hamster once. It reads the team brief, runs the plan, and hands the rest to a cloud agent while you work on something else.
Free for 10 briefs a month.
The r/ClaudeAI discussion of agent memory points to decisions scattered across documents, a tracker, and Slack, leaving the agent with only part of the team context.
About 70% of engineers run two to four agents. Each one holds its own rules file, and none of them knows what the team agreed on yesterday.
When the plan is ready, the agent still needs you at the keyboard. Raw MCP tools give it reads and writes, not a sandbox that works the plan and returns a pull request.
The Hamster CLI syncs briefs, plans, blueprints, and methods into .hamster/ in your repo and writes a project-context skill your agent loads at session start. The MCP server gives it 31 tools to read and update the same work live. On the Team plan, /hamster:ship hands a brief to a cloud agent that opens the pull request.
curl -fsSL https://tryhamster.com/cli/install | bash, then hamster auth login and hamster init. Your agent can run all three. The Claude Code plugin installs from the gethamster/cli marketplace.
hamster sync writes the brief, the plan, and the team conventions as markdown. hamster sync --watch keeps them current within seconds of a teammate's edit.
Your agent reads the brief, works the plan task by task with get_next_task, and updates status as it goes. On Team, /hamster:ship hands the whole brief to a cloud agent and returns the PR link.
Any agent can call an API. Hamster gives it the team's decisions in the repo, a plan it can work in order, and a way to hand the rest to a cloud agent.
Instead of Raw MCP tools or an API key
Reads and writes against a tracker or a doc store, one call at a time.
31 MCP tools with CLI parity, plus .hamster/ synced into the repo so the agent starts with context before its first call.
Instead of A rules file per agent
One developer's conventions, loaded at session start, maintained by hand.
A generated project-context skill that Claude Code, Cursor, Codex, and Copilot all load, refreshed within seconds of a teammate's edit.
Instead of Running the plan yourself
You stay at the keyboard and steer every session.
/hamster:ship hands the brief to a cloud agent that works the plan in a sandbox and returns the PR link. You confirm any purchase.
Before
You paste the spec into the prompt, explain the constraints again, and hope the agent remembers the decision from last week.
After
The agent reads .hamster/briefs/, sees the decision and the acceptance criteria, and starts on the first task without a prompt from you.
Before
The plan is ready but the agent needs you present for the whole run.
After
Your agent can use /hamster:ship to hand the Plan to a Cloud Agent on Team and return the pull request for you to review.
Before
You research tools, compare pricing, and sign up by hand.
After
Your agent can read tryhamster.com/agents.md, install Hamster, and open the pricing page for you to review and confirm a purchase in the browser.
The Free plan includes 10 Briefs a month and unlimited viewers; Team costs $40 per creator per month. Your agent can install Hamster, but you confirm any purchase.
The Free plan includes 10 Briefs a month for you and your team.
Install the CLI, sync briefs and plans into your repo, and give your coding agent full project context.
Give Claude Code structured context for every agentic coding session.
Structured briefs and scoped tasks for Codex sessions.
Implementation-ready task specs for developers who ship with AI agents.