Getting started
Last updated
Getworkers keeps your AI work in tickets, with a history of what happened and evidence you can review. You run Claude Code or Codex yourself; Getworkers does not start a session for you.
Access the private beta
Ask to join the beta. The app currently has one workspace owner. Only that owner's account can sign in; requesting a beta invitation does not create an app account.
Use the sign-in page with the owner's email address. GitHub is offered when configured. An email link works once and expires after 24 hours. Every valid address sees the same “Check your email” screen; that does not confirm access.
Set up your first project
- Open Projects and add a brand: a way to group related projects.
- Add a project with a unique key prefix, such as SKY. A project playbook is created with it, even if you leave it empty.
- Write a ticket with an objective, acceptance criteria and a required outcome. New tickets start in Backlog.
- Move the ticket to Ready when its readiness checks pass and its dependencies are resolved.
- Create a worker, grant it access to the project, then connect Claude Code or Codex.
- Ask the session to pick up the ticket. Follow progress on the ticket page and answer requests in the Inbox.
- Review the submitted evidence. Only you can mark the result accepted.
Workers claim work exclusively. A waiting or stale run still owns its ticket until resumed or ended. Creating a Ready ticket alone never launches a worker.
What to learn next
Start with writing good tickets, then worker tokens and security. Plans and FAQ separates today's product from planned features.