Projects overview
A project is where a team's work lives on X4RGE — the repositories you care about, the tasks you track, and the people who can access them. When someone runs an agent from a project, X4RGE knows which code, which policy, and which usage bucket apply.
This is not org-wide admin (that's the dashboard). Projects are how squads organize day-to-day delivery — one initiative, one shared context, one place to see progress.
What this page is for
Who can see and change what
Project admins manage their project. Org admins manage every project and org-wide policy (Model control, Usage).
Why projects matter
Projects are the unit of work between your org and a single codebase or product line. Most teams create one project per service, migration, or product squad.
How projects fit together
Typical flow: create project → link repo → add members → create tasks → run agent from desktop, CLI, or cloud.
In practice
What a project contains
Every project is a shared workspace with a few building blocks:
Create work items, move them through statuses, and save team views.
Add people, set a project lead, and understand project vs org permissions.
Project status
Projects use a simple lifecycle so leads and admins can tell active work from history:
Health indicators (on track, at risk, off track, no update) on the project overview help leads spot stalled work without opening every task.
Create a project
New project
From Projects, choose New project. Give it a name and a short key (used in task IDs like
ATL-42). Link one or more GitHub repositories when ready.Add members
Open Members for the project. Add people from your org. Assign project admin to whoever manages repos and membership; use member for contributors. Set a project lead for accountability.
Confirm scope
Check linked repos and any project-level model or budget rules your org admin set. Project rules can be stricter than org defaults — never wider.
Start working
Create tasks, save a default view for the team, and run the agent from this project to begin making changes.
Larger orgs often clone a planned project from a template — default views ("My work", "Blocked", "This cycle"), labels, and an integration checklist — instead of rebuilding structure for every initiative.
Work with agents in a project
When you start an agent from a project, X4RGE applies effective policy for that scope — which repos the agent can use, which models are allowed, and how usage is counted. The same person may have different models or repo access in two projects.
Runs from the desktop, CLI, or cloud agents all respect project scope when you start them in project context. Usage shows up on the project's activity and in org Usage.
Keep repo-specific conventions and build instructions where your team already documents them
(for example project rules or AGENTS.md in the repository). Projects give agents scope;
your repo gives agents how to work in that codebase.