JSPM

  • Created
  • Published
  • Downloads 88
  • Score
    100M100P100Q122840F
  • License Apache-2.0

Command line interface for Vector workspaces.

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@rehpic/vcli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    Vector

    CLI for interacting with a Vector workspace from the terminal.

    This package wraps the same auth and Convex-backed workflows used by the app, so you can manage orgs, roles, teams, projects, issues, documents, notifications, and admin settings without opening the UI.

    Install

    npm install -g @rehpic/vcli
    yarn global add @rehpic/vcli
    pnpm add -g @rehpic/vcli
    bun add -g @rehpic/vcli

    Then verify the install:

    vcli --help

    Requirements

    • Node.js >=20.19.0
    • A running Vector app
    • Access to the app's Convex deployment

    The CLI talks to:

    • the Next.js app for auth routes
    • the Convex deployment for queries, mutations, and actions

    The app URL is required. vcli resolves it from:

    • --app-url <url>
    • the saved profile session
    • NEXT_PUBLIC_APP_URL

    The Convex URL resolves from:

    • --convex-url <url>
    • the saved profile session
    • the app's /api/config endpoint
    • NEXT_PUBLIC_CONVEX_URL or CONVEX_URL as local fallbacks when the app reports the default local URL

    You can override either with flags:

    vcli --app-url http://localhost:3000 --convex-url https://<deployment>.convex.cloud --help

    First Run

    Sign up or log in:

    vcli --app-url http://localhost:3000 auth signup --email you@example.com --username you --password 'secret'
    vcli --app-url http://localhost:3000 auth login you@example.com --password 'secret'
    vcli auth whoami

    Create and select an org:

    vcli org create --name "Acme" --slug acme
    vcli org use acme

    From there, most commands can rely on the active org. You can always override it with --org <slug>.

    Profiles

    Sessions are stored per profile in:

    ~/.vector/cli-<profile>.json

    Examples:

    vcli --profile work auth login you@example.com --password 'secret'
    vcli --profile staging --app-url http://localhost:3001 auth whoami

    Use profiles when you work across multiple environments or accounts.

    Common Commands

    Inspect the current session:

    vcli auth whoami
    vcli org current
    vcli org members acme

    Discover workspace metadata before mutating:

    vcli refdata acme
    vcli search --org acme "billing"
    vcli permission check issue:create --org acme

    Create core entities:

    vcli team create --org acme --key eng --name "Engineering"
    vcli project create --org acme --key api --name "API" --team eng
    vcli issue create --org acme --title "Ship CLI" --project api --team eng
    vcli document create --org acme --title "CLI Notes"
    vcli folder create --org acme --name "Runbooks"

    Issue workflows:

    vcli issue list --org acme
    vcli issue assignments API-1
    vcli issue set-priority API-1 High
    vcli issue replace-assignees API-1 "alice,bob"
    vcli issue comment API-1 --body "Investigating now."
    vcli issue link-github API-1 "https://github.com/acme/api/pull/123"

    Invites and notifications:

    vcli org invite acme --email teammate@example.com
    vcli invite list
    vcli invite accept <inviteId>
    vcli notification inbox --filter unread
    vcli notification unread-count

    Settings metadata:

    vcli priority list acme
    vcli state list acme
    vcli status list acme
    vcli role list acme

    Platform admin:

    vcli admin branding
    vcli admin signup-policy

    JSON Output

    Use --json for automation and scripts:

    vcli --json issue list --org acme
    vcli --json notification inbox --filter unread

    For scripts, prefer:

    • --json
    • --profile
    • --org

    Troubleshooting

    Not logged in

    • Run vcli auth login or vcli auth signup.

    app URL is required

    • Pass --app-url <url>, set NEXT_PUBLIC_APP_URL, or log in once with --app-url so the selected profile stores it.

    Organization slug is required

    • Pass --org <slug> or run vcli org use <slug>.

    Auth errors against the wrong app

    • Make sure --app-url points at the running Vector app origin.

    Convex connection errors

    • Make sure --app-url points at the right Vector app first, since vcli fetches the Convex URL from that app when possible.
    • Otherwise set --convex-url, NEXT_PUBLIC_CONVEX_URL, or CONVEX_URL.

    Validation errors when creating teams or projects

    • Use short slug-like keys such as eng, api, or mobile-platform.

    AI Agent Skill

    Install the Vector CLI skill for your AI coding agent:

    npx skills add xrehpicx/vector-skill

    Help

    Inspect command groups directly:

    vcli auth --help
    vcli org --help
    vcli issue --help
    vcli notification --help
    vcli admin --help