Skip to content

windows.md

Latest commit

 

History

History
executable file
·
58 lines (45 loc) · 2.69 KB

windows.md

File metadata and controls

executable file
·
58 lines (45 loc) · 2.69 KB
Raw

Windows setup

  1. Put the kit in the synced folder you intend to keep.
  2. In File Explorer, right-click the whole kit and select Always keep on this device.
  3. Open PowerShell in the kit and run:
Set-ExecutionPolicy -Scope Process Bypass
.\bin\install-windows.ps1 -AddToUserPath

The installer creates directory junctions for generated agents and the Skill. Junctions track future renders without requiring the same OneDrive path on every machine.

%USERPROFILE%\.claude\agents\delekit
%USERPROFILE%\.claude\skills\orchestrate-delegates
%USERPROFILE%\bin\claudex.cmd
%LOCALAPPDATA%\delekit\device.env
%LOCALAPPDATA%\delekit\claude-profile

The isolated profile's skills directory junctions to the normal Claude skills directory. The 272k ccg profile therefore sees the same shared and delekit skills as ordinary Claude, including skills added later.

With -AddToUserPath, the installer also adds the synced delekit\bin directory to the user PATH. This exposes ccg.cmd directly in both PowerShell and cmd.exe; its implementation remains in the synced kit and cannot drift between shell profiles.

Populate only the local device.env, including DELEGATE_PARENT_MODEL. The launcher keeps the parent model runtime-selected — an explicit --model always wins — but without that pin a /model pick inside a gateway session writes a gateway-only alias into the global settings file and breaks every non-gateway launch. See known-issues.md. Apart from that the launcher applies the same gateway compatibility defaults as macOS.

The default 272k Tandy mode uses the dedicated claude-profile above, requires ANTHROPIC_AUTH_TOKEN, and leaves the ordinary Claude profile untouched. DELEKIT_TANDY_CONTEXT_MODE=native-200k is the explicit compatibility fallback. Revalidate the same-agent compaction transcript after every Claude Code update.

Older profile-based installs may dot-source bin\ccg-snippet.ps1, but new Windows installs should use the PATH command installed above. Leave the direct Claude launcher available and pin it to its own model for the same reason.

To run the proxy at login, put a one-line hidden launcher in the Startup folder (shell:startup). Build the command with Chr(34) for quoting; nested doubled quotes fail to parse. macOS uses bin/install-launchd-macos.sh instead.

Open a new terminal after adding the user PATH, then run:

.\bin\doctor-windows.ps1

Execution policy, enterprise controls, filesystem type, or OneDrive status may block junctions or scripts. Do not globally weaken policy. Use -Copy or obtain approval for the narrow local change. Copied generated files must be reinstalled after future renders.