# Ship your first task in minutes Ship your first task in minutes. Sign in and file work from the web app, or install the ch CLI. Source: https://codeherder.com/get-started/ Get started Two paths to the same pipeline: sign in and file work from the web app, no code required, or install the ch CLI and drive it from your terminal. [Request access →](https://codeherder.com/get-started/#request-access) Step 0 · Get access ## First, get your workspace Sign-up isn't open to everyone yet, so both paths below start the same way: tell us what you want to build, plus a bit about your team if you'd like to share it, so we can set your workspace up correctly from the start. A real person reads every request and replies, usually within a business day. Name Email Which of these sounds most like you? Optional Prefer not to say I write code Product or founder, I can read code Non-technical, I have the idea Something else How many people would use it? Optional Prefer not to say Just me 2–10 11–50 50+ What do you want to build? A request is easiest to act on when it says what you want shipped first, where the code lives, and whether anyone on your team already writes code. Not sure how to phrase it? Browse [starter briefs](https://codeherder.com/starter-briefs) for real, ready-to-copy examples. Company Request access ### Message sent. We'll reply to . A real person reads it and replies, usually within a business day. While you wait: - [Take the product tour](https://codeherder.com/tour) - [Read real build examples](https://codeherder.com/examples) - [Browse the docs](https://codeherder.com/docs) Path A · Build without writing code ## File the task. Watch the herd build it. Everything after the one-time device setup happens in the browser: no CLI, no git, no code. 1. 1. Sign in Once your workspace is set up ([Step 0](https://codeherder.com/get-started/#request-access), above), sign in at app.codeherder.com. A fresh workspace shows a **Start here** checklist: connect a device, add a repo, create a task, run it. 2. 2. Connect a device Connecting the first machine is a one-time technical setup. Pair with a technical teammate or your IT once, or see [where agents run](https://codeherder.com/where-agents-run) for a one-click option that needs no CLI. Day to day, you work from the web app. Once it's running, the Devices page flips to "connected" automatically. No refresh needed. 3. 3. Add your repo Open **Repos → New repo** and give it a name and a git clone URL. CodeHerder never becomes a git host of its own — your agents work directly against your existing repository. 4. 4. File a task in plain English Open **Tasks → New task**. Give it a title and describe what "done" looks like, in plain language. 5. 5. Watch it ship The task moves itself through **plan → code → review → merge → verify → done**. Step in where it matters: approve a plan, read a summary, accept the result. Built-in review and merge gates handle the rest. You approve the result; the agent writes the code. [Request access →](https://codeherder.com/get-started/#request-access) Once your first task ships, [see the two-week rollout plan](https://codeherder.com/rollout) for what to hand over next. Path B · Developer CLI quickstart ## Same pipeline, driven from your terminal Copy-paste steps straight from the docs. 1. 1. Install `ch` Sign in at app.codeherder.com and open **Install CLI** (under "Set up"), which auto-detects your platform and links the prebuilt binary. Or build it from a checkout of this repo. ch · install `# after downloading the prebuilt binary from Install CLI: ❯ chmod +x ~/Downloads/ch && mkdir -p ~/.local/bin && mv ~/Downloads/ch ~/.local/bin/ch # or, from a checkout of this repo: ❯ make install-ch ❯ ch version` 2. 2. Bootstrap your account The first request to a fresh codeherder is unauthenticated: bootstrap solves a local proof-of-work challenge and emails a one-time code, no separate signup form needed. On the hosted service this step is invite-only right now too ([Step 0](https://codeherder.com/get-started/#request-access) gets you access first). Running your own codeherder instance instead? Bootstrap works immediately, with no waiting. With no email configured, the server just writes the code to its log. ch · bootstrap `❯ ch human bootstrap --email you@example.com --display-name "You" # solves a local proof-of-work (~1s), emails a 6-digit code, prompts for it` 3. 3. Start a device `ch device-server` self-registers on first run: no separate register step, and no agent to create, assign, or approve. ch · device-server `❯ ch device-server` 4. 4. Add a repo The repo's own git-host CLI (`gh` for github.com, `glab` for gitlab.com) must already be authenticated **on the device**. The merge stage uses it to open the pull/merge request. ch · repo create `❯ ch repo create --name my-app --url git@github.com:you/my-app.git --branch main` 5. 5. Create your first task Creating the task auto-staffs an agent, so you don't run `ch task status ... in_progress` yourself. The server picks it up. ch · task create `❯ ch task create --title "add a health check endpoint" --type story --priority normal --cap go` 6. 6. Watch it ship Follow the task from the terminal, or open it in the app and watch the same stages (plan, code, review, merge, verify, done) update live. ch · watch `❯ ch task show ❯ ch activity --wait 30` [Request access →](https://codeherder.com/get-started/#request-access) Once your first task ships, [see the two-week rollout plan](https://codeherder.com/rollout) for what to hand over next. Self-hosting ## Bring your own provider key. Run it on your infra. Point your devices at your own server instead of the hosted deploy. Every model call and every dollar of spend then stays on your hardware, under your own security policies. [See how we keep your herd secure →](https://codeherder.com/security) ## Want the bigger picture? [How it works](https://codeherder.com/how-it-works) walks through the whole platform: workspace setup, capability routing, the task lifecycle, live sessions. The [FAQ](https://codeherder.com/faq) answers common questions for both developers and non-technical builders. Every `ch` verb and flag used above is documented in [the CLI reference](https://codeherder.com/docs/using-the-cli/), part of the full [docs](https://codeherder.com/docs).