Getting started
From signing up to your first reviewed task: one workspace, Claude Code or another coding agent, and one approved plan. Free covers all of it.
1. Sign up
Start free from the header. Onboarding creates your first workspace. Plans are on pricing if you want more AI credits or a team later.
2. Create a token
Open Settings → Tokens and create one named after your agent, for example Claude Code. The name is how the agent shows up on tasks and on Now.
3. Connect your agent
In Claude Code, install the plugin. It adds Beck’s MCP server and two hooks: one resumes from Beck when a session starts or compacts, and one asks the agent to record the plan when you approve it. It asks for the token on install.
/plugin marketplace add beckhq/beck-plugin /plugin install beck@beck
Cursor, Codex, Windsurf and other MCP hosts run the same server. Connect an agent has the config for each.
4. Bind the repo
In your repo, ask the agent to use Beck. The first time, it checks whether the repo is bound to a workspace and, if not, binds it to the one you name. After that it finds the workspace on its own.
5. Plan, then approve
Ask for the next piece of work, in plan mode if your agent has one. When you approve a plan with three or more tasks, the agent calls record_plan. In Beck you’ll see the plan as a document under plans/, and an epic in the backlog with its tasks and acceptance criteria.
6. Follow the run
Open Now. The run shows the task the agent is on, its test results as it checks in, anything it’s waiting on you for, and its latest notes. If it stops calling in for 30 minutes, the run says Quiet.
7. Answer its questions
When a choice is yours, the agent asks it with the default it’s going with and keeps working. The question waits in Waiting on you, which works on a phone. Keep the default or answer in a sentence; the agent hears it on its next call.
8. Review
Finished tasks land in Ready for Review with the agent’s note on what it tried and what passed. Accept a task, or reject it with a reason. Next session, the agent calls resume and picks up where the last one stopped. The task loop covers each call.
Do
One workspace per repo. Approve the plan in your agent and let it record it.
Don’t
Don't retype the agent's plan as tickets, or run Plan it over it. The breakdown you approved is the one that counts.
Questions
Do I need a team to start?
No. Free is personal. Invite seats when you want your team in the same workspaces.
Do I write a PRD first?
No. Your agent's plan is enough. Write documents when you want specs or research next to the plans; teammates who are not coding can use Plan it on them.
What if my job is small?
Jobs under three tasks skip Beck unless you ask. Beck earns its keep when work spans sessions.