Install the standalone argv-cli, connect this development machine to your ARGV account, then link a repository to a Project.
Before you start
- An ARGV account you can sign in to.
- A local checkout of the codebase you want to link. A Git origin is helpful but not required.
- A Linux or macOS shell, or Windows PowerShell, with network access.
1. Install argv-cli
Choose your platform, then run its installer command:
curl -fsSL https://argv.app/install.sh | shVerify the installed version. If the installer added the command to your shell configuration, open a new terminal first.
argv --versionFor future upgrades, run argv update. To check without installing, use argv update --check.
argv update2. Sign in from the CLI
Start the pairing flow:
argv login- The CLI creates a secure, expiring pairing request and opens its verification page in your browser.
- If you are not signed in, the browser asks you to sign in to ARGV first.
- Review the displayed environment name, platform, and CLI version.
- Choose Connect to approve this environment. Choose Deny if you did not start the request or the account is wrong.
- The terminal receives the approval, redeems the request, and stores its environment credential in your user configuration directory, outside the repository.
Expected output after browser approval
Opening ARGV in your browser…
Waiting for approval in your browser…
✓ Connected to ARGV
Environment: <computer name> workstationThe exact environment name comes from your computer name unless you configured ARGV_ENVIRONMENT_NAME.
3. Sign in without an automatically opened browser
On a headless machine or when the browser cannot be opened, run:
argv login --no-browserExpected headless prompt
Open: https://argv.app/device
Code: ABCD-EFGH
Waiting for approval in your browser…Open the URL on a browser where you can sign in, enter the code, continue, then approve the environment. The short code identifies only this pending request; it is not the durable environment credential. Keep the CLI process running until it confirms connection. If approval expires, run argv login again.
4. Check the environment connection
argv statusExpected output after login
Account
<your ARGV display name>
Environment
<environment name>
ConnectedBefore login, status reports Account — Not connected and tells you to run argv login. Workspace details appear only when the current directory has a workspace record in this environment's local config.
5. Link a repository workspace
Change to the repository directory you want to associate with an ARGV Project. Replace the example path with your repository's path:
cd path/to/your/repository
argv connectThe CLI checks the Git origin in the repository's .git/config. When present, it displays a normalized identity such as github.com/company/repository (host/path lowercased and a trailing .git removed). This repository identity is descriptive; it is not a credential. If no Git origin is detected, you may still continue and link the local workspace.
ARGV opens the workspace request in your browser. If asked, sign in to the same account that owns the CLI environment. Choose the ARGV Project this checkout represents and confirm with Connect workspace. The CLI waits for the browser approval and prints the linked Project name. No Project ID or local path needs to be copied manually.
If the browser does not open, the CLI prints the workspace approval URL. Open that URL manually and finish the same Project selection flow.
6. Confirm the workspace
While your shell is still in the linked repository, run:
argv statusExpected output after workspace approval
Account
<your ARGV display name>
Environment
<environment name>
Connected
Workspace
<current local repository path>
ARGV Project: <selected Project name>That link is a Local Workspace Binding between this CLI environment and the selected Project. It does not choose or bind a runtime to an Execution.
7. Disconnect
To remove this environment's local login and ask ARGV to revoke its credential:
argv logoutThe CLI removes the saved local configuration after attempting remote revocation. If ARGV is unreachable, it reports that remote disconnect could not be completed; remove the remote environment later in Settings → Connected environments. You can also disconnect from Settings at any time. Disconnecting an environment revokes its credential; workspace bindings belong to that environment and are not an Execution runtime selection.
8. Remove argv-cli
To disconnect this environment, remove its local credentials and workspace state, remove the PATH block installed by ARGV, and remove the managed CLI binary, run:
argv uninstallInteractive uninstall defaults to No. For a deliberate script or terminal session, pass --yes. By comparison, argv logout disconnects the environment and removes local credentials while keeping the CLI and PATH setup installed.
Troubleshooting
- The browser did not open. Keep the CLI running and open the printed URL. For login with no browser, use
argv login --no-browser, enter the short code at/device, approve, and return to the terminal. - The connection request expired. Start a fresh
argv loginorargv connectrequest and approve it before its expiry. Do not reuse an old short code or workspace URL. - I signed into the wrong ARGV account. Do not approve the request. Deny it, switch browser accounts, then start a new CLI request. If the environment was already connected to the wrong account, run
argv logoutand sign in again with the intended account. - The environment was disconnected or revoked. Status reports that the environment was disconnected. Run
argv loginand approve a new environment connection. - The repository was not detected. Check that you are in the repository and that
.git/configcontains anoriginremote. You can still link a workspace without a detected Git origin. - Status says the workspace is not connected. From that same repository directory, run
argv connect, choose the intended Project, and wait for the CLI's success message. Then runargv statusin the same directory. - The Project is missing from the picker. The picker lists Projects you can currently access. Create the Project or ask its owner to restore your access, then retry
argv connect. - Project access was lost after linking. Ask the Project owner to restore access. Then create a fresh workspace link with
argv connect. A previous binding does not restore Project authorization. - The CLI is missing or uninstall cannot remove its executable. Remove only the installed
argvbinary. Remove local data under~/.config/argv(or the Windows user AppData ARGV config directory). Remove a shell PATH entry only when it is inside the exact# >>> ARGV CLI >>>…# <<< ARGV CLI <<<managed block. On Windows, remove%LOCALAPPDATA%\argv\binfrom User PATH only if ARGV added it; do not remove similarly named paths or edit Machine PATH.