Overview
Projects are the top-level organizational unit in Contox. Each project has its own memory brain, sessions, and settings. A project typically corresponds to a single codebase or repository.
Creating a project
- Navigate to the Projects page in the dashboard
- Click New Project -- a modal appears with a creation form
- Enter a name (e.g., "my-saas-app") and optional description
- Choose the visibility setting (Public or Private)
- Click Create
The project card appears immediately in the project list:
You can see the project name, description, context count, and status badge. Click the gear icon on the project card to access settings.
After creating a project in the dashboard, link it to your local directory with contox init -t <team-id> -p <project-id> to use CLI or MCP commands from that project directory.
Project settings
Name and description
The project name is displayed throughout the dashboard and in the brain document. Choose a descriptive name that your team will recognize. The description is optional and appears in project listings.
Visibility
Projects have two visibility modes:
| Visibility | Description |
|---|---|
| Private | Only explicitly added project members can access this project |
| Public | All team members can access this project |
Public visibility is useful for shared repositories that the entire team works on. Private visibility is appropriate for personal projects or sensitive codebases.
AI Model
Configure the enrichment AI model per-project. Open project settings and go to the General tab:
- Small (
mistral-small-latest) -- Fast and cost-effective processing - Medium (
mistral-medium-latest) -- Higher quality analysis and extraction
The default model depends on your plan (Small for Free/Personal, Medium for Team+). All paid plans can override the model. Free plan users see the options but must upgrade to change them. Setting the model to "Default" uses your plan's built-in model.
Repository
Link a GitHub repository to enable deep enrichment -- AI reads your source code for richer memory. Open the Repository tab in project settings.
Connecting with GitHub OAuth (recommended)
- Click Connect with GitHub
- Authorize Contox in the GitHub OAuth popup
- Select a repository from the picker
- Done -- deep enrichment is enabled by default
Connecting with a Personal Access Token
- Toggle to Personal Token in the connection form
- Enter the repository URL (e.g.,
https://github.com/org/repo) - Paste a GitHub PAT with
reposcope - Click Test Connection to verify access
- Click Save & Connect
Deep Enrichment toggle
Once connected, the Repository tab shows a Deep Enrichment switch. When enabled (the default), the pipeline adds a deep_enrich stage that reads source files from your repo and enriches memory items with implementation details (routes, schemas, function signatures, auth flows).
Disable the toggle to skip GitHub API calls and reduce token usage.
Managing the connection
- Change repository -- Select a different repo without re-authenticating
- Unlink repo -- Remove the repo URL but keep GitHub authentication
- Disconnect GitHub -- Remove all GitHub credentials and repo data
Status
Projects can be active or archived. Archived projects retain their data but do not accept new events or sessions.
Member management
Adding members
- Open your project and go to Members
- Click Add Member
- Enter the email address of the user to invite
- Select a role (admin or member)
- Click Invite
The invited user receives an email notification. They must accept the invitation to gain access.
Roles
Project members inherit their team role, but project-level access is also controlled by visibility:
| Role | Capabilities |
|---|---|
| Owner | Full access including project deletion and member management |
| Admin | Manage project settings, members, and all project data |
| Member | Read and write access to project memory, sessions, and contexts |
Removing members
Click the remove button next to a member's name to revoke their access. This takes effect immediately.
Project data
Each project contains:
- Brain -- The assembled memory document
- Sessions -- History of captured work sessions
- Memory items -- Structured knowledge extracted by enrichment
- Contexts -- Hierarchical context tree
- HMAC secret -- Used for V2 ingest authentication
Deleting a project
Deleting a project permanently removes all associated data including memory, sessions, contexts, and settings. This action cannot be undone.
- Open the project settings
- Scroll to the danger zone
- Click Delete Project
- Confirm the deletion