# How to install the DunSocial CLI

> Run npm install -g dunsocial, then use the dun command. Node.js 20 or newer is required & Bun isn't needed at runtime. You can also try it without installing via npx dunsocial. Upgrade with dun update.

Updated: 2026-10-05.

## What you need

The CLI is published to npm as `dunsocial` & installs a command called `dun`. It needs Node.js 20 or newer. Bun isn't required at runtime, even though the project itself is built with it.

## Install it

Use whichever package manager you already have:

```bash
npm install -g dunsocial
# or: bun add -g dunsocial
# or: pnpm add -g dunsocial
```

Then confirm it works:

```bash
dun --help
```

## Try it without installing

If you only want to look around, or you're in a throwaway environment, run it through npx:

```bash
npx dunsocial --help
```

That's also how most CI jobs run it, which is covered in the GitHub Actions article in this cluster.

## Check the version

```bash
dun --version
```

Knowing the version matters when you report a problem, & when you pin a version in CI so upgrades are deliberate.

DunSocial's CLI prints its version with a single flag, so quoting it in a bug report takes seconds.

## Keeping it up to date

Upgrade whenever you like:

```bash
dun update
# or just check: dun update --check
```

On a human terminal with a global install, DunSocial's CLI also upgrades itself after a successful command when a newer non-major version is on npm. Agents, CI, `--json` output & `npx` runs are never auto-updated.

## Turning auto-update off

Set `DUN_UPDATE=0` or pass `--no-update` if you want full control, for example on a shared machine or in a locked-down dev container.

Pinning a version in CI, such as `npx dunsocial@0.4.0`, is the safest option for pipelines, because a new release can't change behaviour under you.

DunSocial's CLI never auto-updates in CI, so pinning is about your own upgrade schedule rather than a guard against surprise changes.

## What to do next

Install is the easy part. The next step is signing in & picking a workspace, which takes a minute & is covered in the next article. After that, `dun accounts list` shows the account ids you'll use for every post.

Whatever you do from the CLI shows up on the same DunSocial calendar as the web app, so the two never drift apart.

## Related guides

- [How to sign in to the DunSocial CLI](https://www.dunsocial.com/hub/dunsocial-cli-guides/how-to-sign-in-to-the-dunsocial-cli.md)
- [How to schedule social media posts from the command line](https://www.dunsocial.com/hub/social-media-automation-for-developers/how-to-schedule-social-media-posts-from-the-command-line.md)
- [How to install DunSocial skills for coding agents](https://www.dunsocial.com/hub/dunsocial-cli-guides/how-to-install-dunsocial-skills-for-coding-agents.md)
- [CLI vs API vs MCP: which one should you use?](https://www.dunsocial.com/hub/social-media-automation-for-developers/cli-vs-api-vs-mcp-which-one-should-you-use.md)

## About this document

This is the Markdown representation of https://www.dunsocial.com/hub/dunsocial-cli-guides/how-to-install-the-dunsocial-cli. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login