VectorCI Docs

GitHub-authenticated setup

Install once.
Prove every run.

VectorCI gives users and coding agents one guarded path to install, configure, and validate CI across private repositories—without copying credentials or treating local checks as production proof.

Install in a repository Set up an agent
repository
Project-local quick start 
npm install --save-dev --save-exact @orintech/vectorci@0.5.0
npx vectorci auth login
npx vectorci setup .
✓

Same pinned version
for humans, scripts, and agents.

GitHubidentity provider

macOS + Windowsnative clients

1 repoper CLI process

No tokensin CLI output

One workflow

From package install to exact-run proof.

Each stage has a distinct job. A plan is not a write, local validation is not a live run, and a passing check must belong to the VectorCI GitHub App.

  1. 01Install

    Pin the CLI in package.json and the lockfile.

  2. 02Plan

    Review the full candidate and SHA-256 digest.

  3. 03Apply

    Create only the missing configuration after confirmation.

  4. 04Doctor

    Prove the exact default-branch App-owned run.

Documentation

Everything needed to onboard a codebase.

01 Install VectorCI in a repository Add the official VectorCI CLI so humans, package scripts, and agents use the same reviewed version. 02 Authenticate with GitHub Use GitHub CLI web authentication and explicit GitHub App consent without copying tokens into VectorCI. 03 Set up one repository Plan a deterministic .vectorci.yml, review its digest, apply it once, and prove the exact default-branch run. 04 Keep product repositories isolated Run one pinned CLI inside each product repository without granting cross-repository access. 05 Give coding agents a safe VectorCI workflow Pin the CLI in the repository, tell agents which read-only commands to run first, and keep every write review-gated. 06 Understand .vectorci.yml Declare required capabilities and exact validation commands while VectorCI owns routing, credentials, cleanup, and check publication. 07 Validate configuration and prove readiness Keep local contract checks, GitHub identity, exact branch configuration, and live App-owned execution proof distinct. 08 Security model Use short-lived GitHub identities, bounded filesystem writes, exact capability routing, and separate privileged release paths.

Built for agents

Documentation is part of the interface.

The website, vectorci docs, llms.txt, and docs.json all come from one versioned topic catalog.

Agent setup guide