The CLI

For users: vn is the command-line client for the Venture Network. It wraps the same API the web app and MCP server use, so a vn command sees exactly what you would see signed in on the web.

Install

npm install -g @venturenetwork/cli
# or: pnpm add -g @venturenetwork/cli
vn --version

@venturenetwork/cli is published to the public npm registry, so there is no registry configuration and no token to set up. Anyone can install it. Node 22 or newer is required.

vn --version prints something like @venturenetwork/cli/0.1.0+1bb84f3. The part after the plus sign is the commit the build came from, which is useful when reporting a problem. It plays no part in version comparison.

Signing in

vn login --api-url https://venturenetwork.ai
vn whoami

Pass --api-url on that first vn login. The CLI defaults to http://localhost:3000, a local dev server, so without the flag it will try to sign you in against a server that is not running. The URL is saved to your config, so a later plain vn login reuses it.

vn login runs the device flow. It opens your browser to approve the sign-in and stores the token in your OS config directory. Add --no-browser over SSH or in a headless environment, then open the printed URL yourself. vn whoami confirms who you are signed in as and shows your role.

Everyday commands

Command	What it does
`vn profile show` / `vn profile edit`	Read and edit your profile.
`vn profile avatar <file>`	Set your profile photo from a file, `--url <link>`, or `--from-linkedin`, or `--remove` it.
`vn orgs list` / `vn orgs show <slug>`	Browse organizations.
`vn orgs join <slug>`	Join or ask to join an organization.
`vn orgs members <slug>`	List an organization’s members.
`vn orgs logo <slug> <file>` / `vn orgs cover <slug> <file>`	Set an organization logo or cover photo (owners and admins) from a file or `--url <link>`, or `--remove` it.
`vn events cover <id> <file>`	Set an event’s cover image (the host, or the host org’s owners and admins) from a file or `--url <link>`, or `--remove` it.
`vn posts photo <id> <file>`	Set the photo on one of your posts from a file or `--url <link>`, or `--remove` it.
`vn members search`	Search the member directory.
`vn intros list` / `vn intros show <id>`	See intro requests you sent or received.
`vn intros request` / `vn intros accept <id>` / `vn intros decline <id>`	Ask for an intro, or answer one you received.
`vn notifications list` / `vn notifications read [id...]`	See your inbox, and mark one, several, or all of it read.
`vn health`	Check the API the CLI is pointed at.

Every command accepts --json, so a script or an agent can consume the output directly instead of parsing text.

Staying current

vn update

vn update asks the registry for the newest published version and installs it with whichever package manager installed vn, npm or pnpm. When you already have the newest one it prints vn 0.1.0 is already the newest version. and does nothing else.

Any other command prints a once-a-day notice on stderr when a newer version is out:

A newer vn is available (0.2.0, you have 0.1.0). Run vn update.

The notice stays quiet when you pass --json, when stdout is not a terminal (a pipe or a CI log), and for vn update itself, so it can never land in the middle of machine-read output. There is no environment variable to turn it off.

Building from a checkout

If you are contributing to the repo rather than installing the release, build and run the CLI in place:

pnpm install
pnpm nx run @venturenetwork/cli:build
node apps/cli/bin/run.js login

Wrap that last path in a small script on your PATH named vn if you use it often. A checkout build defaults to a local API. Point it at the live one with:

vn config set api-url https://venturenetwork.ai

See vn for the full command reference, generated from the CLI’s own manifest on every build.