Public binaries and Claude Code plugin marketplace for the Remote.com partner API CLI.
This repository is generated by an automated release pipeline. Do not open pull requests here — source lives elsewhere.
One-line install (latest release):
curl -fsSL https://raw.githubusercontent.com/remoteoss/remote-cli/main/install.sh | shThis installs to ~/.local/bin/remotecli — a user-owned directory, so no
sudo is required. Make sure ~/.local/bin is on your PATH (the installer
prints a hint if it isn't):
export PATH="$HOME/.local/bin:$PATH" # add to your shell profile if neededInstall system-wide by pointing INSTALL_DIR at a shared directory. If it
isn't writable (e.g. /usr/local/bin), the installer prompts for sudo:
INSTALL_DIR="/usr/local/bin" \
sh -c "$(curl -fsSL https://raw.githubusercontent.com/remoteoss/remote-cli/main/install.sh)"Pin a version with VERSION (combine with INSTALL_DIR as needed):
VERSION=v1.2.0 \
sh -c "$(curl -fsSL https://raw.githubusercontent.com/remoteoss/remote-cli/main/install.sh)"Grab a binary from the latest release:
| Platform | Asset |
|---|---|
| macOS (Apple Silicon) | remotecli-darwin-arm64 |
| Linux (x86_64) | remotecli-linux-amd64 |
curl -fsSL -o remotecli \
https://github.com/remoteoss/remote-cli/releases/latest/download/remotecli-darwin-arm64
chmod +x remotecli
mv remotecli ~/.local/bin/ # a dir you own & on PATH; use /usr/local/bin (needs sudo) if you prefer
remotecli --versionVerify against SHA256SUMS from the same release if you care:
shasum -a 256 remotecli # compare against the published SHA256SUMSremotecli talks to the Remote.com partner API with a Bearer token. Released
binaries default to the production environment, so you just need to sign in.
Pick whichever fits:
Browser (OAuth2). Opens your browser, then saves the token to
~/.remote-cli/state.json; every later command uses it automatically:
remotecli loginAPI key. Paste a personal API key at a hidden prompt — the key is never shown, never written to your shell history, and never passed on the command line. It's saved to the same local state as the OAuth token, so later commands need no further input:
remotecli login --api-key
# headless / CI: read the key from a file (or - for stdin) instead of the prompt
remotecli login --api-key --api-key-file ./key.txtAn API key is used as-is and is not auto-refreshed — when it stops working,
re-run remotecli login --api-key.
Per-command token. Skip the saved session and pass any Bearer token (an OAuth access token or an API key) directly. This is the only method that puts the token on the command line:
remotecli employments list --company-token <token>Once signed in, remotecli me shows who you're authenticated as.
This repository is also a Claude Code plugin marketplace:
/plugin marketplace add remoteoss/remote-cli
/plugin install remote-cli@remote-cli
/reload-plugins
After installing, two Claude Code skills become available:
remote-cli— drives theremoteclibinary to perform HR actions (hire someone, list time off, approve expenses, …).remote-api-builder— guides building your own client (Python, TypeScript, etc.) against the Remote.com partner API, usingremoteclias a self-documenting executable spec.
The same two skills are bundled inside remotecli itself, so you can install
them without the plugin marketplace — handy if you installed the binary via
install.sh, or you use an agent other than Claude Code:
remotecli skills list # show the bundled skills
remotecli skills install # install both to ~/.claude/skills
remotecli skills install --project # install into ./.claude/skills (this repo)
remotecli skills install --dir PATH # install into any directory (e.g. another agent's skills dir)Re-running install overwrites the installed copy with the version bundled in
your current binary; add --dry-run to preview without writing. The command
needs no authentication.
Current release: v0.1.3
See the Releases page for history.