[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"pack-detail-windows-engineer-ai-stack-en":3,"seo:pack:windows-engineer-ai-stack:en":96},{"code":4,"message":5,"data":6},200,"操作成功",{"pack":7},{"slug":8,"icon":9,"tone":10,"status":11,"status_label":12,"title":13,"description":14,"items":15,"install_cmd":95},"windows-engineer-ai-stack","🪟","#0078D4","new","New · this week","Windows Engineer's AI Stack","Ten picks for developers on Windows 10\u002F11 who want an AI-powered setup: WinGet + Scoop for installs, Windows Terminal + WSL for shells, PowerToys + GlazeWM for window control, AutoHotkey + Espanso for automation, Windows-MCP so agents can drive the desktop. Native-Windows-first, not warmed-over Mac advice.",[16,28,36,43,50,57,64,71,78,85],{"id":17,"uuid":18,"slug":19,"title":20,"description":21,"author_name":22,"view_count":23,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3491,"c3c11cdc-4e82-11f1-9bc6-00163e2b0d79","winget-windows-package-manager-microsoft-c3c11cdc","WinGet — Windows Package Manager by Microsoft","WinGet is the official Windows Package Manager CLI from Microsoft. It lets you discover, install, upgrade, remove, and configure applications from the command line using a curated repository of thousands of packages.","AI Open Source",94,0,"en","skill","Skill",{"id":29,"uuid":30,"slug":31,"title":32,"description":33,"author_name":34,"view_count":35,"vote_count":24,"lang_type":25,"type":26,"type_label":27},3492,"dbb25df1-4e82-11f1-9bc6-00163e2b0d79","scoop-command-line-installer-windows-developer-tools-dbb25df1","Scoop — Command-Line Installer for Windows Developer Tools","Scoop is a command-line installer for Windows that focuses on developer tools. It installs programs to your home directory by default, avoids UAC pop-ups, and keeps your PATH clean by shimming executables automatically.","Script Depot",49,{"id":37,"uuid":38,"slug":39,"title":40,"description":41,"author_name":34,"view_count":42,"vote_count":24,"lang_type":25,"type":26,"type_label":27},2745,"5eefbaec-4946-11f1-9bc6-00163e2b0d79","windows-terminal-modern-terminal-windows-microsoft-5eefbaec","Windows Terminal — The Modern Terminal for Windows by Microsoft","A GPU-accelerated terminal application for Windows that supports tabs, panes, Unicode, UTF-8, custom themes, and multiple shell profiles including PowerShell, CMD, and WSL.",89,{"id":44,"uuid":45,"slug":46,"title":47,"description":48,"author_name":34,"view_count":49,"vote_count":24,"lang_type":25,"type":26,"type_label":27},1102,"290af8f3-3641-11f1-9bc6-00163e2b0d79","wezterm-gpu-accelerated-terminal-emulator-multiplexer-290af8f3","WezTerm — GPU-Accelerated Terminal Emulator and Multiplexer","WezTerm is a GPU-accelerated cross-platform terminal emulator and multiplexer written in Rust. Configured entirely in Lua with built-in tabs, splits, SSH multiplexing, image display, and a rich set of terminal features.",152,{"id":51,"uuid":52,"slug":53,"title":54,"description":55,"author_name":22,"view_count":56,"vote_count":24,"lang_type":25,"type":26,"type_label":27},4593,"cb4291cd-5446-11f1-9bc6-00163e2b0d79","powertoys-windows-productivity-utilities-microsoft-cb4291cd","PowerToys — Windows Productivity Utilities from Microsoft","PowerToys is a set of open-source system utilities for Windows power users that includes window management, file renaming, color picking, keyboard remapping, and more.",5,{"id":58,"uuid":59,"slug":60,"title":61,"description":62,"author_name":34,"view_count":63,"vote_count":24,"lang_type":25,"type":26,"type_label":27},4160,"8753dec0-522e-11f1-9bc6-00163e2b0d79","glazewm-tiling-window-manager-windows-inspired-i3-8753dec0","GlazeWM — Tiling Window Manager for Windows Inspired by i3","GlazeWM is a tiling window manager for Windows that brings i3-style keyboard-driven workflows to the Windows desktop. It features workspaces, configurable layouts, window gaps, a built-in status bar (Zebar), and simple YAML-based configuration with hot-reload support.",46,{"id":65,"uuid":66,"slug":67,"title":68,"description":69,"author_name":34,"view_count":70,"vote_count":24,"lang_type":25,"type":26,"type_label":27},2484,"d7a6fb8a-459b-11f1-9bc6-00163e2b0d79","powershell-cross-platform-automation-shell-microsoft-d7a6fb8a","PowerShell — Cross-Platform Automation Shell from Microsoft","PowerShell is a cross-platform task automation solution consisting of a command-line shell, a scripting language, and a configuration management framework that runs on Windows, Linux, and macOS.",92,{"id":72,"uuid":73,"slug":74,"title":75,"description":76,"author_name":34,"view_count":77,"vote_count":24,"lang_type":25,"type":26,"type_label":27},4600,"62279cf5-5447-11f1-9bc6-00163e2b0d79","autohotkey-desktop-automation-scripting-windows-62279cf5","AutoHotkey — Desktop Automation and Scripting for Windows","AutoHotkey is a free scripting language for Windows that lets you create hotkeys, remap keys, automate repetitive tasks, and build lightweight GUIs with minimal code.",11,{"id":79,"uuid":80,"slug":81,"title":82,"description":83,"author_name":22,"view_count":84,"vote_count":24,"lang_type":25,"type":26,"type_label":27},2686,"fbecf272-485a-11f1-9bc6-00163e2b0d79","espanso-cross-platform-text-expander-written-rust-fbecf272","Espanso — Cross-Platform Text Expander Written in Rust","Espanso is a privacy-first text expansion tool that detects trigger keywords as you type and replaces them with templates, scripts, or dynamic content—running locally on Linux, macOS, and Windows.",80,{"id":86,"uuid":87,"slug":88,"title":89,"description":90,"author_name":91,"view_count":92,"vote_count":24,"lang_type":25,"type":93,"type_label":94},3066,"55710c60-049b-403c-972c-926e7079b382","windows-mcp-windows-computer-use-mcp","Windows-MCP — Windows Computer-Use MCP","Windows-MCP is a Python MCP server for Windows 7–11 that lets agents control apps, UI, and files. Install from PyPI via uvx and add to Claude Code.","MCP Hub",71,"mcp","MCP","tokrepo install pack\u002Fwindows-engineer-ai-stack",{"pageType":97,"pageKey":8,"locale":25,"title":98,"metaDescription":99,"h1":100,"tldr":101,"bodyMarkdown":102,"faq":103,"schema":119,"internalLinks":124,"citations":137,"wordCount":150,"generatedAt":151},"pack","Windows Engineer's AI Stack — 10 Tools for an AI-Powered Win10\u002F11 Setup","WinGet, Scoop, Windows Terminal, WezTerm, PowerToys, GlazeWM, PowerShell, AutoHotkey, Espanso, Windows-MCP — a one-evening rig that turns a stock Win10\u002F11 box into a keyboard-driven, scriptable, agent-controllable workstation. Native-Windows-first, install order included.","Windows Engineer's AI Stack — A One-Evening Native-Windows Rig","Ten picks in deliberate order: package managers first, then terminal, then WSL, then window control, then automation, then an MCP server so AI agents can drive the desktop. By the second evening your shell, your windows, and your AI assistant all speak the same keyboard.","## What's in this pack\n\nThis is the rig a working engineer on **Windows 10 or 11** would build on a fresh box in one evening — not a Reddit thread of 40 random utilities. Every pick is **actively maintained**, **scriptable**, and **plays nicely with AI agents** (Claude Code, Cursor, Codex, Copilot — anything that can call a shell or an MCP server).\n\nThe pack is deliberately **Windows-native-first**. WSL shows up, but as a peer to PowerShell and Win32, not as a way to pretend you're on Linux. If the answer is \"just use macOS\", that's a different pack — this one is for engineers who chose Windows on purpose (gaming rig, work-issued laptop, Surface, Arm64 Snapdragon, GPU box) and want it to feel as automatable as a Unix workstation.\n\n## Install in this order\n\n1. **WinGet** — Microsoft's official package manager. Already shipped on Win10 1809+ and Win11. Start here because every later tool can be installed with `winget install --id \u003Cid>` and you'll want one canonical install path before you start scripting.\n2. **Scoop** — bucket-based portable installer. Complements WinGet rather than replacing it: Scoop excels at command-line developer tools (jq, ripgrep, fd, sd) that drop straight into `~\u002Fscoop\u002Fshims` with no admin prompt. Use WinGet for GUI apps, Scoop for CLI utilities.\n3. **Windows Terminal** — modern GPU-accelerated terminal with tabs, panes, profiles. This is where PowerShell, CMD, WSL, and SSH all live in one window. Bind a `Ctrl+\\`` global hotkey via `\"globals.keybindings\"` to summon it quickedrop-style — single biggest QoL win.\n4. **WezTerm** *(optional alt)* — GPU-accelerated terminal configured in Lua, with built-in SSH multiplexing and image protocols. Pick **either** Windows Terminal **or** WezTerm; only run both if you want WezTerm for SSH-heavy days and Windows Terminal for Windows-native sessions.\n5. **PowerShell 7** — cross-platform pwsh. Don't settle for the built-in `powershell.exe` (5.1, Windows-only, no module updates). `winget install Microsoft.PowerShell` gets you `pwsh`, which AI agents can invoke identically on Windows, Linux, and macOS.\n6. **PowerToys** — Microsoft's productivity utility suite. Turn on **PowerToys Run** (Alt+Space launcher), **FancyZones** (snap windows to a custom grid), **Keyboard Manager** (remap Caps Lock → Esc or Ctrl), and **Always On Top**. Don't turn on everything — pick the four above and ignore the rest until you miss them.\n7. **GlazeWM** — i3-style tiling window manager. Once you've used FancyZones for two weeks and gotten tired of dragging windows into zones, GlazeWM auto-tiles everything. Lives alongside PowerToys without conflict if you scope hotkeys cleanly (`Alt+1..9` for GlazeWM workspaces, `Win+arrow` for FancyZones snap).\n8. **AutoHotkey** — the Windows answer to Hammerspoon. Bind `CapsLock & j\u002Fk\u002Fl\u002F;` to arrow keys, build a Pomodoro HUD, fire a webhook on idle, glue anything to anything. AutoHotkey v2 is the version to learn (v1 syntax is being phased out).\n9. **Espanso** — Rust-based text expander. Type `:llm` and get a 200-word Claude prompt; type `:gpr` and get your git PR template. Cross-platform config in YAML, syncable via git. Lower learning curve than AutoHotkey for the 80% of cases where you just want \"type this when I type that\".\n10. **Windows-MCP** — Model Context Protocol server that lets agents control Windows apps, UI, and files. Install with `uvx windows-mcp` and wire it into Claude Code or Codex. This is the AI-stack tie-in: once your shell, windows, and clipboard are scripted, an MCP-aware agent can drive the whole rig.\n\n## How they fit together\n\n```\nWinGet ───────┐\n              ├─→ install everything else\nScoop ────────┘     (GUI via WinGet, CLI via Scoop)\n\nWindows Terminal  (or WezTerm)\n        │\n        ├─ tab: PowerShell 7 (pwsh)\n        ├─ tab: WSL 2 (Ubuntu \u002F Debian)\n        ├─ tab: CMD (rare, only for legacy .bat)\n        └─ tab: SSH to dev box \u002F GPU server\n\nPowerToys (PT Run, FancyZones, Keyboard Mgr)  ⟵  GlazeWM (auto-tile)\n        │                                              │\n        └─── both bound under Win+...  \u002F  Alt+... ────┘\n             (don't double-bind — pick one per hotkey)\n\nAutoHotkey  ──┐\n              ├─ glue layer: Hyper-style remaps, global hooks,\n              │  Pomodoro HUDs, screenshot pipelines, webhooks\nEspanso ──────┘     (Espanso for text expansion only,\n                     AHK for everything else)\n\nWindows-MCP (uvx)\n        │\n        └─→ Claude Code \u002F Codex \u002F Cursor — agent drives desktop\n            via screenshot + click + keyboard + file APIs\n```\n\nThe four-tool combo **Windows Terminal + PowerShell 7 + AutoHotkey + Windows-MCP** is the inflection point: at that moment your dev box stops feeling like \"Windows with tools bolted on\" and starts feeling like a single AI-driven workstation. Don't skip PowerShell 7 — without `pwsh`, every cross-platform script you copy from Claude has to be rewritten.\n\n## Tradeoffs you'll hit\n\n- **WSL 2 vs native Win32** — WSL 2 is fast, has real `apt`, and Linux dev workflows port over almost free. The catch: filesystem perf across the WSL ↔ Windows boundary is terrible (10-100x slower). Rule of thumb: code stays on the side where the tool runs. Node project? Keep it in `~\u002Fprojects\u002F` inside WSL, not in `\u002Fmnt\u002Fc\u002FUsers\u002F...`. C# \u002F .NET \u002F game dev? Stay native.\n- **WinGet vs Scoop vs Chocolatey** — WinGet ships with Windows, Scoop is best for CLI tools (no admin prompts), Chocolatey has the deepest catalog but heavier and admin-only. The pack picks WinGet+Scoop because together they cover ~98% of dev tools with zero admin nags for the CLI side.\n- **PowerToys FancyZones vs GlazeWM** — FancyZones is opt-in per drag (you choose when to snap). GlazeWM tiles automatically (every new window joins the layout). Run both: FancyZones for monitor-spanning code review zones, GlazeWM for tab-heavy workspaces.\n- **AutoHotkey vs PowerShell scripts** — AHK lives at the input layer (intercept Caps Lock, fire on hotkey, click coordinates). PowerShell lives at the process\u002Ffile layer (manage services, parse JSON, hit APIs). Don't use either for the other's job — AHK loops doing HTTP are painful; PowerShell hotkeys via `Register-EngineEvent` are flaky.\n- **Windows Terminal vs WezTerm** — Windows Terminal has the best Windows integration (notifications, jumplist, Quake mode). WezTerm has better SSH multiplexing, better font rendering on high-DPI, and Lua config. Most engineers default to Windows Terminal and keep WezTerm for SSH-heavy days. Pick one as default; don't agonize.\n\n## Common pitfalls\n\n- **WSL 2 filesystem perf** — `npm install` in `\u002Fmnt\u002Fc\u002F...` is 30x slower than in `~\u002F`. If your dev workflow feels broken, this is usually why. Move the repo into WSL's native ext4 partition.\n- **Path translation between WSL and Windows** — `wslpath -w ~\u002Ffile` converts a WSL path to `C:\\Users\\...\\file` for handoff to a Windows tool, and `wslpath -u` reverses it. Memorize these two; they save hours.\n- **AutoHotkey v1 vs v2 syntax** — almost every script on the open web is v1. Don't paste blindly into AHK v2 — syntax is different (`Send, foo` vs `Send(\"foo\")`). Pick v2 for new scripts; convert old ones with the official v1-to-v2 converter.\n- **PowerToys auto-update breaking GlazeWM hotkeys** — every PowerToys update can re-enable modules you disabled. If GlazeWM workspaces stop responding, check whether PT FancyZones grabbed `Alt+1..9` again.\n- **PowerShell execution policy** — `pwsh.exe -ExecutionPolicy Bypass -File foo.ps1` is the AI-agent-friendly invocation. Default `Restricted` policy will silently refuse to run `.ps1` files and make it look like your script is broken.\n- **Windows-MCP needs the foreground window** — agent-driven UI automation can't click a window that's behind another. Either bring the target to front before sending input, or use the headless file\u002Fregistry APIs instead.\n- **Defender SmartScreen on first launch** — Scoop, GlazeWM, AutoHotkey scripts can all trip SmartScreen on first run. Right-click → Properties → Unblock, or `Unblock-File` in PowerShell. Don't disable SmartScreen globally — unblock per file.",[104,107,110,113,116],{"q":105,"a":106},"How long does the full install actually take on a fresh Windows machine?","Active install time is about 2 hours: 30 minutes for WinGet + Scoop + Windows Terminal + PowerShell 7 (all one-liners), 20 minutes for WSL 2 + an Ubuntu distro to download, 30 minutes for PowerToys + GlazeWM setup + hotkey conflict cleanup, 30 minutes for your first AutoHotkey script + Espanso config. Plan an evening, not a coffee break. The AI-stack tie-in (Windows-MCP wired into Claude Code) adds another 30 minutes once you've got `uvx` working.",{"q":108,"a":109},"Do I actually need WSL, or can I run this entire stack natively on Windows?","Native-only works fine for .NET, Go, Rust, and most Python dev. WSL becomes load-bearing when you depend on Linux-first tools (Docker without Desktop, Nix, Bash-heavy CI scripts that won't run under pwsh, or a Linux-only dependency in a Node project). Many engineers run WSL only when they hit a specific tool that needs it — not as a default. The pack treats WSL as a peer tab in Windows Terminal, not a primary OS.",{"q":111,"a":112},"Why GlazeWM if PowerToys FancyZones already snaps windows?","FancyZones is manual (you drag a window into a zone). GlazeWM is automatic (every new window tiles itself, i3-style). Different jobs. Most converts end up running both: FancyZones for big monitors where you want explicit control over a 2-3 window code review setup, GlazeWM for laptop screens where you just want everything tiled by default. The two coexist cleanly as long as their hotkeys don't overlap (use `Win+arrow` for FancyZones, `Alt+1..9` for GlazeWM workspaces).",{"q":114,"a":115},"Is AutoHotkey v1 or v2 the right version to learn in 2026?","v2. The official AutoHotkey team has marked v1 as maintenance-only; v2 is the supported future. The catch: 80% of scripts you'll find on GitHub or AHK forums are still v1 syntax. Use the official v1-to-v2 converter for old scripts; for anything new, learn v2 from the start (cleaner syntax, real functions, real objects, proper error handling). Don't waste time on v1.",{"q":117,"a":118},"Can AI agents like Claude Code actually drive Windows via Windows-MCP?","Yes — that's the whole point of the MCP server. Once you `uvx windows-mcp` and register it in Claude Code's MCP config, the agent gets tools for screenshot, click, keyboard input, file ops, and window management on Windows 10 and 11. Combined with PowerShell 7 for headless scripting, an agent can do the same desktop automation you'd write in AutoHotkey — but conversationally. Treat the MCP server as the high-trust glue layer: limit it to its own user account, not your admin profile.",{"@context":120,"@type":121,"name":13,"description":122,"numberOfItems":123,"inLanguage":25},"https:\u002F\u002Fschema.org","ItemList","Ten Windows-native and Windows-friendly tools for an AI-powered Win10\u002F11 developer setup, installed in deliberate order.",10,[125,129,133],{"url":126,"anchor":127,"reason":128},"\u002Fen\u002Fai-tools-for\u002Fautomation","AI agent automation tools","AutoHotkey and Windows-MCP belong to a larger AI-automation toolkit",{"url":130,"anchor":131,"reason":132},"\u002Fen\u002Ftopics","Browse other topic packs","Mac, backend, frontend, and data-engineer packs sit alongside this one",{"url":134,"anchor":135,"reason":136},"\u002Fen\u002Ffeatured","Featured assets on TokRepo","These ten tools live in the broader curated catalog",[138,142,146],{"claim":139,"source_name":140,"source_url":141},"WinGet is the official Windows Package Manager from Microsoft","WinGet documentation","https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows\u002Fpackage-manager\u002Fwinget\u002F",{"claim":143,"source_name":144,"source_url":145},"PowerToys is Microsoft's open-source productivity utility suite for Windows","PowerToys GitHub","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FPowerToys",{"claim":147,"source_name":148,"source_url":149},"GlazeWM is an i3-inspired tiling window manager for Windows","GlazeWM GitHub","https:\u002F\u002Fgithub.com\u002Fglzr-io\u002Fglazewm",1244,"2026-05-22T10:00:00Z"]