One source of truth for what your AI coding agents are told.

1. 1

   Set up your workspace

   A tenant administrator invites people, creates Teams and projects, and decides which knowledge layers need approval.

2. 2

   Build the library

   Anyone can write an artefact in the browser: Markdown with typed variables, supporting files and links to the artefacts it builds on. It is published directly, or after an administrator approves it.

3. 3

   Bring it into projects

   Team leads assign published artefacts to their projects as mandatory or optional. Each project gets its own copy, and decides when to take later library changes.

4. 4

   Write it into the code

   Developers run context login once in their project folder, then context browse to write the project's artefacts with variables and the project header filled in. context status and context pull keep them current, and every write is recorded.

Variables

Write {{placeholders}} into the Markdown and give each a type — text, number, yes/no, a list of allowed values, or JSON — with defaults and required rules. One artefact then fits many projects. Render fills them in and previews the finished file in the browser, ready to copy.

Attachments

Scripts, configuration, PDFs and images travel with the content: up to 20 files of up to 10 MB per version, versioned with it, and written next to the artefact's file by the CLI.

Dependencies

An artefact can require others — a CLAUDE.md that builds on the AGENTS.md baseline. The CLI writes what is required first, and assigning an artefact to a project brings its dependencies along.

Versions and activity

A save that changes the content, variables or attachments creates a new version; the published one stays live until its replacement is published. Every version opens exactly as saved, and the activity record shows who created, published, approved, assigned or changed it.

Artefacts

Every artefact in the project: a library copy or made for this project, Mandatory or Optional, its status — Update available when the library has moved on, No Access for private ones you may not view — whether and how often it was applied, and its rating.

Dependencies

A visual designer: what is applied first on the left, what builds on it to the right. Team leads draw and remove links and save them together.

Applied history

Every file the CLI wrote for this project: when, which artefact, by whom, which version and where in the folder, including updates by context pull.

Agent files

The project's GitHub repository, scanned read-only for the agent files it already contains.

Header

An optional block the CLI puts at the top of every file it writes for the project — the artefact's name, version and layer, the project, the date, the user, and the Git branch and commit.

context login

Signs in through the browser: the terminal shows a code, the developer confirms it in Context, and the folder is bound to one of their projects. It then lists the mandatory artefacts not yet written.

context init

Binds another folder with the session already signed in.

context browse

An interactive browser in the terminal: the project's artefacts with a preview and details, search across the project and the library, Write to folder, Add to project, attachments, and importing local documents as drafts.

context status

The mandatory artefacts still to write and, for each file Context wrote, its version, the published version and whether it was changed locally.

context pull

Updates written artefacts to the newest published versions with the values remembered from the first write. It never overwrites a local change without asking.

context logout

Ends the session and removes the stored credentials.

When it writes, the CLI asks for each variable's value — with defaults and what it already knows, such as the project name, filled in — adds the project header, writes the attachments next to the file, and reports the write to Context. A report that cannot be sent is kept and sent on the next run. A small .context folder in the project holds the binding and a list of what it wrote, which teams may commit.

Approvals

Submissions waiting for a decision, with a count in the navigation.

Users

Invite people by email, set their role, deactivate and reactivate them, and see who has not accepted an invitation yet.

Projects and Teams

Create projects and allocate them to Teams and people; manage each Team's members and leads.

GitHub

Tokens, with each one's account, status and expiry, and the repositories assigned to projects.

Knowledge layers

The approval switch, and each layer with its description, whether it needs approval, how many artefacts use it, and whether it is active.

Artefact types

Each type with what it contains and what applying it to a project does. A layer or type in use cannot be deleted — only deactivated, so existing artefacts keep it.