ApproveOnce for VS Code is a local approval-and-execution layer for AI-shaped work.
It now expects a signed founding-access token before the commands can run on a machine. Public install can stay open through the Marketplace; paid usage is gated by local entitlement activation rather than a hidden thank-you page.
It turns one bounded request into:
one structured plan
one reviewable plan hash
one one-time approval
one isolated local run
one proof pack
First Run
Activate founding access first with ApproveOnce: Enter Access Token.
Open a git-backed workspace. Safe mode currently requires a repository and blocks early if the folder is not under git yet.
Start with one bounded request in plain language or the explicit MVP grammar.
Good first prompts:
add one line to README.md saying "Approved once."
append "Approved once." to README.md
create file notes.txt with content hello
replace "old" with "new" in README.md
run command "npm test" in .
Commands
ApproveOnce: Enter Access Token
ApproveOnce: Show Access Status
ApproveOnce: Create Plan
ApproveOnce: Review Current Plan
ApproveOnce: Approve Once
ApproveOnce: Run Approved Plan
ApproveOnce: Apply Latest Result
ApproveOnce: Open Latest Proof
MVP Notes
The current MVP is intentionally narrow and deterministic.
Safe execution currently targets git-backed workspaces through an isolated local worktree.
Proof packs are written under .approveonce/runs/<run-id>/.
The isolated execution workspace is preserved for inspection after the run.
A successful isolated run can now be promoted back into the current workspace through Apply Latest Result.
Proof output distinguishes approved shell commands from internal runner setup so the result stays honest about what the user actually approved.
Paid access is intended to be delivered through a signed entitlement token tied to purchase proof, not through a public thank-you page.
