Glossary of terms
What the words EasyCode uses mean: org, space, teamspace, product, session, kit, library, gate and more, each with a link.
The words used across these docs, in alphabetical order. Each links to the page that explains it.
A–D
Admin: an org role that runs the org: settings, members, teamspaces, products, repos and publishing. Admins act as maintainer on every product. See Roles and access.
Artifact: a page, frame or prototype a session makes, kept in the studio and shared by grant. See Share and review in the studio.
Board: the org's view of its tasks, by status. See Workflows, gates and the board.
Built-in browser: the desktop app's browser pane, beside the session, for testing a build and sending what you find to an agent. Desktop only. See Test in the built-in browser.
Contributor: a product role that can create tasks, start runs, edit documents and pick up shared sessions. See Roles and access.
Design system: a kind of product that other products use, with a record of its tokens, components and releases. In the pilot. See The design system record.
Desktop app: EasyCode for macOS, Windows and Linux. It runs the runner, starts sessions and signs you in to your org. See Desktop app.
Document: a piece of writing on a task, such as a spec, that the team edits together. See Write a spec with your team.
E–K
Everyone: the default teamspace of every org. It always stays open, and guests are never in it. See How it fits together.
Gate: a step in a workflow that waits for a person to approve before the run moves on. Only a person in the web or desktop app decides one. See Workflows, gates and the board.
Guest: an org role for people outside the team. A guest sees only what they are given. See Roles and access.
Harness: a coding agent you run on your own login: Claude Code, Codex, Cursor, Copilot, Gemini, OpenCode or pi. See Harnesses on your own login and the harness reference.
Kill switch: a switch EasyCode staff can turn off for one org or all of them, such as pick-up or sync. While it is off, that feature pauses. See Kill switches and modules.
Kit: the instructions and tools a harness reads: CLAUDE.md, AGENTS.md, skills, agents and MCP servers. See
Bring your existing kit.
Knowledge: what EasyCode knows about each repo and product, read by every session. See Set up knowledge for a repo.
L–P
Lead: a teamspace role that manages the teamspace and its people. See Roles and access.
Library: the org's shared kit: skills, agents, guides and MCP servers, at the org, teamspace, product or personal scope. See Propose a library change.
Local app: EasyCode run from a source checkout with the easycode CLI, paired with one browser. See
The CLI.
Maintainer: a product role that manages the product, assigns tasks and sets up its knowledge. See Roles and access.
MCP server: a tool server a harness connects to. EasyCode gives sessions its own, and the library can share yours. See MCP tools.
Member: the org role for everyone on the team. See Roles and access.
Module: an area of EasyCode an org has on or off, such as the library, knowledge or the studio. When it is off, its rail item and settings are gone. See Kill switches and modules.
Org: your company in EasyCode, holding its people, products, repos, library and work. See How it fits together.
Owner: the org role above admin; only an owner makes or removes another owner. See Roles and access.
Pairing: how the local app trusts one browser, with a one-time link the CLI opens. See Troubleshooting.
Personal: the space that is yours alone. Its sessions stay on your machine. See How it fits together.
Pick-up: continuing a teammate's session, or your own on another machine, in the same or another harness. See Pick up a session.
Private session: a team session whose content stays on your machine; only its metadata reaches the org. See Security and privacy.
Product: something your teams ship. It links repos and holds tasks, sessions and knowledge. See Products and repos.
R–S
Repo: a GitHub repository connected through the GitHub App and linked to products. See Products and repos.
Run: one pass of a workflow over a task. See Workflows, gates and the board.
Runner: the local process that drives your harnesses and terminals. The desktop app starts it for you. See Troubleshooting.
Scope: where a library asset applies: the org, a teamspace, a product or just you. See Propose a library change.
Session: one conversation with a harness, working in a repo on your machine. See Start a session.
Skill: a reusable instruction set a harness loads when a task calls for it. Shared through the library. See Bring your existing kit.
Space: where a session belongs on your machine: Personal or one of your orgs. See How it fits together.
Studio: where artifacts are kept, shared, commented on and reviewed. See Share and review in the studio.
T–W
Task: one piece of work on the board, on a product. See Workflows, gates and the board.
Team session: a session in an org space. Its metadata, and unless Private its content, reach the org. See Security and privacy.
Teamspace: a group of people that owns products and gives its members access to them. See Org, members and teamspaces.
Viewer: a product role that sees a product and comments on its documents and artifacts. See Roles and access.
Web app: your org in a browser: the board, sessions, the library, the studio and settings. It starts no session. See Web app.
Workflow: the steps a task goes through, with gates between them. See Workflows, gates and the board.
Something wrong or missing? Suggest a change