CLI Installation
Need unlimited generations and frontier models? Architect Pro — unlimited validated workspaces and priority queue for $20/month. See plans →
The Logic64 CLI (logic64-cli) is a Node.js command-line tool distributed via npm. It authenticates with the Logic64 API, downloads validated workspace bundles, and routes every file to its correct destination on your machine — project files, global configs, and environment templates — with full rollback support.
This page covers installation, authentication, and verification on macOS, Linux, and Windows. For the full command reference see CLI Reference.
Prerequisites
Verify the following before installing:
- Node.js 18 or later — check with
node --version. Download from nodejs.org if needed. - npm — bundled with Node.js. Confirm with
npm --version. - Operating system — macOS, Linux, or Windows. All three are supported.
- A Logic64 account with a Developer or Architect Pro plan to generate an API key. Sign up at Logic64 Studio.
Install globally
Install logic64-cli as a global npm package. The binary name is logic64.
$ npm install -g logic64-cli
On Linux and macOS, if your global npm prefix is owned by root, prefix the command with sudo:
$ sudo npm install -g logic64-cli
To avoid requiring sudo in the future, configure npm to use a user-writable prefix directory. See the npm permission guide for details.
Verify the install
Confirm the CLI is on your PATH and reports a version number:
$ logic64 --version
If the command is not found, your global npm bin directory may not be in PATH. Run npm bin -g to find the directory and add it to your shell profile. See Troubleshooting for common fixes.
Authenticate
Run logic64 auth with your API key and the public API endpoint. The CLI stores credentials locally so subsequent commands authenticate automatically.
$ logic64 auth --api-key l64_YOUR_KEY --api-url https://api.logic64.com
API keys follow the format l64_xxxxxxxx_xxxxxxxx…. Keys are displayed once at creation time — copy and store yours securely before closing the dialog.
To obtain a key:
- Open Logic64 Studio and sign in.
- Navigate to Settings → API Keys.
- Click Generate new key and copy the value shown.
For the full authentication specification — including the Authorization: Bearer l64_… header format used on all requests — see API Authentication.
Where the config is stored
After authenticating, the CLI writes your credentials and API endpoint to a local config file. By default this file lives at:
~/.logic64/config.json
This file is never transmitted anywhere beyond the initial auth call. It is read on every CLI invocation to supply the Authorization header. Do not commit it to version control.
Cross-platform config paths
When a bundle is pulled, the CLI resolves abstract destination_type values from manifest.json to real filesystem paths. The table below shows how each type maps per operating system.
| destination_type | macOS / Linux | Windows |
|---|---|---|
global_config (Claude) | ~/.config/claude-code/config.json | %APPDATA%\claude-code\config.json |
env_file | Project root /.env | Project root \.env |
project_root / workspace_root | Current working directory | Current working directory |
The CLI uses Node.js os.homedir() and process.env.APPDATA to resolve platform-specific base paths. Target directories are created automatically if they do not exist. If the expected config path is absent and the assistant is already installed, the CLI checks common alternative locations (e.g. $XDG_CONFIG_HOME on Linux) before creating a new file at the canonical path.
Every file the CLI writes is recorded in resolution_log.json at the project root. Global config files are backed up before any merge operation so you can restore them with logic64 rollback <bundle_id>.
Updating
Keep the CLI up to date to receive the latest routing logic and compatibility fixes:
$ npm update -g logic64-cli
To confirm the installed version after updating, run logic64 --version.
Uninstalling
Remove the CLI from your machine:
$ npm uninstall -g logic64-cli
Your local config file at ~/.logic64/config.json and any resolution_log.json files in project directories are not removed automatically — delete them manually if needed.
Troubleshooting
- Command not found after install — the global npm bin directory is not in
PATH. Runnpm bin -gto get the path, then add it to your shell profile (~/.bashrc,~/.zshrc, or the Windows system environment variables). - Permission denied on Linux / macOS — your global npm prefix is root-owned. Either use
sudo npm install -g logic64-clior reconfigure npm to use a user-writable prefix (see the npm permission guide). - Behind a corporate proxy — set the
HTTPS_PROXYenvironment variable before running any CLI command:export HTTPS_PROXY=http://proxy.example.com:8080. On Windows:set HTTPS_PROXY=http://proxy.example.com:8080. - 401 Unauthorized on pull — re-run
logic64 auth --api-key l64_YOUR_KEY --api-url https://api.logic64.comto refresh stored credentials. Verify the key is active in Studio → API Keys. - Node.js version too old — the CLI requires Node.js 18 or later. Run
node --versionand upgrade from nodejs.org if necessary.
Next steps
With the CLI installed and authenticated, you are ready to pull your first workspace bundle. The pages below cover the complete command set and the structure the CLI writes to disk.