# Install forcecli with Homebrew, scoop

Command-line interface to Force.com. Version 1.13.0 via Homebrew; verified 2026-07-26. Also installable with scoop: scoop install main/force.

## Install

```sh
sudo av install brew:forcecli
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install forcecli
```

  Evidence: local Homebrew formula metadata

### Windows

- Scoop (92%):

```sh
scoop install main/force
```

  Evidence: Scoop official bucket manifest trees: bucket/force.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:forcecli
- **Package manager:** Homebrew
- **Version:** 1.13.0
- **Source summary:** Command-line interface to Force.com
- **Homepage:** <https://force-cli.herokuapp.com/>
- **Repository:** <https://github.com/ForceCLI/force>
- **Last updated:** 2026-07-26T11:37:57+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- force (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.13.0
## Project history and usage

Force CLI is a Go command-line interface for Force.com and Salesforce orgs. The README identifies it as a command-line interface to force.com and documents commands for login, metadata import/export, SOQL queries, bulk APIs, Apex, packages, records, limits, and org inspection.

### Project history

The project is maintained in the ForceCLI/force repository. Its README labels the documented generation as force CLI v1.3.0, while the repository tag list shows later v1.x releases, including v1.13.0.

### Adoption history

The README documents precompiled binaries from the GitHub release page or CLI home page, plus source installation with Go. It also documents reuse of SFDX usernames or aliases when a stored force session is unavailable, placing the tool alongside Salesforce DX workflows rather than only older standalone Force.com usage.

### How it is used

Users authenticate with force login, list and switch saved logins, inspect objects, run SOQL, import and export metadata directories, deploy metadata, run Apex tests, and interact with Bulk API 1.0 and 2.0. The generated command docs expose a --config option whose default directory is .force, but no specific config file path is documented.

### Why package nerds care

Force CLI is significant as a standalone Go-era Salesforce CLI that predates or coexists with SFDX-style tooling. For package managers, it is a single executable that wraps authenticated cloud workflows, release binaries, and local metadata directory conventions.

### Timeline

- v1.3.0: README documents the command set under the force CLI v1.3.0 heading.
- v1.13.0: official Git tags include a later v1.13.0 release line.

### Related projects

- The README and command docs relate Force CLI to Force.com, Salesforce, SFDX authentication, Salesforce metadata directories, Apex, SOQL, and Bulk API workflows.

### Sources

- <https://github.com/ForceCLI/force>
- <https://raw.githubusercontent.com/ForceCLI/force/master/README.md>
- <https://raw.githubusercontent.com/ForceCLI/force/master/docs/force.md>


## Security Notes

No matching local secret-handling manifest was found for forcecli. Nucleus package metadata is still published here so future coverage has a stable package URL.


## Other Package-Manager Records

- Scoop - main/force: installed executable or alias match | Scoop official bucket manifest trees: bucket/force.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/forcecli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/forcecli.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph