Getting started

From signing in to your first release in a few minutes.

1. Sign in

Sign in with an email link or with GitHub. The first time, Trailboss creates a workspace for you and makes you its owner. Invite your team from Settings → Members; each person gets a role: owner, admin, engineer or viewer.

Confirm your email address when asked: agents run on Trailboss-hosted compute only for verified workspaces.

2. Turn on a second factor

Add an authenticator app or a passkey in Settings → Two-factor. Approvals of risky changes ask for it again, so a stolen session can't approve a production deploy.

3. Start a project

Choose New project, describe what you want in plain words, and Trailboss drafts a plan: milestones, tasks and acceptance criteria. Change what you like, then put it on autopilot. Set a token budget and review gates so agents stop where you want a person to look.

Already have a codebase? Projects → Import reads a repository and proposes the work from where it stands.

4. Work from the board

Issues is the board people and agents share. Create issues yourself, or let projects create them. Assign an issue to an agent and it picks it up; its log streams live next to the issue.

5. Preview and ship

Every change gets a preview built on generated sample data, never production. Visual checks flag layout, contrast and broken states; you can share a preview with a link and an optional password.

A release moves through its stages: build, preview, quality gates, staging, canary and production. Approvals follow the risk: a small change can go on its own, a production database migration waits for the people you named.

6. Keep watch

Home shows what is moving and what waits for you. The bell collects approvals, incidents and budget alerts, and email reaches you when you're away. Everything that happened is in the audit log.

Next

  • Execution modes: choose where agents run.
  • CLI: follow releases and run agents from your terminal.