Windows
6 articles about "Windows".
agent-browser for the desktop: letting Claude Code drive Windows apps (field test)
agent-desktop turns Windows app windows into JSON so Claude Code can click by ref. Tested on Windows 10 with 1.2.0, rechecked on 1.3.1: what reads, what fails, two PowerShell traps.
git worktree plus a junctioned node_modules: how we broke our shared dependencies, and how we stop it now
On Windows, if a git worktree's node_modules is a mklink /J junction back to the main checkout, git worktree remove follows the junction and empties the main copy. We hit this four times between early September and mid October. Retesting this week: it happens without --force too, and running npm ci inside the junction also empties the main copy. Includes our cleanup order and a check script.
We ran 10 Claude Code agents at once and froze the PC. Here is how we schedule them now
Ten headless Claude Code agents, each running npm ci, a build and headless Chrome, left a 96 GB desktop unable to start cmd.exe. Our rules now: 6 at once, 2-minute stagger, a resource guard that sets a pause flag, workers clean up after themselves.
Exit code 0 is not success: how we check 50+ Windows scheduled tasks for real
Task Scheduler showed 0x0 while our Telegram watchdog actually exited 255 and never restarted anything. We stopped trusting result codes: every task writes its own start and end markers, a checker reads them, and no success within the time limit means red. 52 tasks covered, 1 left. Includes a VBS wrapper, the cmd errorlevel trap and a Node checker skeleton.
Running Claude Code in Windows CMD? Three Upgrade Layers to Make It Your Main Workflow
Running Claude Code in Windows CMD wastes it. Three upgrade layers: Windows Terminal, VS Code integration, then WSL2 with tmux. An assessment guide for managers.
Three Rough Edges of Running Claude Code + Telegram MCP on Windows: A 200-Line Toolkit
Running the official Telegram MCP plugin with Claude Code on Windows long enough surfaces three papercuts. None are bugs. They're gaps between OS behavior and plugin assumptions. Wrote a small toolkit to seal them, open-sourced it.