# Vector

> Build reusable OpenCode configurations for teams and evaluate them.

## Start

- [Install Vector in an ESM project](https://vector.evil.kiwi/start/install): Add Vector to a Node.js 24 ESM project, then choose the package entrypoint for configuration building or behavioral evaluations.
- [Build and run your first Vector Configuration](https://vector.evil.kiwi/start/quickstart): Define a project-aware command, load its OpenCode Plugin Entrypoint, invoke it, and recover from common setup errors.
- [Understand Vector's configuration model](https://vector.evil.kiwi/start/concepts): Connect Configuration Packages, Vector Configurations, runtime values, reusable extensions, Snapshot preflight, and OpenCode registration.

## Build

- [Reuse extensions across configurations](https://vector.evil.kiwi/build/reuse): Define extensions independently, select them from Context, and reuse the same implementation across multiple Vector Configurations.
- [Add per-installation Runtime Configuration](https://vector.evil.kiwi/build/runtime-config): Validate global and project JSON with a Configuration Author-owned Standard Schema and use its typed output in Context.
- [Compute shared Context properties](https://vector.evil.kiwi/build/computed-context): Bind one synchronous computeContext callback to a builder and share its inferred Context across configurations and extensions.

## Activate

- [Package and load a Vector Configuration](https://vector.evil.kiwi/activate/package): Build an ESM Configuration Package, expose its OpenCode Plugin Entrypoint, publish it through your existing workflow, and connect it to a project.
- [Follow the activation lifecycle](https://vector.evil.kiwi/activate/lifecycle): Trace Runtime Configuration, Context, Extension Plan construction, Snapshot preflight, and sequential registration.
- [Troubleshoot activation failures](https://vector.evil.kiwi/activate/troubleshoot): Identify the failing activation seam, apply the documented recovery, and verify the configuration after reload.

## Evaluate

- [Run an Evaluation Suite](https://vector.evil.kiwi/evaluate/run-evals): Execute a Vector Configuration in a disposable Fixture and inspect normalized response and effect evidence with vitest-evals.
- [OpenCode Harness API reference](https://vector.evil.kiwi/evaluate/harness-api): Configure createOpenCodeHarness(), apply its option defaults, and interpret success, redaction, cleanup, and partial-run failures.

## API

- [defineVector() API reference](https://vector.evil.kiwi/api/define-vector): Define one Vector Configuration from its identity and a builder-bound Context callback that returns the complete Extension Plan for each activation.
- [createVectorBuilder() API reference](https://vector.evil.kiwi/api/create-vector-builder): Create a builder that binds inferred Runtime Configuration and computed Context types to every Vector definition and extension helper.
- [Extension helper API reference](https://vector.evil.kiwi/api/extensions): Look up the inputs, fixed identities, build callbacks, Snapshot relationships, and failure behavior of every specific defineX helper.
- [Context API reference](https://vector.evil.kiwi/api/context): Look up the base Context fields, ComputeContextInput, computed properties, sharing rules, and reserved-key boundary.
- [Runtime Configuration reference](https://vector.evil.kiwi/api/runtime-config): Look up the createVectorBuilder() runtimeConfig option, file paths, precedence, schema output, slug constraints, and failure behavior.

## Other

- [Build reusable OpenCode configurations](https://vector.evil.kiwi/): Define reusable OpenCode 2 configurations, activate them through ordinary ESM packages, and evaluate their behavior with Vector.