windows-computer-use-mcp
Copilot instructions50 starsChanged 5 months agoMITView on GitHub
Native Windows UI automation over MCP: 20 portmanteau tools, all with an operation enum. Start sessions by recalling: automationwindows (find/focus), getdesktopstate (element tree), approveautomation before any click/type. Mutating runs need HITL approval or windowscomputerusemcpBYPASS_HITL=1. Backend: FastAPI on :10789 (/api/v1/*, MCP on /mcp); frontend :10788. Verify with uv run --no-sync ruff check src/ and pytest tests/ -q --no-cov. Close of work: commit per repo AGENTS.md, never leave the tree dirty.
We split this copilot-instructions.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Verify with uv run --no-sync ruff check src/ and pytest tests/ -q --no-cov.
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
windows-computer-use-mcp — Copilot instructions
Native Windows UI automation over MCP: 20 portmanteau tools, all with an
operation enum. Start sessions by recalling: automation_windows (find/focus),
get_desktop_state (element tree), approve_automation before any click/type.
Mutating runs need HITL approval or windows_computer_use_mcp_BYPASS_HITL=1.
Backend: FastAPI on :10789 (/api/v1/*, MCP on /mcp); frontend :10788.
Verify with uv run --no-sync ruff check src/ and pytest tests/ -q --no-cov.
Close of work: commit per repo AGENTS.md, never leave the tree dirty.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- desktop-automation-protocolSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

