Installation

4RGE has several surfaces: the desktop app (IDE), the CLI, cloud agents, and a mobile companion. Most people start with the desktop app. This page covers system requirements, per-platform install notes, and how the other surfaces fit in.

System requirements

Cloud agents and the mobile companion do not install a full IDE on your machine — they run against your 4RGE account and organization policy from the cloud.

Desktop app

1. Download

   Get the installer for your platform from your organization's 4RGE download page. Builds are typically signed for macOS (Apple notarization), Windows (Authenticode), and Linux (package maintainer signatures).

2. Install

   Run the installer for your platform — see per-platform notes below.

3. Sign in

   Launch the app and sign in to your organization. First launch may download additional components and build a local index of your opened workspace.

4. Open a repository

   Use File → Open Folder and select your Git repository root. The agent scopes all tool access to this directory.

macOS

• Installer format: .dmg — drag 4RGE to Applications.
• Architecture: Universal builds support Apple Silicon and Intel; Rosetta is not required on M-series Macs.
• Permissions: macOS may prompt for accessibility or file-access permissions depending on features you use. Grant access to the folders you intend to open.
• Updates: The app checks for updates in the background; restart when prompted to apply.
• CLI: Optional — install the CLI via the in-app setup flow or CLI installation and add it to your PATH in .zshrc or .bash_profile:

# Example: add to PATH after CLI install (path may vary by version)
export PATH="$HOME/.4rge/bin:$PATH"

Windows

• Installer format: .exe (per-user or machine-wide, depending on your org's package).
• Architecture: 64-bit x64. ARM64 Windows is not supported on all channels — check your download page.
• Terminal: The agent's shell tool uses your default terminal environment. If you rely on WSL, open the repo from a path WSL can access or run the CLI inside WSL — see CLI installation.
• Antivirus: Some enterprise AV suites scan new IDEs aggressively on first launch. Allowlist 4RGE if startup is slow or file watchers are blocked.
• Updates: Background download with restart-to-apply, similar to macOS.

Linux

• Packages: .deb for Debian/Ubuntu derivatives, .rpm for Fedora/RHEL derivatives, or a portable archive depending on your org's distribution.
• Dependencies: libfuse2 or equivalent may be required for AppImage builds; distro packages declare dependencies in the package manager.
• Wayland vs X11: Both are supported; if screen sharing or certain browser tools misbehave on Wayland, try the X11 session or see Troubleshooting.
• Sandboxing: Flatpak or Snap builds may restrict filesystem access — grant the project directory when prompted.

CLI

The 4RGE CLI runs agents from the terminal without opening the desktop IDE. It shares your account, model catalog, and organization policy.

1. Install the CLI

   Follow CLI installation for your platform. Installation is separate from the desktop app — you can use either or both.

2. Authenticate

   Run the login command documented on your CLI download page. Credentials are stored for subsequent runs in the same user account.

3. Run from a repository

   cd into your Git repository and start an agent run. The CLI uses the current directory as the working tree, same as the desktop app.

When to prefer the CLI:

• Scripting repeated agent tasks in your shell
• Headless CI runs in pipelines with structured output
• SSH sessions on remote dev machines where a GUI is unavailable
• Kicking off cloud agents from automation

# Illustrative — exact commands are on your CLI product page
cd ~/src/my-service
4rged agent run --prompt "Add structured logging to the HTTP middleware"

Cloud agents

Cloud agents do not require a local install beyond a surface that can start them — the desktop app, CLI, automations, or integrations. Execution happens in 4RGE-managed cloud environments.

To use cloud agents you typically need:

1. A connected repository — see Cloud agents · Setup
2. GitHub (or your VCS integration) granted to the org — see GitHub
3. Network and egress policy approved by your admin — see Security & network

Cloud runs continue after you close your laptop. Review results in the app, on the web dashboard, or via pull requests the agent opens.

Install artifacts and release URLs

Desktop installers and CLI tarballs are served from downloads.4rged.ai (override with X4RGE_DESKTOP_RELEASE_BASE_URL or X4RGE_CLI_RELEASE_BASE_URL in custom deployments). The bash install script at 4rged.ai/cli/install downloads a versioned archive, verifies its SHA-256 checksum, and places the 4rged binary in ~/.local/bin by default. Pin CI installs with X4RGE_CLI_VERSION when your org certifies a specific release.

Mobile companion

The mobile companion is for staying connected to 4RGE when you are away from your desk. It is not a full IDE — you will not edit code on your phone — but it keeps cloud work moving.

Install from your organization's mobile distribution link (TestFlight, Play Store, or MDM). Sign in with the same organization identity as the desktop app. Mobile access respects the same roles — members see their runs; admins see org-wide views where policy allows.

Updating

The desktop app updates itself in the background; restart to apply. The CLI may need a separate update via your package manager or the install script — check 4rged --version against your org's recommended version.

Verify your installation

After install, confirm everything works:

1. Sign in and see your organization name in the shell or title bar.
2. Open a small Git repository and confirm the agent panel loads.
3. Select a model from the picker (or run 4rged policy models --surface desktop on the CLI).
4. Run a trivial task — e.g. "Summarize the README" — and approve one tool step.

If any step fails, see Troubleshooting or Quickstart.