vn

vn is the command line client for Venture Network, the GT MBA venture directory. It signs you in, keeps your profile and organization memberships up to date, and searches the member directory from your terminal.

Install

npm install -g @venturenetwork/cli

Node 22 or newer is required.

First steps

The CLI defaults to http://localhost:3000, a local dev server, so sign in with the production API URL explicitly:

vn login --api-url https://venturenetwork.ai   # opens the browser, stores the URL and your session
vn whoami                                       # confirms who you are signed in as

--api-url only needs to be passed once. It is saved to your config, so a later plain vn login reuses it.

Run vn --help for the full command list.

Intros and notifications

| Command | What it does | |---|---| | vn intros list | The intro requests you received. Add --sent for the ones you asked for. | | vn intros show <id> | One intro, with the message and, once accepted, both email addresses. | | vn intros request --to <handle> --message "..." | Ask a member for an intro. Use --post <id> or --event <id> in place of --to to ask from an ask or an event. | | vn intros accept <id> / vn intros decline <id> | Answer an intro request you received. | | vn notifications list | Your notification inbox. Add --unread for just the new ones. | | vn notifications read [id...] | Mark notifications read. With no ids, marks every one of yours read. |

Projects

A project is a venture team, and the team owns it. Its leads run everything: fields, visibility, archive, delete, and the roster. A network project can be found and read by any signed-in member. A private one shows only to its team and to the owners and admins of organizations it has a pending or active affiliation with. Every project is addressed by its id, which create, mine, and search print.

| Command | What it does | |---|---| | vn projects create --name "..." | Start a project. You are seated as its lead and the id is printed. Add --summary, --description, --stage idea\|validating\|building\|launched, or --visibility network\|private (default network). | | vn projects show <id> | One project with its visibility, active affiliations (org, kind, cohort), and roster. | | vn projects update <id> | Edit --name, --summary, --description, --stage, or --visibility, or archive it with --status archived and reopen it with --status active. | | vn projects delete <id> | Delete a project, its roster, and its affiliation history. | | vn projects assign <id> <handle> | Put any member on the roster, or change their --role lead\|member and --title. | | vn projects unassign <id> <handle> | Take someone off the roster. Your own handle leaves the project. The last lead cannot leave or be removed. | | vn projects mine | The projects you are on. --status active\|archived\|all (default active), --limit, --cursor. | | vn projects search <query> | Network projects whose name matches, for example to find one to invite. --limit, --cursor. | | vn projects list <org> | The projects affiliated with an org, with the kind and cohort of each. Takes the same --status, --limit, and --cursor as mine. |

Affiliations

An organization affiliates with a project rather than owning it. A project can hold several affiliations at once, and ended ones stay as history. The kind is community (a club or network), program (an accelerator or cohort), or investor (a funder or stakeholder). Either side can ask, and the other side decides. The team side is a lead of the project or a network admin. The org side is an owner or admin of the organization.

| Command | What it does | |---|---| | vn projects affiliate <id> <org> --kind <kind> | The team asks an org, with an optional --message. The org has to be public or one you belong to. Prints the affiliation id. | | vn projects invite <org> <id> --kind <kind> | The org invites a project, with an optional --message. Prints the affiliation id. | | vn projects affiliations <id> | A project's affiliations. Each side sees every status, other readers active ones only. --status, --limit, --cursor. | | vn projects requests <org> | An org's affiliations with who initiated each and, for the org side, how many of the team are not yet in the org. --status pending\|active\|declined\|cancelled\|ended (default every status), --limit, --cursor. | | vn projects accept <affiliation> | The side that did not ask accepts. Accepting for the org also invites the team members who are not yet in it and prints who was invited and who was skipped. Pass --no-invite-team to leave that out. | | vn projects decline <affiliation> | The side that did not ask declines. | | vn projects cancel <affiliation> | The side that asked withdraws a pending affiliation. | | vn projects end <affiliation> | Either side ends an active affiliation. | | vn projects cohort <affiliation> <label> | The org side sets a cohort label such as "Spring 2027". Pass "" to clear it. | | vn projects terms <affiliation> | Print the private deal terms. Only the project's leads, network admins, and the org's owners and admins can see them. --set "..." or --file <path> replaces them. | | vn projects invite-team <affiliation> | The org side invites the team to the org while the affiliation is active. Nobody joins until they accept their own invitation. |

Every command accepts --json.

Staying current

vn update

Source

https://github.com/GTMBA/venture-network