Skip to main content
A project is the context group your threads run in. It owns the repository catalog (which repos a machine gets, and each repo’s base branch), the dev environment, environment variables, snapshots, automations, and integration routing like Linear team mappings. Project threads spawn with project repos cloned automatically. Every enabled member of the organization can read every non-personal thread in every project. Service users, however, carry their own project access (all projects, or an explicit list). Repository access is gated through GitHub: a human’s clones and pushes use their own GitHub access and a service user’s run through the Capy GitHub App installation.

​
Repositories

A project carries an ordered list of repositories, each with a base branch: the branch machines check out and PRs target by default. You can also create repoless projects for research, planning, and general computer-use work. Connecting the GitHub App grants Capy access to clone and use repos for projects. You pick what the App may reach in GitHub’s installer, then pick what the project contains in Capy’s repository picker.

​
Identity

Each project has a name, an icon/emoji, and a short uppercase code of up to four letters that prefixes thread references: CAPY-42 is thread 42 of the project with code CAPY.

​
Working across projects

You can view threads from every project in the threads page. Folders and tags are organization-wide and can mix threads from different projects freely.