Skip to main content

Welcome to 4RGE

4RGE is an AI coding assistant for your team — describe what you need in plain language, review what the agent proposes, and ship with confidence. Use it on your laptop, in the cloud, or from the terminal — one account, one set of projects and rules.

You stay in control: the agent shows changes and waits for your approval before anything lands in your code. This page is your map of the docs — what 4RGE is, how to pick a workflow, and where to go next.

This documentation is searchable — press ⌘K (or Ctrl K) anywhere to jump to any page or topic.

What this page is for

Use this welcome page to orient yourself before diving into setup guides.

You want to…This page helps you…
Understand what 4RGE isAI assistant for coding — not a separate chatbot bolt-on
Pick where to workDesktop, cloud, or command line — same org behind all three
Start todayLinks to Quickstart and Installation
See how teams use itCommon day-to-day patterns below
Connect your stackGitHub today; Slack and Linear on the roadmap
Find the right docWhere to go next by role and goal

Who this page is for

You are…Start here
New developerAlready signed up?Quickstart
Team lead / PMWhat you can do + Projects
DevOps / platformCommand line + Headless & CI
Org adminDashboard overview after skimming this page
Evaluating 4RGEWhat 4RGE is and is not + Core concepts

What 4RGE is and is not

4RGE is4RGE is not
An agent that reads and edits your repo with your approvalA black box that merges code without review
Desktop, cloud, and CLI on one platformThree different products with separate billing
Scoped to your organization and projectsA personal-only tool disconnected from team policy
Good for fixes, features, refactors, and reviewsA replacement for code review, tests, or your judgment
Same rules everywhere

Models, usage, and admin policy apply across desktop, cloud, and CLI — see Model control and Usage.

Understand 4RGE at a glance

TermPlain meaningExample
AgentAI that plans, edits, and runs tools in your repo"Fix the failing auth test"
Desktop appIDE-style assistant on your machineExplore code with diffs in UI
Cloud agentsRuns continue in the cloud after you close the laptopLarge refactor overnight
CLI4rged command in the terminalQuick fix or CI pipeline
ProjectTeam scope for repos, tasks, and usageProjects overview
PromptWhat you ask the agent to doClear goal + how to verify
ApprovalYou review diffs before acceptSensitive changes pause for OK

Typical first week: install → sign in → one small task on desktop → learn Core concepts → add GitHub when ready.

Already signed up? Get started now

Choose how you want to work

Pick the surface that matches how you work today. You can switch anytime — your account and projects stay in sync.

Desktop vs cloud vs CLI

All three use the same org and models — choose by session length and where you sit.

DesktopCloudCLI
Best forExploring code, rich UI, back-and-forthLong jobs, background workTerminal, scripts, CI
Where work runsYour machineX4RGE cloud sandboxYour machine (or cloud handoff)
Get startedQuickstartCloud agentsCLI overview
SituationStart here
First time using 4RGEDesktopQuickstart
Fix tests before lunchDesktop or CLI local
Migration that takes hoursCloud agents
PR check on every pushCLI + Headless & CI

What you can do with 4RGE

The most common ways teams use 4RGE day to day — you can mix all three.

1

Build and fix on your computer

  • Describe what you want in everyday language and review changes before accepting
  • Fix bugs, add features, and keep tests passing
  • Ask the agent to explain unfamiliar code before you edit it
2

Hand off longer tasks to the cloud

  • Start bigger refactors or test sweeps and come back when they are done
  • Review results in Diff and Review before merging
  • Learn more in Cloud agents
3

Work with your team

  • Share progress on Projects so everyone stays aligned
  • Link agent runs to Tasks & views when your team tracks work there
  • Same policy on desktop, cloud, and CLI — admins set rules once in the dashboard

What good prompts look like

  • Say what done means and how to verify (for example "make auth.test.ts pass")
  • Name files or areas when you know them; keep scope small on first runs
  • Never paste secrets — use env var names; see Agent security

What success looks like

  • You reviewed diffs and tests before merge
  • Usage shows under your org in Usage
  • Your team knows which project owns the repo

Connect your tools

Link 4RGE to apps your team already uses. GitHub is fully connectable today; Slack and Linear appear in the product and are documented for what is coming next.

GitHub first for production work

Use GitHub for live repo and PR workflows. Use the Agents workspace for cloud runs until Slack and Linear connect fully ship.

Where to go next

Jump to the doc that matches your goal — you do not need to read everything in order.

Your goalNext doc
First task todayQuickstart
Install desktop or CLIInstallation
Learn the vocabularyCore concepts
Automate in CICLI Headless & CI
Long background workCloud agents overview
Team tasks and viewsProjects overview
Something brokeTroubleshooting
Admin: models and spendDashboard overview

Help and next steps

Questions about 4RGE?

QuestionAnswer
What is 4RGE?AI coding assistant — desktop, cloud, and CLI on one platform
Do I need all three surfaces?No — pick what fits; same account everywhere
Is it safe to use on company code?Review diffs, approvals, and org policy — Agent security
Where do admins configure models?DashboardModel control
Does usage count toward billing?YesUsage
GitHub vs Slack vs Linear?GitHub connect today; Slack and Linear documented for upcoming connect
First doc after this page?Quickstart for almost everyone