Use developer tools

Aside includes a command-line interface (CLI), Model Context Protocol (MCP) support, and a browser automation REPL.

Install the CLI

macOS
Windows

Run:

curl -fsSL https://releases.aside.com/install.sh | bash

Open PowerShell, download the signed installer, verify its publisher and timestamp, then run it:

$ErrorActionPreference = 'Stop'
$ProgressPreference = 'SilentlyContinue'
$installer = Join-Path $env:TEMP 'aside-install.ps1'
$publisher = 'CN=AT YOUR SIDE INC, O=AT YOUR SIDE INC, L=San Francisco, S=California, C=US'
Invoke-WebRequest -UseBasicParsing -Uri https://releases.aside.com/install.ps1 -OutFile $installer
$signature = Get-AuthenticodeSignature -LiteralPath $installer
if ($signature.Status -ne 'Valid' -or $null -eq $signature.SignerCertificate -or $signature.SignerCertificate.Subject -ne $publisher -or $null -eq $signature.TimeStamperCertificate) {
  throw "Aside CLI installer signature verification failed ($($signature.Status): $($signature.StatusMessage))."
}
& $installer

The Windows installer adds Aside to your user PATH. Open a new terminal if aside is not available immediately. If signature verification reports UnknownError on a managed device, ask your administrator to add Microsoft Identity Verification Root Certificate Authority 2020 to the Trusted Root Certification Authorities store.

The developer settings page can also install, update, or reinstall the CLI directly. Run aside --update to check for updates from the terminal.

Prepare CLI credential storage

When signing the CLI in on another computer, including an assistant’s hosted environment, set ASIDE_CLI_AUTH_PATH before running aside login. Choose an absolute file path, not a directory, in private storage that the current process is allowed to write and that remains available for later commands. Verify the parent directory exists and is writable; do not assume $HOME is writable. Replace the example path and email with real values:

export ASIDE_CLI_AUTH_PATH="/your/allowed/private/path/aside-auth.json"
aside login --email "you@example.com"

In PowerShell, set $env:ASIDE_CLI_AUTH_PATH = 'C:\your\allowed\private\path\aside-auth.json' before running the same login command. Keep the login process running while approving its code in Aside Settings > Account > Devices. Wait for Signed in as ... before continuing. Approval alone does not confirm that the CLI saved its credentials. Pass the same ASIDE_CLI_AUTH_PATH to every later Aside command, including commands in new shells or agent tool calls. A shell export does not configure separate future shells automatically. Never print, upload, commit, or share the credential file; do not store it in a public, shared, or temporary directory. If the environment does not permit credential storage, stop and report the limitation rather than bypassing its restrictions. Without this variable, the CLI uses ~/.aside/cli/auth.json. ASIDE_HOME does not change this CLI credential path, and ASIDE_CLI_AUTH_PATH does not relocate the CLI installation or other configuration files. If login fails after approval while creating a directory (ENOENT or EACCES), resolve the storage issue first, then start a fresh login and approve its new code.

Run a browser task

Use aside to start a browser agent session from the terminal:

aside "Open localhost:3000 and run a smoke test"

Use --session to continue an existing session:

aside --session <session-id> "Continue"

Manage accounts

If you are signed in to more than one Aside account, each CLI command runs under one selected account. Use the account commands to inspect, switch, or target accounts from the terminal. List the accounts available on this device. The current account is marked with *:

aside account list

Show the current account, or check a specific one by ID:

aside account status
aside account status u1

Set the default account for future commands:

aside account use u1

Target a single run at a specific account with the --account flag. It works on aside and on aside exec:

aside --account u1 "Summarize the current page"
aside exec --account u1 -m openai-codex/gpt-5.5 "Plan this workflow"

If the selected account is signed out, the CLI prints a warning explaining how to recover. Your own provider keys (OpenAI, Anthropic) keep working, but built-in Aside models require an active sign-in. Sign in again from Aside Settings > Account, or switch to a signed-in account with aside account use <id> or --account <id>.

Use MCP

Use aside mcp to connect Aside to another agent or coding tool as a Model Context Protocol server.

aside mcp

For clients that support mcp.json, add:

{
  "mcpServers": {
    "aside": {
      "command": "aside",
      "args": ["mcp"]
    }
  }
}

If Developer settings found a concrete CLI path, use that path for command. Aside can install browser automation setup for supported coding tools. Developer settings also describe MCP setup for tools that support mcp.json.

Use the REPL

Use aside repl for browser automation REPL tasks:

aside repl "const p = await openTab('https://example.com')"

Use the REPL when you need direct page inspection, screenshots, downloads, or deterministic browser steps.

Run tasks

Get started

Work in Aside

Password Manager

Settings and safety

Developers

Changelog

Use the CLI, MCP, and REPL

Use developer tools

Install the CLI

Prepare CLI credential storage

Run a browser task

Manage accounts

Use MCP

Use the REPL

​Use developer tools

​Install the CLI

​Prepare CLI credential storage

​Run a browser task

​Manage accounts

​Use MCP

​Use the REPL

​Related

Use developer tools

Install the CLI

Prepare CLI credential storage

Run a browser task

Manage accounts

Use MCP

Use the REPL

Related