Local CLI · never edits the repo

One home.
Six projections.

Keep rules and MCP servers in ~/.vincra. Import from an agent, edit the plate, then sync the rest. Vincra stops if a target drifted.

pnpm add --global vincra@latest

Node 22.12+ · pnpm dlx vincra --help

Published package

v0.1.1

View on npm Source on GitHub

First run

Start with a clean handoff

01

Install the CLI

Use the published package globally, or try it once with no install.
02

Create the canonical home

Vincra creates ~/.vincra without replacing existing files.
03

Choose a source of truth

Import one agent once, then sync the canonical configuration everywhere else.

Tap a row to copy.

Coverage

AgentRulesMCP

CodexAutomaticAutomatic

Claude CodeAutomaticAutomatic

CursorManual pasteAutomatic

OpenCodeAutomaticAutomatic

Devin / WindsurfAutomaticAutomatic

PiAutomaticUnsupported

Cursor User Rules still require a paste through Cursor Settings > Rules. Pi has no documented global MCP schema.

Guardrails

Secrets stay outside the files. Use ${NAME} references and define the real value in your environment.

Drift stops a broad sync. Run vincra diff before deciding whether to import or sync.

Every risky write gets a backup. Use vincra doctor after syncing to verify the result.

Paste this into a coding model so it uses real Vincra commands instead of inventing flags.

Open /llms.txt

Keep reading