How it fits together
Orgs, spaces, teamspaces, products, repos, sessions, the library, knowledge and work, and how each one relates to the rest.
EasyCode has a handful of building blocks. Once you know how they nest, every screen makes sense. This page uses one example throughout: the org Northwind, with a teamspace Checkout, which owns the product Northwind Pay.
Org
An org is your company in EasyCode. It holds the people, the teamspaces, the products, the repos, the library and the work. Everything you see in the web app belongs to one org, and nothing crosses from one org to another. You can belong to more than one org and switch between them.
Each person has one org role: owner, admin, member or guest. Roles and access says what each can do.
Spaces
On your machine, the desktop app keeps your work in spaces. Personal is yours alone. Each org you belong to is a space of its own. Sessions in Personal stay on your machine; sessions in an org space are team sessions, which your org can see. Choose the space before you start a session. Settings → Spaces sets each space's default harness accounts, git identity and email domains.
Teamspaces
A teamspace is a group of people, usually a team: Checkout, Platform, Growth. Teamspaces own products and give their members access to them. A teamspace is open, closed or private, and has leads and members. Every org has a default teamspace, Everyone, which always stays open. A guest is never in it.
Products
A product is something your teams ship, such as Northwind Pay. A product has an owner teamspace, links one or more repos, and has its own tasks, sessions, knowledge and library assets. Access to a product is a role: viewer, contributor or maintainer. A teamspace or a person is granted a role on the product, and you hold the highest role any of your grants gives you.
A design system is a special kind of product that other products use. That module is in the pilot.
Repos
A repo is a GitHub repository connected to the org through the GitHub App. An admin connects repos and links them to products: one repo can serve several products, and one product can span several repos. To read a repo's code in EasyCode, you also need read access to it on GitHub. Products and repos covers the setup.
Sessions
A session is one conversation with a harness, working in a repo on your machine. Your harness runs it on your own login. In an org space, the session is a team session: its title, status and cost reach the org, and so do its redacted transcript and patch, unless you mark it Private or your org keeps content off. Teammates with access can read it, comment on it and pick it up. Start a session.
The library
The library is your org's shared kit: skills, agents, guides and MCP servers. An asset lives at a scope: the org, a teamspace, a product, or just you. A change is proposed, reviewed and published, and every harness then gets the same published version. Propose a library change.
Knowledge
Knowledge is what EasyCode knows about each repo and product: a context for each repo and a map of each product. Sessions read it so an agent starts with the shape of the code. An admin or a product's maintainer sets it up, and it is refreshed as the code changes. Set up knowledge.
Work
Work lives on the Board as tasks, each on a product. A workflow takes a task through its steps as a run, and a gate waits for an approver before the run moves on. A task can carry documents, such as a spec, that your team writes together. Workflows, gates and the board.
The studio
The studio holds artifacts: pages, frames and prototypes your sessions make. You share them with people or teams, comment on them and review them. Share and review in the studio.
How it nests
Org (Northwind)
├── Members: owner, admins, members, guests
├── Teamspaces (Checkout) ── own ──> Products (Northwind Pay)
│ ├── Repos (via the GitHub App)
│ ├── Knowledge
│ ├── Tasks, runs and documents
│ └── Sessions
├── Library: org, teamspace, product and personal scopes
└── Studio: artifacts, shared by grantSome areas are modules your org has on or off: sessions, the library, knowledge, workflows, the studio and design systems among them. When a module is off, its item leaves the rail. See Kill switches and modules.
Something wrong or missing? Suggest a change