Overview

What EasyCode is

EasyCode runs every harness on your own login, for every role, with one org brain and one flow from idea to shipped.

Last updated November 16, 2026View as Markdown

EasyCode is the place a software team does its work with coding agents. It runs the agents you already use, on your own logins. It gives developers, PMs, QA, designers, DevOps and marketers one shared place to work. It keeps what your org knows in one place that every session reads. And it carries a piece of work from an idea to a merged pull request.

Every harness, on your own login

A harness is a coding agent you run from a terminal, such as Claude Code or Codex. EasyCode drives seven of them: Claude Code, Codex, Cursor, Copilot, Gemini, OpenCode and pi. Each one runs unmodified on your machine, signed in with your own account. EasyCode never reads its credentials and never signs in for you.

You pick the harness when you start a session, and you can switch: a teammate can pick up your session in another harness. Support differs per harness; some are marked preview. The harness reference lists each one's install command, sign-in command and tested versions.

Every role, one place

Sessions are not only for developers. A PM writes a spec as a document on a task. QA tests a build in the desktop app's built-in browser and sends what they find to an agent. A designer shares frames in the studio and reviews them live. Everyone works from the same board, the same products and the same library. The role pages show where each role starts.

One org brain

Every session in your org starts with what your org has agreed:

  • The library holds your shared skills, agents, guides and MCP servers. A change to it is proposed, reviewed and published, and every harness gets the same version.
  • Knowledge describes each repo and each product, so an agent knows the code before it starts.

You don't copy a kit into every repo by hand. You bring your existing kit once, and EasyCode keeps every harness in step.

One flow, from idea to shipped

Work lives on the Board as tasks. A workflow takes a task through its steps, and a gate waits for a person to approve before work moves on. Sessions report to the task they work on. When the work is done, you open the pull request from the app. Workflows, gates and the board explains the flow.

How you use it

The desktop app runs on macOS, Windows and Linux. It is where you start sessions: it runs a local runner that drives your harnesses on this machine, and it signs you in to your org. It also has the built-in browser for testing. Set up the desktop app.

What stays on your machine

Your harness logins, your working tree and your Personal sessions stay on your machine. A Private org session keeps its content there, while your team still sees that it exists. Your org receives what the team needs to work together. Security and privacy lists exactly what leaves.

Next

Something wrong or missing? Suggest a change

On this page