Always Click Yes (acy) — VS Code extension

Supervise a long-running Claude Code task from VS Code: plan it, arm it, and let acy approve each permission prompt after a short, interruptible countdown. The extension launches acy's TUI in an integrated terminal — same UI, same keys, one supervisor per window.

Commands

The ▶ acy status-bar item asks which of the two you want. If a supervisor terminal is already alive, Plan & Run reveals it instead of launching a second one, and a panel that is already open for a folder is revealed rather than reopened — one supervisor per project, either way.

The panel, and why it is not the default

ACY: Open Panel starts acy serve: the identical supervisor — same gate, same countdown, same dispatched children — with no terminal, exposed over HTTP on 127.0.0.1 behind a per-run bearer token, which a webview then renders. It is fully wired but deliberately unstyled: the visual design is still to come, so it looks like a plain document and works like a real run. ACY: Plan & Run therefore still opens the terminal, and will keep doing so until acy.useTerminal is turned off — which you can do today if you would rather live in the panel.

The panel owns its supervisor: closing the tab stops the run, and so does closing the window. acy serve's stderr goes to the acy output channel, which is where a panel that will not start explains itself.

Configuration

Run settings live in the project's .acy.json, not in flags and not in VS Code settings — the same file a terminal acy run reads, so the CLI and the extension can never disagree. Editing it gets IntelliSense from the bundled schema. Example:

{
  "model": "opus",
  "countdown": "20s",
  "maxLines": 15
}

Extension settings cover only what can't live in the project file:

• acy.binaryPath — where the acy binary is. Leave empty to use the binary bundled with a platform-specific build of this extension, or acy from your PATH.
• acy.defaults — seed values for ACY: Create .acy.json. Once the file exists, the file is the source of truth; these are never consulted at launch.
• acy.useTerminal — whether ACY: Plan & Run opens the TUI in a terminal (default) or the panel. ACY: Open Panel ignores it and always opens the panel.

Requirements

acy supervises a Claude Code session, so the claude CLI has to be installed. The extension looks for it in the project's .acy.json (claudeBin), then the acy.defaults.claudeBin setting, then your PATH, then the usual install directories (~/.local/bin, ~/.claude/local, Homebrew, %APPDATA%\npm) — a GUI-launched VS Code inherits the login environment rather than a shell's, so claude is routinely off PATH even when it works fine in your terminal. If none of those hit you get a warning at startup, not a run that dies on its first turn.

Install

Install Always Click Yes (acy) from the VS Code Marketplace — search for it in the Extensions view, or ext install hweeks.always-click-yes. VS Code picks the package built for your platform, so the acy binary comes with it. (The listing goes live with the first release published from CI.)

Or grab a .vsix from the latest release and install it via Extensions: Install from VSIX…. The platform-specific packages (darwin-arm64, darwin-x64, linux-x64, linux-arm64, win32-x64 — the last experimental) bundle the acy binary; the universal package expects acy on your PATH or acy.binaryPath set.

What you're opting into

acy is an experiment in total trust: you make contact at the plan and at the end, and in between the machine runs unattended, approving its own way to the finish. Read the project README before leaving it alone with anything you love. The veto key is Ctrl+X.

License

WTFPL v2 — you just do what the fuck you want to.