Veil for VS Code-compatible editors

This extension is a thin client for an independently installed, compatible Veil CLI. It supports VS Code, Cursor, and VSCodium-style hosts on macOS and Linux. It never installs the CLI, stores Codex credentials, or starts a daemon.

Install the exact same alpha version of @useveil-dev/cli first, then install the matching VSIX from the GitHub Release or a configured editor marketplace. The release manifest lists the CLI, VSIX, and Codex plugin checksums together. If the CLI has not been published to npm yet, build it from a repository checkout; then run npm install --global ./apps/cli from that checkout and verify command -v veil. A shell alias is not visible to the extension process. Do not point the extension at a nonexistent installer or Cloud Connector.

An ordinary local clone keeps unpushed edits private. Veil adds an encrypted, local-first workspace, independent checks, and deliberate publication without requiring a public fork or intermediate public branch. Use Veil: Open Public GitHub Repository, paste a canonical public GitHub HTTPS URL, and choose an import parent folder. Veil performs the filtered clone and opens its managed workspace. Veil: Open Current Repository is also available for an already-clean local checkout whose HEAD is on its public origin.

Work begins in an Unassigned Change beside any declared concurrent Logical Changes. Name, create, focus, assign, split, combine, pause, resume, abandon, mark, restore, and reconcile them from the Command Palette, then work manually or with the Codex agent harness. Capture the current result, read its behavior-first review, verify it, and publish only after explicit confirmation. Draft-PR publication still requires repository access; exporting a patch remains the handoff when direct upstream publication is unavailable. The extension invokes one foreground veil rpc process per action and rehydrates authoritative encrypted state from Veil after reload.

The Command Palette exposes the same workflow as the CLI and Codex plugin:

• Context and work: Open Public GitHub Repository, Open Current Repository, Open Private Workspace, and Work with Codex
• Intent and review: Name/Show/Create/Focus Logical Change, Assign Work Fragments, Split/Combine, Pause, Resume, or Abandon, Mark/Restore Recovery Moment, Reconcile Published Logical Change, Show Status, Show Logs, Follow Run Logs, Checkpoint Workspace, Capture Workspace, Review Behavioral Changes, and Check Result
• Publication: Publish Draft PR and Export Patch
• Local state: Destroy Manual Workspace and Show Codex Status
• Website monitoring: Connect Website, Show Website Connection, Disconnect Website, Show Metrics Status, and Flush Metrics

Repository admission is language-neutral. Capture encrypts the current result and evaluates its pinned verification recipe when one is detected or configured. Built-in detection covers common Node, Python, Go, Rust, Java/Kotlin, Ruby, PHP, and .NET layouts; veil.verify.json supports any other language or build system. Veil: Review Behavioral Changes displays structural behavioral sections bound to exact evidence. TypeScript/JavaScript program-flow coverage is labeled complete, partial, or unsupported with reasons. When no recipe exists, Veil: Check Result reports the result as unchecked instead of claiming repository tests ran. A configured recipe can instead report verified, failed, or unavailable according to its gates and toolchain.

The web companion is optional. The extension talks only to the local CLI and does not receive browser sessions, OpenAI credentials, marketplace tokens, or Veil billing data.

Each action is attributed to the vscode surface by the CLI's shared bounded metrics collector. The extension does not implement a telemetry client and never receives a website access token. Once the user connects veil auth, the CLI uploader may report the same allowlisted operational evidence used by the CLI, MCP server, and Codex plugin.