By role

For developers

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

Last updated November 15, 2026View as Markdown

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: join your org and run your first session in a few minutes.
  2. Desktop app: it holds the runner your sessions run on, and the built-in browser.
  3. Harnesses on your own login: install and sign in to the harnesses you use. EasyCode never reads their credentials.
  4. The easycode CLI: easycode open registers a folder and opens it in the app.

Work in sessions

  1. Start a session: pick a repo, a harness and a task, and see what the session is given.
  2. 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.
  3. Workflows, gates 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

  1. Bring your kit: your CLAUDE.md, AGENTS.md and skills keep working, and can become the org's.
  2. Set up knowledge for a repo: repo contexts every session reads, so the agent starts from what your team knows.
  3. Propose a library change: a skill or agent you improved becomes a draft your team reviews before it is published.

Prove it and ship

  1. Test in the built-in browser: the agent opens your local app, checks the page and saves proof for the pull request.
  2. From idea to merged PR: the whole loop, end to end, with the steps above in order.
  3. From 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 and task_move, and report a workflow step with run_step. session_read reads the session's earlier history after a pick-up. The full list is in MCP tools.

Gated

Pick-up, workflow runs and the board follow your org's modules. EasyCode staff can pause pick-up with the pickup switch and workflow runs with runs. See Kill switches and modules.

Where next

Something wrong or missing? Suggest a change

On this page