Skip to content

Local Installation

Pinix has two installation modes, depending on your use case:

Installation modeBest forWhat it installs
Full installationPeople who want to run Clips on this machinedaemon + CLI + browser engine + runtime
CLI-onlyPeople who want to invoke other people’s Clips remotelyOnly the pinix command-line tool

Typical setup: one server uses the full installation to run the daemon and Clips, while the rest of the team installs CLI-only on their own machines for remote invocation. Or, if you are already using the pinixai.com Cloud Agent, you can install only the CLI to invoke Clips from your terminal too.

macOSLinuxWindows
Full installationarm64 / amd64arm64 / amd64amd64
CLI-onlyarm64 / amd64arm64 / amd64amd64

Install the daemon and all dependencies to run Clips on this machine.

Terminal window
curl -fsSL dl.pinixai.com/install.sh | sh

Components installed automatically:

ComponentPurpose
pinixCLI + daemon (single binary)
Node.jsRuntime dependency (installed automatically if missing)
BunClip runtime for running TypeScript Clips
bb-browserBrowser automation Edge Clip

Chrome is downloaded automatically the first time the daemon starts.

  1. Start the daemon

    Terminal window
    pinix start

    The daemon starts on port :9000 and automatically launches Chrome and bb-browser.

  2. Log in

    Terminal window
    # 浏览器授权(会自动打开浏览器)
    pinix login
    # 或者用 token 登录(从 pinixai.com/settings 获取 token)
    pinix login --token pnx_...

    After login, the daemon automatically connects to the Cloud Hub. Your local Clips can be accessed from the cloud, and you can also use Clips shared by others.

  3. Start using Pinix

    Terminal window
    # 查看可用的 Clip
    pinix hub list
    # bb-browser 的平台 Clip 已自动注册
    pinix invoke hackernews top
    pinix invoke google search "pinix ai agent"
    # 安装更多 Clip
    pinix hub add @pinix/todo
    pinix invoke todo list
    # 打开本地 Console
    open http://localhost:9000

Install only the pinix command-line tool, without starting the daemon or installing runtimes. Use it to invoke Clips through the Cloud Hub or a remote daemon.

Terminal window
curl -fsSL dl.pinixai.com/install.sh | sh -s -- --cli

After installation, you need to log in. There are two ways:

Terminal window
pinix login

This prints a link and automatically opens your browser. Confirm authorization on the web page to finish.

After login, the CLI automatically connects to the Cloud Hub. You do not need to manually specify --server; use it directly:

Terminal window
# 查看所有可用的 Clip(你自己的 + 别人共享的)
pinix hub list
# 调用 Clip
pinix invoke todo list
pinix invoke hackernews top

If you do not want to go through the Cloud Hub, you can also connect directly to another machine’s daemon on the local network:

Terminal window
pinix --server http://192.168.1.100:9000 hub list
pinix --server http://192.168.1.100:9000 invoke todo list
CommandDescriptionRequires daemon
pinix startStart the daemon
pinix stopStop the daemon
pinix loginLog inNo
pinix whoamiCheck login statusNo
pinix hub listView the Clip listYes
pinix hub add @scope/nameInstall a ClipYes
pinix hub remove <alias>Uninstall a ClipYes
pinix hub update [alias]Update Clips to the latest versionYes
pinix hub info <alias>View Clip commands and parametersYes
pinix invoke <alias> <command>Invoke a ClipYes
pinix registry search <query>Search the RegistryNo
pinix upgradeUpgrade Pinix itselfNo

Requires Go 1.25+:

Terminal window
git clone https://github.com/epiral/pinix.git
cd pinix
make build

You also need to install Bun and bb-browser separately:

Terminal window
curl -fsSL https://bun.sh/install | bash
npm install -g bb-browser
Terminal window
# 更新单个 Clip 到最新版
pinix hub update todo
# 更新所有 Registry 安装的 Clip
pinix hub update --all
# 更新到指定版本
pinix hub update todo --version 1.2.0
Terminal window
pinix upgrade

This upgrades the Pinix binary itself and updates bb-browser. It does not affect installed Clips.