Core concepts
A handful of ideas show up on every X4RGE page. This short guide explains them in plain language so the rest of the docs make sense — whether you are running your first task, joining a team project, or checking why an admin setting matters.
You do not need to memorize everything here. Use it as a map, then jump to the guide that matches what you are doing today.
What this page is for
After Quickstart, come back here when a doc mentions org policy, project scope, or model access.
Who this page is for
Understand 4RGE at a glance
Simple mental model: your org sets the rules → projects scope day-to-day work → agents do the work → you review before anything merges.
Organization and workspace
An organization is the top-level home for your company or team on X4RGE. It holds:
When you sign in, you work inside one org (your workspace). If you belong to multiple companies on X4RGE, you switch between them — each has its own members, projects, and settings.
Org-wide admin lives in the dashboard. That is separate from coding in the desktop app or cloud agents.
Members and roles
Everyone on X4RGE is a member of an organization. Your role controls what you can change:
Org membership gets someone into your company. Project membership limits which repos and tasks they see. Many orgs require project assignment before agents run — see Settings.
Org vs project
Easy to confuse — here is the split:
Rule of thumb: org = house rules; project = where this team works.
Projects
A project groups related work — linked repositories, tasks, views, and the people who can access them. Agents started from a project inherit that scope: the right repos, policy, and usage bucket.
Projects organize how your team uses X4RGE — they do not replace Git.
Agents
An agent is the AI that understands your request, reads the codebase, runs tools (tests, terminal, integrations), and shows you a diff to review.
Every agent run follows the same loop:
- Understand your prompt and context
- Act with tools (within policy)
- Verify with tests or checks when possible
- Present results for your review
You approve sensitive steps. Nothing merges without your OK — see Agent security.
Desktop vs cloud
Same agent capability — different where it runs:
Many teams use desktop for exploration and cloud for longer tasks on the same repos.
Tools and approvals
Agents do not get unrestricted access to your machine or network. Reading files, running commands, and calling connected apps go through a controlled tool model with approvals when it matters.
Org admins set which integrations and plugins are allowed so desktop and cloud behave consistently.
Integrations
Integrations connect X4RGE to tools your team already uses. Admins configure them; members use them through agent and cloud runs.
Connect GitHub first for cloud agents and PR workflows. Add Slack and Linear when connect is ready — see each integration page for what works today.
Usage and budgets
Every agent run uses usage (tokens / spend). What you see depends on your role:
Admins set budget policies for the org. Enterprise contracts and capacity are managed separately by platform operators — see Console if your company uses it.
Members do the work. Org admins set house rules (models, budgets, settings). Platform operators set enterprise ceilings when applicable.
How it fits together
Typical path: sign in to org → open or join a project → start an agent → review diff → merge or open PR.