# For developers

A developer's path through EasyCode: sessions on your own harness, pick-up and hand-off, the kit, repo knowledge and workflows.

## What does EasyCode do for a developer?

You keep your harness. EasyCode drives Claude Code, Codex, Cursor, Copilot, Gemini, OpenCode or pi on your own login,
and gives every session the same things: your org's library, the repo's knowledge and the task you are working on. A
session can move to a teammate's machine or to another harness without losing its history. Work moves on the
**Board**, through your org's **Workflows**, to a pull request your team reviews.

## Your path

Follow these pages in order. Each line says why it matters to you.

### Get running

1. [Quickstart](/setup/quickstart): join your org and run your first session in a few minutes.
2. [Desktop app](/setup/desktop-app): it holds the runner your sessions run on, and the built-in browser.
3. [Harnesses on your own login](/setup/harnesses): install and sign in to the harnesses you use. EasyCode never
   reads their credentials.
4. [The `easycode` CLI](/setup/cli): [`easycode open`](/reference/cli#open) registers a folder and opens it in the app.

### Work in sessions

5. [Start a session](/guides/start-a-session): pick a repo, a harness and a task, and see what the session is given.
6. [Pick up a session](/guides/pick-up-a-session): **Pick up** a teammate's session, or use **Continue in…** to carry
   on in another harness when one hits its limit.
7. [Workflows, gates and the board](/guides/workflows-and-the-board): **Start task** opens a session on a card, and
   **Run workflow** walks it through your org's steps and gates.

### Make the agent know your code

8. [Bring your kit](/guides/bring-your-kit): your `CLAUDE.md`, `AGENTS.md` and skills keep working, and can become
   the org's.
9. [Set up knowledge for a repo](/guides/set-up-knowledge): repo contexts every session reads, so the agent
   starts from what your team knows.
10. [Propose a library change](/guides/propose-a-library-change): a skill or agent you improved becomes a draft
    your team reviews before it is published.

### Prove it and ship

11. [Test in the built-in browser](/guides/browser-testing): the agent opens your local app, checks the page and
    saves proof for the pull request.
12. [From idea to merged PR](/scenarios/idea-to-merged-pr): the whole loop, end to end, with the steps above in
    order.
13. [From invite to merged PR](/walkthroughs/invite-to-merged-pr): the same loop as a walkthrough of real screens.

## What does the agent get in a session?

Each session has EasyCode's tools beside your harness's own. The work tools let the agent read and move tasks, such as [`task_get`](/reference/mcp-tools#task-get) and [`task_move`](/reference/mcp-tools#task-move), and report a workflow step with [`run_step`](/reference/mcp-tools#run-step). [`session_read`](/reference/mcp-tools#session-read) reads the session's earlier history after a pick-up. The full list is in
[MCP tools](/reference/mcp-tools).

> **Gated**
>
> Pick-up, workflow runs and the board follow your org's modules. EasyCode staff can pause pick-up with the [`pickup`](/reference/kill-switches-and-modules#pickup) switch and workflow runs with [`runs`](/reference/kill-switches-and-modules#runs). See
> [Kill switches and modules](/reference/kill-switches-and-modules).

## Where next

- [How it fits together](/overview/how-it-fits-together): orgs, products, repos, sessions and the library in one
  picture.
- [Settings](/reference/settings): runner settings such as [`handoff.budgetTokens`](/reference/settings#handoff-budgettokens) and [`repos.searchRoots`](/reference/settings#repos-searchroots).
- [Troubleshooting](/help/troubleshooting) when a harness or the runner misbehaves.
