Does basecamp auto-invoke its skills?

Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.

Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

Productivity

Plugin

basecamp

basecamp is the official command-line interface for Basecamp. Manage projects, todos, messages, and more from your terminal or through AI agents.

Boost this plugin

basecamp@basecamp

GitHub

Plugin Signal75/100Solid

maintained99

capable43

documented100

adopted52

Install

$ npx -y skills add basecamp/basecamp-cli --agent claude-code

Stats

Bash PowerShell Linux Git GitHub

+3 tags

Anthropic Gemini MCP

277

Stars

Forks

Active

Maintenance

Language

MIT

License

2h ago

Last commit

8mo ago

Created

Repo: basecamp/basecamp-cli

In this plugin

4 hooks 3 skills

See everything inside

What's inside

Basecamp CLI

basecamp is the official command-line interface for Basecamp. Manage projects, todos, messages, and more from your terminal or through AI agents.

Works standalone or with any AI agent (Claude, Codex, Grok, Copilot, Gemini)
JSON output with breadcrumbs for easy navigation
OAuth authentication with automatic token refresh
Includes agent skills plus native Claude Code and Codex plugins; Grok Build reads the shared skill directly

Quick Start

macOS / Linux / WSL2

curl -fsSL https://basecamp.com/install-cli | bash

Windows (PowerShell)

irm https://raw.githubusercontent.com/basecamp/basecamp-cli/main/scripts/install.ps1 | iex

On Windows 11 with Smart App Control, see Troubleshooting if the install is blocked.

On an interactive terminal, the installer opens Basecamp setup: approve OAuth in your browser and the CLI uses the account granted by OAuth, otherwise preserves an existing account or selects the first available. It saves that account globally, clears the global project default, and connects every detected coding agent. Directory-specific and environment project settings continue to apply. Use basecamp setup --customize to choose those settings instead.

Brew / macOS

brew install --cask basecamp/tap/basecamp-cli

Arch Linux / Omarchy (AUR):

yay -S basecamp-cli

Linux (deb/rpm/apk):

# Download from https://github.com/basecamp/basecamp-cli/releases/latest
sudo apt install ./basecamp-cli_*_linux_amd64.deb            # Debian/Ubuntu
sudo dnf install ./basecamp-cli_*_linux_amd64.rpm            # Fedora/RHEL
sudo apk add --allow-untrusted ./basecamp-cli_*_linux_amd64.apk  # Alpine

Arm64: substitute arm64 for amd64 in the filename. Verify the SHA-256 checksum from checksums.txt before installing unsigned Alpine packages.

Scoop (Windows):

scoop bucket add basecamp https://github.com/basecamp/homebrew-tap
scoop install basecamp-cli

Shell script (macOS / Linux / WSL2 / Git Bash):

curl -fsSL https://raw.githubusercontent.com/basecamp/basecamp-cli/main/scripts/install.sh | bash

Nix:

nix profile install github:basecamp/basecamp-cli

Go install:

go install github.com/basecamp/basecamp-cli/cmd/basecamp@latest

mise:

mise use --global github:basecamp/basecamp-cli@latest

GitHub Release: download from Releases.

Upgrading

basecamp upgrade

What happens depends on how the CLI was installed:

Installer script / tarball (a binary under your home directory, e.g. ~/bin or ~/.local/bin): upgrades in place. The CLI downloads the release for your platform, verifies its Sigstore signature (the keyless checksums.txt.bundle published by the release pipeline, identity-pinned to the release workflow and tag) and SHA-256 checksum, swaps the executable transactionally, and confirms the installed binary reports the new version. On failure the previous binary is restored; in the worst case — restoration itself fails mid-swap — the error names the preserved backup file next to the binary so you can put it back by hand.
Homebrew / Scoop: delegates to brew upgrade --cask / scoop update, then verifies the manager-installed binary actually reports the new version.
System packages (apt/dnf/apk, AUR, Nix), mise, and go install builds: never touched. basecamp upgrade exits nonzero with upgrade guidance for that install method (the exact command where it can be known, e.g. mise or go install; otherwise which package manager to use).

basecamp upgrade exits 0 only when there is no update, or the update was applied and confirmed. Every other outcome is a structured failure ("ok": false in JSON) with one of these codes:

Code	Meaning
`upgrade_required`	An update exists but the CLI won't apply it for this install method — the hint carries the right next step
`upgrade_incomplete`	The package manager exited 0 but the binary still reports the old version
`upgrade_unverified`	The upgrade may have worked, but the installed version could not be confirmed
`upgrade_failed`	The update check, download, signature/checksum verification, or executable swap failed — the previous binary remains installed (or the error names the preserved backup if restoration also failed)

The install scripts verify release signatures when cosign is available: cosign v3 verifies the published bundle format as-is, v2.6+ is driven with --new-bundle-format=true, and older versions skip signature verification with a warning (SHA-256 checksums are always verified).

First-time setup

The first interactive basecamp run applies the recommended setup automatically after browser approval:

Account granted by OAuth, otherwise the existing configured account or first available account, saved globally
No global default project; directory-specific and environment project settings continue to apply
Every detected Claude Code, Codex or Grok integration

Run the same setup directly with basecamp setup. To choose the account, default project, config scope, and agent integrations, run:

basecamp setup --customize

Usage

basecamp projects list                            # List projects
basecamp todos list --in 12345                    # Todos in a project
basecamp todos create "Fix bug" --in 12345        # Create todo
basecamp todos complete 67890                     # Complete todo
basecamp cards done 67890 --in 12345              # Complete card (move to Done)
basecamp search "authentication"                  # Search across projects
basecamp files list --in 12345                    # List docs & files
basecamp cards list --in 12345                    # List cards (Kanban)
basecamp chat post "Hello" --in 12345             # Post to chat
basecamp comments create 67890 "@Jane.Smith, done!"    # Comment with @mention

Output Formats

basecamp projects              # Styled output in terminal, JSON when piped
basecamp projects --json       # JSON with envelope and breadcrumbs
basecamp projects --quiet      # Raw JSON data only

JSON Envelope

Every command supports --json for structured output:

{
  "ok": true,
  "data": [...],
  "summary": "5 projects",
  "breadcrumbs": [{"action": "show", "cmd": "basecamp projects show <id>"}]
}

Breadcrumbs suggest next commands, making it easy for humans and agents to navigate.

Errors use the same envelope with ok: false, a stable code, and retryable, which says whether a retry can change the outcome:

{
  "ok": false,
  "error": "Gateway error (503)",
  "code": "api_error",
  "retryable": true,
  "hint": "..."
}

Key order within the envelope is not part of the contract — the interactive (TTY) path re-encodes through a map and alphabetizes keys — so match on key names, never on position.

retryable is present on every error envelope — true when the CLI classified the failure transient (network, timeout, rate limit, circuit open, and most 5xx/gateway responses — not all: 507 and some 500s are verdicts), false for a verdict (usage, not found, auth, forbidden, validation, account limit) and for any error nothing classified — and never on a success envelope. Key on it rather than on the code or message when deciding whether to retry; false means no known reason a retry would help, not a guarantee the failure is permanent.

Authentication

OAuth 2.1 with automatic token refresh. First login opens your browser. When the server advertises the OAuth device flow, login uses it automatically: you approve a short code in the browser instead of a redirect. Login falls back to Launchpad's authorization-code flow only when no modern OAuth issuer is advertised for the server; once a modern issuer is selected, login failures surface loudly rather than silently falling back.

basecamp auth login              # Authenticate with Basecamp (full access)
basecamp auth login --scope read # Read-only access (ignored by Launchpad)
basecamp auth login --scope full # Full read+write access (default; ignored by Launchpad)
basecamp auth token              # Print token for scripts

--expect-identity <id> makes any login assert who it authenticated as: the new credential is checked before it is stored, and on a mismatch nothing is written (a profile's previous credential is untouched) and the command exits non-zero. basecamp profile create <name> --expect-identity <id> does the same for a profile that does not exist yet. --login-hint <email> names the account to sign in as on the device-flow approval page (sent as login_hint; it steers the sign-in page and never authenticates on its own; ignored by Launchpad).

Personal access tokens

A personal access token can be imported instead of running OAuth — the shape for bots, CI, and any machine that should never sign in interactively. The token is read from stdin (never an argument), verified against the server — who it authenticates as, and that it can reach the profile's account — and only then stored under a named profile, with whatever expiry the server reports for it:

op read "op://Vault/Item/credential" | basecamp auth login --with-token -P bot --account 999
op read "op://Vault/Item/credential" | basecamp auth login --with-token -P bot --account 999 --expect-identity 12345 --json

--account is required when the profile does not exist yet. --json returns an envelope with the profile, account, identity and person, oauth_type, scope, and expires_at (the expiry the server reports for the token, or null when it reports none). A token has no refresh token, so near a reported expiry the CLI refuses it and asks for a fresh import.

Agents

A Basecamp agent is a principal with no person behind it, so it has no browser to sign in with and is granted no refresh token. It authenticates with the OAuth client_credentials grant instead: its client id and secret mint a short-lived self-token, and the CLI mints another whenever that one nears expiry. The client secret is read from stdin (never an argument) and stored with the token it mints — in the OS keyring where one is available — because the client, not a refresh token, is what survives an expiry:

op read "op://Vault/Item/credential" | basecamp auth login --with-client-credentials --client-id <id> -P agent --account 999

The login mints once, which is what proves the client id and secret: a refused mint stores nothing. --account is required when the profile does not exist yet. basecamp auth logout forgets the credential; there is no useful revocation, since the same client would mint another — rotate the client secret in Basecamp to end an agent's access.

Multiple Identities

Use named profiles when the same machine or agent gateway needs more than one Basecamp identity. Each profile has its own stored OAuth credentials and can be selected per command:

basecamp profile create design-agent
basecamp profile create ops-agent
basecamp --profile design-agent todo "Fix bug" --in 12345 --list 67890

Set a default with basecamp profile set-default <name>, or set BASECAMP_PROFILE=<name> for a process. Actions are posted as the authenticated user for the selected profile.

Custom OAuth Credentials

To use your own OAuth app (e.g., a custom Launchpad integration):

Variable	Purpose
`BASECAMP_OAUTH_CLIENT_ID`	OAuth client ID
`BASECAMP_OAUTH_CLIENT_SECRET`	OAuth client secret

File tree

More plugins by @basecamp.

View @basecamp’s profile

HotVerifiedPlugin

Operations Linux

omarchy

Omarchy is a beautiful, fun & agentic Linux distribution by DHH. Read more at omarchy.org.

2 skills+143k

@basecamp

View Plugin

FAQ

basecamp is a Claude Code plugin with 3 hand-picked skills for productivity work, indexed on Flowy. Install it with the command on its page. It includes basecamp-connect, basecamp-doctor, basecamp. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.

What is basecamp?: basecamp is the official command-line interface for Basecamp. Manage projects, todos, messages, and more from your terminal or through AI agents.
How do I install basecamp?: Run these in Claude Code: npx -y skills add basecamp/basecamp-cli --agent claude-code. Then prompt normally.
Does basecamp auto-invoke its skills?: Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
Is basecamp free?: Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

Is this plugin yours?

Claim it with GitHub Submit a plugin Promote it