How VectorForce Works — Git for AI Engineering Context
Keep your coding agents' goals, constraints, decisions, and Git evidence in sync across machines and AI harnesses (Antigravity, Claude Code, Cursor, Windsurf, Codex, Copilot, Meta Muse, Kiro) with zero-knowledge end-to-end encryption.
vf)
Zero-dependency CLI captures immutable checkpoints (claims + Git SHA + SHA-256 doc digests) in .vectorforce/.
vf mcp)
11 MCP tools let any AI IDE read briefings, check workspace drift, reason over context, and save checkpoints.
AES-256-GCM + X25519/Ed25519 sync across computers, fine-grained RBAC & scoped API tokens, and tamper-evident audit logs.
docs.vectorforce.in)
Step-by-step harness setup, CLI commands, MCP specs, and REST API endpoints.
npm i -g vectorforce && vf init && vf login --url https://cloud.vectorforce.in && vf push
Sign in / Create Account
Create New ProjectOrg Admin / Owner
New projects start in non-breaking Monitor governance mode.
Engineering Tasks
Read-onlyExecutive Stakeholder Digest
Cryptographic Evidence Ledger
Separates unverifiable AI claims from verified Git SHAs, Ed25519 signatures, and governance compliance verdicts.
AI Coding Governance Policies
Evaluated server-side on every sync/push before context is persisted.
Recent Policy Violations & Flags
Workspace & Role Summary
Members & Role Assignments
Read-onlyRole × Permission Governance Matrix
Authoritative server matrix enforced by authorize() across every API route. Last-owner demotion/removal and privilege escalation are blocked server-side.
Scoped Access Tokens (CLI / CI)
Token permissions are strictly bounded by the intersection of the creator's role and the token scope.
Active & Revoked Tokens
API Key / Platform Key Override (Testing)
Connected Machines & 1:1 E2EE Pairs
Read-onlyRegister 1:1 Machine Pair
Free plan allows 1 registered pair per project (Computer A → Computer B).
Tamper-Evident Audit Log (SHA-256 Chain)
Every login, token event, role update, policy change, push, pull, and denied action is cryptographically hash-chained.