WinCode MCP server
Commit Oct 17, 2026Enables AI agents to perform background Windows UI inspection and .NET code analysis through structured JSON and source code navigation.
Also known as linnnn89/WinCode
- Stars
- 1
- Tools
- 19
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 17, 2026
- License
- MIT
What is WinCode MCP?
WinCode enables AI agents to perform background Windows UI inspection and .NET code analysis through structured JSON and source code navigation. It exposes 19 tools, such as workspace_open, wincode_list_directory, wincode_analyze_workspace.
Summary generated from the project's README
About WinCode MCP server
Developers working on Windows and .NET applications can use WinCode to bridge the gap between running software and its source code. This local MCP server allows AI agents to perform background UI inspection using Windows UI Automation without interrupting your active window or changing keyboard focus. By returning control hierarchies, properties, and states as structured JSON, it enables text-only models to understand desktop interfaces without needing screenshots.
Beyond UI inspection, the server provides deep code intelligence for .NET projects. It supports navigating source files, searching for symbols, and analyzing project references. Users can choose between a standard text-based navigation mode or an optional Roslyn integration for compiler-backed C# symbol analysis. To use it, you must configure a local stdio connection in your MCP client, specifying the absolute path to the server and your project workspace. The setup requires Windows 11 x64, Node.js, and the .NET 10 SDK.
What you can do with it
- 1Debug disabled UI elementsAn agent can check if a specific button is enabled in a running application and then locate the corresponding C# code to find the cause.
- 2Perform semantic code analysisDevelopers can use Roslyn integration to search for specific C# symbols and find all their references across a solution.
- 3Inspect UI without visual inputText-only large language models can navigate desktop interfaces by receiving structured JSON data instead of images.
Written from the project's README. Every use case is checked against a quote from it.
WinCode MCP tools 19
Detected from the READMEworkspace_openwincode_list_directorywincode_analyze_workspacewincode_search_textwincode_file_outlinewincode_prepare_contextwincode_find_code_symbolwincode_find_referencesanalyze_change_impactwincode_plan_refactoringwincode_safe_move_to_trashwincode_ui_list_windows
Show all 19 toolsShow fewer tools
wincode_ui_inspectwincode_ui_clickwincode_ui_set_expandedwincode_ui_typewincode_ui_reviewwincode_hello_worldwincode_diagnose_project
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelinnnn89/wincode is public and reachablegithub.com/linnnn89/wincode ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-17github.com/linnnn89/wincode ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model19 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubWinCode
Setup / 配置指南 · Code / 代码分析 · UI inspection / UI 检查 · Changelog / 版本记录
The persistent JSON Skill session also supports explicit readonly workflows, checkbox summaries and one-parent expansion with observed ancestor paths. See client workflows and validation boundaries / 客户端工作流与验证边界. 这些流程通过显式调用启用;支持按实际父路径定位、一次展开与子控件状态读回,不自动递归导航或调用模型 API。
Checkbox audits accept either AutomationIds or exact name + CheckBox selectors. Real-application coverage and performance remain subject to validation; merging these capabilities does not change client defaults. 复选框统计可使用 ID 或精确名称与类型;真实应用覆盖与性能仍须验收,合并不改变客户端默认配置。
For repository maintenance, start with current work and acceptance criteria / 当前任务与验收条件, architecture / 架构与数据流, or contributing and verification / 开发与验证. Keep private screenshots and raw diagnostic results in ignored local directories; publish only sanitized findings. 本机截图和原始诊断材料保留在忽略目录,公开内容仅包含去标识后的结论。
English
WinCode is a local server implementing the Model Context Protocol (MCP) for AI coding agents. It combines Windows UI Automation (UIA), code navigation and .NET project analysis, so an agent can inspect a running application and investigate its source code through the same connection.
Features
- Background UI inspection: Read controls in a running application without activating its window or changing keyboard focus. Continue working in other applications while the agent inspects the target window.
- Support for text-only LLMs: Control names, hierarchy, properties and states are returned as structured JSON. Through an MCP-capable agent client, models such as DeepSeek used without image input can inspect desktop interfaces. Screenshots are optional.
- UI inspection with source navigation: Inspect a control, find candidate XAML declarations and related C# code, then read the relevant source lines. File paths, line numbers and content hashes make the findings traceable.
- Faster, more accurate inspection in everyday use: In our day-to-day Windows/.NET development, WinCode makes UI inspection and source navigation faster and more accurate than screenshot-based Computer Use workflows. Direct access to structured control properties and source locations reduces reliance on image interpretation and repeated interaction. Targeted queries and compact responses also reduce the amount of data the model needs to process.
- Project and code analysis: Explore declared solution and project references, search text and symbols, read selected code, and assess change impact. Built-in text analysis works by default; optional Roslyn integration provides compiler-backed C# symbol and reference analysis.
- Semantic UI actions:
wincode_ui_clickandwincode_ui_typeact on exactly one control that a single bounded search proves unique. They use UI Automation patterns and keyboard input only—never coordinate mouse simulation—and do not explicitly activate, restore or raise the target window. Control events and navigation may still bring the application forward. Disabled controls, ambiguous or incomplete matches, read-only values and unconfirmed keyboard focus are refused rather than guessed.
Use a query and an observed parent scope to retrieve the relevant controls, and request compact output when full geometry is unnecessary. Check completeness and ambiguity before drawing conclusions.
Example: Investigate a disabled Save button
Find the application's window, check whether the Save button is enabled without bringing the window to the foreground, and locate the relevant XAML and C# code.
The agent can complete this investigation using text output:
- Call
wincode_ui_list_windowswithprocessNameortitleContainsto obtain the target process ID (pid) and window handle (hwnd). - Call
wincode_ui_reviewwith the target control and relevant source files. If those files are not yet known, locate them with the code navigation tools first.
{
"pid": 12345,
"hwnd": "0x123456",
"backgroundOnly": true,
"capture": "none",
"responseFormat": "compact",
"query": { "automationId": "SaveButton", "controlType": "Button" },
"maxDepth": 3,
"maxNodes": 30,
"candidateFiles": ["Views/MainWindow.xaml"],
"candidateCodeFiles": ["ViewModels/MainWindowViewModel.cs"]
}
- Read the returned control properties and source candidates. For example,
isEnabled: falsereports that the control is disabled. Follow the returnednextRequestarguments withwincode_prepare_contextto inspect the candidate declaration or assignment. - Check the source before explaining the behavior. A matching binding or command name identifies code to investigate; it does not by itself establish the active
DataContextor the reason the button is disabled.
The IDs and paths above are placeholders. Use values from the actual window and workspace. When only the control tree is needed, use wincode_ui_inspect without the source-file arguments. Add readStates: true for toggle, selection or expand/collapse states; use capture: "annotated" when a numbered screenshot is useful for visual review.
Quick start
Requirements: Windows x64, Git 2.36 or later, Node.js >=22 (24 primary, 22 compatible), and .NET SDK 10.0.303. The SDK version is pinned in global.json with roll-forward disabled. The published UI helper and optional Tray require the .NET 10 Windows Desktop runtime. Windows 11 x64 is the development and test baseline.
1. Build and verify WinCode
git clone https://github.com/linnnn89/WinCode.git
cd WinCode
npm ci
npm run check
npm run delivery:verify
Running npm run check builds the Gateway and native components, runs core regression and stdio integration tests, and verifies the delivery manifest. Desktop tests are available separately.
2. Configure the MCP connection
For Codex with persistent terminal support, the Skill on-demand mode starts WinCode only when needed and reuses one connection throughout the task. Install the Skill, disable the native WinCode MCP entry, and refresh the client connection before using this mode. The Skill starts dist/Client/SkillSessionCli.js in an interactive execution session; results remain available as full JSON and image files. It requires an extra file read per result. Other clients can use the native stdio configuration below.
For clients that support mcpServers, add the following stdio configuration. Explicitly setting --workspace is recommended:
{
"mcpServers": {
"wincode": {
"command": "node",
"args": ["C:/path/to/WinCode/dist/index.js", "--workspace", "C:/path/to/project"]
}
}
}
Replace both paths with existing absolute paths. The WinCode installation directory and your project directory may be different. Ensure node is available in PATH, or use its absolute executable path.
For a graphical configuration interface, use type stdio, command node, and three separate argument entries: the dist/index.js path, --workspace, and the project path. Do not add surrounding quotes to individual argument entries, even when a path contains spaces. No additional environment variables are required for the default configuration.
3. Verify the connection and try a query
After connecting, ask the agent to call wincode_hello_world and confirm that health.workspaceBinding.root matches your project. Then try:
Summarize this project's structure, list the contents of
src, and locate the code responsible for saving data.
The agent can use workspace_open to obtain the project summary, wincode_list_directory to browse a directory, and wincode_search_text to locate code. For UI inspection, start the target application in your interactive Windows desktop session and use the example above.
Each connection is bound to one workspace for its lifetime. workspace_open confirms or recovers that workspace; it does not switch projects. A different root returns WORKSPACE_MISMATCH. Use a separately configured connection for another project. If --workspace is omitted, the connection binds to the server's launch directory.
See the Skill and MCP setup guide for client configuration and the optional agent Skill. After rebuilding, reconnect the client's MCP server to load the updated process and tool schemas.
Common workflows and tools
Code navigation: Start with a known directory, file or symbol. wincode_search_text searches within scopePaths using plain strings rather than regular expressions; wincode_file_outline returns a file's declarations and line count. Both provide follow-up arguments for reading source with wincode_prepare_context.
{
"task": "Review the save logic",
"lineRanges": [{ "file": "src/Service.cs", "startLine": 50, "endLine": 80 }],
"maxTokens": 2000
}
Use actual paths and line numbers from the search result. lineRanges selects known lines; scopeFiles limits reading to known files. candidateFiles prioritizes files during discovery and is not an exclusive scope. Check returned ranges, coverage and truncation before deciding whether more code is needed. maxTokens is an estimate based on UTF-16 character count, not a model-specific token count.
UI inspection: Select a window, query the relevant control or subtree, and request source candidates when needed. responseFormat: "compact" retains control IDs, names, hierarchy and states while omitting per-node geometry and class names. Use full when coordinates or additional detail are needed. Unsupported or unknown control states are distinct from false.
C# semantic analysis: Enable Roslyn explicitly, search for a symbol, and pass its returned location unchanged as symbolLocation to reference, impact or refactoring tools. Search again when the tool reports a stale location. The default local-text provider offers text-based navigation and reports its semantic limitations.
| Tool | Purpose |
|---|---|
workspace_open |
Confirm or recover the fixed workspace and return a compact project summary. |
wincode_list_directory |
Browse a directory with depth, entry-count and output limits. |
wincode_analyze_workspace |
Read solution structure and declared project references. |
wincode_search_text |
Find literal text within selected files or directories. |
wincode_file_outline |
Read a file's local declarations and observed line count. |
wincode_prepare_context |
Read selected source excerpts with paths, line ranges and coverage information. |
wincode_find_code_symbol |
Search symbols using the configured provider. |
wincode_find_references |
Find references and report known totals, returned counts and truncation. |
analyze_change_impact |
Assess potential change impact and report uncertainty when evidence is incomplete. |
wincode_plan_refactoring |
Suggest checks and verification steps for a proposed refactoring. |
wincode_safe_move_to_trash |
Move validated workspace files to trash/ and record the actual completed or partial outcome. |
wincode_ui_list_windows |
List visible top-level windows with process and title filters. |
wincode_ui_inspect |
Read controls and optional states or screenshots. |
wincode_ui_click |
Click one uniquely matched control through UI Automation patterns. |
wincode_ui_set_expanded |
Explicitly expand/collapse one uniquely matched enabled control; optional scopePath confines it to observed ancestors. Requires inspectionVersion 4, or 5 with a path. Verify its state afterwards. |
wincode_ui_type |
Type text into, or set the value of, one uniquely matched control. |
wincode_ui_review |
Inspect UI and return candidate XAML/C# source locations. |
wincode_hello_world |
Read instance identity, workspace binding, capabilities and known status. |
wincode_diagnose_project |
Actively check SDKs, Git and the local environment. |
wincode_analyze_change_impact is an alias of analyze_change_impact. Detailed parameters and workflows: code analysis, UI inspection, diagnostics. To inspect a tool's schema in the running connection, pass its name as toolName to wincode_hello_world.
Optional configuration
- Roslyn: Add
--roslyn-configfollowed by an absolute configuration-file path. This enables the C# Code Host and requires explicit authorization for MSBuild project evaluation. Configuration, input tracking and recovery are described in the code guide. - Connection configuration: Run
node C:/path/to/WinCode/dist/index.js --print-connection --workspace C:/path/to/projectto generate a project's stdio configuration without starting its Gateway or changing client settings. This generates the default local-text configuration; add any Roslyn or Tray options separately. - Tray and memory management: Add
--trayto the Gateway arguments, reconnect, and manually starttools/WinCode.Tray/bin/Release/net10.0-windows/win-x64/publish/WinCode.Tray.exe --show. In 设置 / 内存管理, select an idle instance and choose 释放 Roslyn 内存. The next explicit symbol search reloads the project; previous symbol locations become invalid. Automatic idle release is disabled. Exiting Tray leaves MCP running. See the diagnostics guide. - Agent Skill: After updating WinCode, use
npm run skill:check -- <absolute-skill-directory>to check the installed Skill.npm run skill:sync -- <absolute-skill-directory>backs up and synchronizes the Skill documents managed by the sync script. It does not change MCP configuration or restart a connection.
Scope and limitations
- Desktop access: UI inspection is read-only: it does not click controls, type text or read input-field values. The separate
wincode_ui_clickandwincode_ui_typetools are destructive: they act on one uniquely matched control through UI Automation patterns or keyboard input, never mouse simulation, and do not explicitly activate or restore the target window. Application events may still bring it forward. They refuse disabled controls, ambiguous or incomplete matches, read-only values and unconfirmed keyboard focus:typerequests keyboard focus on the control (which may bring its window to the front), so use it only when the user has approved foreground interaction, and prefermode:"setValue"for background work. Background mode requires both PID and HWND, supports non-minimized windows, and does not activate or restore the target. UI inspection requires an interactive Windows desktop session and does not support headless operation. - UIA and visual rendering: Available properties depend on the application's UIA provider. WPF is covered by the project's desktop tests; other frameworks and custom-rendered controls may expose less information. Colors, icons and rendering quality require visual review. Background screenshots use
PrintWindowwithout screen-capture fallback; check the returned capture-quality indicators. - Source mapping: XAML and C# matches identify candidate source locations, with
runtimeSourceVerified: false. The tool does not verify that the running build matches the source, resolve dynamic bindings or runtime templates, or determine the activeDataContext. - Analysis coverage: Project structure analysis reads
.slnand.csprojdeclarations without MSBuild evaluation. Text-based references are heuristic. Review completeness, omissions and diagnostics before drawing conclusions; no matches in a limited scan do not establish absence across the project. - Resource limits: Requests, traversal and response size have explicit limits. Overload returns
SERVER_BUSY; queue time counts toward the timeout. Output limits do not represent process memory limits. Full concurrency, cache and process-lifecycle details are in the architecture guide. - Inspection notice: During UI inspection and UI actions, a semi-transparent
REC / WinCodingstatus overlay is displayed without taking focus, and minimal local audit metadata is recorded under%LOCALAPPDATA%/WinCode/logs/ui-audit, including the action name for actions. See the diagnostics guide for audit-log maintenance.
Development and documentation
Current source version: 0.17.1. See CHANGELOG for version history and migration notes. Windows 11 x64 is the reference platform; ports to other operating systems require adaptation and separate validation.
npm run check # Builds, core regression, stdio integration and delivery verification
npm run check:desktop # WPF and UI-to-source tests; requires an interactive Windows desktop
npm run delivery:verify # Verify Gateway, native components and managed Skill artifacts
npm run test:inventory # Verify automated-test suite registration
npm run benchmark:agent -- 1 # Run one iteration of the optional scripted benchmark
npm run benchmark:context -- compare 8 # Model-free, paired sequential/batch context experiment
benchmark:context accepts baseline|compare, 1–100 repetitions, and an optional existing WinCode checkout path. Without a path it creates an isolated fixture under ignored test-tmp/context-work/; reports remain there. It exercises real MCP handlers over in-memory transport, records request-local inclusive phase times and application-level scan/read/parse counters, checks paired response equality and source evidence, and verifies input hashes. first means a fresh application cache, not cold OS disk cache. Initialization, prewarm and cleanup are excluded; no model, UIA, or network is used. Production local-text context requests batch up to four extracted keywords by default; the benchmark explicitly selects sequential queries as its baseline. Truncated/capped batches fall back to sequential queries and may cost more; no P95 or general Agent speedup is inferred.
CI runs on Windows with Node.js 22 and 24 and the pinned .NET SDK. The Node.js 22 job includes additional native and integration checks; desktop tests run separately. Benchmark reports measure scripted scenarios, including calls, response size and execution time. See the linked records for test conditions and results.
- Contributing: builds, test suites and delivery requirements.
- Architecture and data flow: components, interfaces, resource limits and lifecycle management.
- Skill and MCP setup: installation and client configuration.
- Iteration plan: unfinished improvements, known limitations and acceptance criteria.
简体中文
WinCode 是面向 AI 编程智能体的本地模型上下文协议(Model Context Protocol,MCP)服务器,集成 Windows UI Automation(UIA)、代码导航和 .NET 项目分析功能。智能体可以通过同一连接检查正在运行的应用,并查阅相关源码。
核心功能
- **后台 UI 检查:**无需激活目标窗口或切换键盘焦点,即可读取运行中应用的控件信息。智能体检查目标窗口时,用户可以继续使用其他应用。
- **支持纯文本大语言模型:**以结构化 JSON 返回控件名称、层级、属性和状态。通过支持 MCP 的智能体客户端,DeepSeek 等以纯文本方式使用的模型也能检查桌面界面,无需输入图像;截图为可选功能。
- **结合源码分析 UI:**检查运行时控件,查找可能对应的 XAML 声明和相关 C# 代码,再读取具体源码。结果包含文件路径、行号和内容哈希,便于核查。
- 语义化 UI 操作:
wincode_ui_click与wincode_ui_type只操作同一次有界搜索证明唯一的控件;仅使用 UI Automation 模式与键盘输入,不做坐标鼠标模拟,不主动调用激活、还原或置顶;控件事件与导航仍可能让应用进入前台。禁用控件、歧义或不完整的匹配、只读值以及无法确认的键盘焦点都会被拒绝,而不是靠猜测继续。 - **实际使用中更快、更准确:**在日常 Windows/.NET 开发中,使用 WinCode 检查 UI 和定位源码,比基于截图的 Computer Use 工作流更快、更准确。通过直接获取结构化的控件属性和源码位置,可以减少对图像识别的依赖和反复交互;配合定向查询与精简响应,还能减少模型需要处理的数据量。
- **项目与代码分析:**查看解决方案和项目中声明的引用关系,搜索文本与符号,按需读取代码,并评估变更影响。默认提供内置文本分析,可选的 Roslyn 集成支持基于编译器语义的 C# 符号与引用分析。
通过 query 和实际观察到的父范围只读取相关控件,不需要完整几何信息时使用 compact 输出。得出结论前仍需核对完整性与歧义。
使用示例:排查“保存”按钮被禁用的问题
查找应用窗口,在不切换前台窗口的情况下检查“保存”按钮是否启用,并定位相关 XAML 和 C# 代码。
智能体可以通过纯文本输出完成以下排查流程:
- 调用
wincode_ui_list_windows,通过processName或titleContains获取目标进程 ID(pid)和窗口句柄(hwnd)。 - 调用
wincode_ui_review,指定目标控件和相关源码文件。如果尚不知道文件位置,先使用代码导航工具定位。
{
"pid": 12345,
"hwnd": "0x123456",
"backgroundOnly": true,
"capture": "none",
"responseFormat": "compact",
"query": { "automationId": "SaveButton", "controlType": "Button" },
"maxDepth": 3,
"maxNodes": 30,
"candidateFiles": ["Views/MainWindow.xaml"],
"candidateCodeFiles": ["ViewModels/MainWindowViewModel.cs"]
}
- 查看返回的控件属性和源码候选位置。例如,
isEnabled: false表示控件处于禁用状态。根据返回的nextRequest参数调用wincode_prepare_context,读取候选声明或赋值语句。 - 核查源码后再解释界面行为。匹配到绑定或命令名称,可以确定下一步需要检查的代码,但仅凭名称匹配无法确定当前
DataContext或按钮被禁用的原因。
上述 ID 和路径均为示例,使用时应替换为实际窗口和工作区中的值。如果只需读取控件树,可使用 wincode_ui_inspect,无需传入源码文件参数。需要勾选、选中或展开/折叠状态时,添加 readStates: true;需要结合编号截图检查视觉效果时,使用 capture: "annotated"。
快速开始
**环境要求:**Windows x64、Git 2.36 及以上、Node.js >=22(推荐 24,兼容 22),以及 .NET SDK 10.0.303。SDK 版本已在 global.json 中锁定,并通过 rollForward: "disable" 要求使用完全匹配的版本。发布的 UI 辅助程序和可选托盘程序均依赖 .NET 10 Windows Desktop 运行时。开发和测试的基准平台为 Windows 11 x64。
1. 构建并验证 WinCode
git clone https://github.com/linnnn89/WinCode.git
cd WinCode
npm ci
npm run check
npm run delivery:verify
运行 npm run check 会构建 Gateway 和原生组件,执行核心回归测试与 stdio 集成测试,并验证交付清单。桌面测试单独执行。
2. 配置 MCP 连接
支持持久终端的 Codex 可使用 Skill 按需模式:首次需要时才启动 WinCode,任务内复用同一连接。先安装 Skill、禁用原生 WinCode MCP 条目,并刷新客户端连接。Skill 通过交互执行会话启动 dist/Client/SkillSessionCli.js,完整结果保存为 JSON 和图片文件,每次结果需要额外读取文件。其他客户端可使用下列原生 stdio 配置。
对于支持 mcpServers 的客户端,添加以下 stdio 配置。建议显式设置 --workspace:
{
"mcpServers": {
"wincode": {
"command": "node",
"args": ["C:/path/to/WinCode/dist/index.js", "--workspace", "C:/path/to/project"]
}
}
}
将两个路径替换为实际存在的绝对路径。WinCode 安装目录与目标项目目录可以不同。确保 node 位于 PATH 中,或将命令改为其可执行文件的绝对路径。
使用图形化配置界面时,类型选择 stdio,命令填写 node,依次添加三个独立参数:dist/index.js 的路径、--workspace、目标项目路径。即使路径包含空格,也不要为独立参数额外添加引号。默认配置不需要额外环境变量。
3. 验证连接并执行首次查询
连接后,让智能体调用 wincode_hello_world,确认 health.workspaceBinding.root 与目标项目一致,然后尝试:
概述项目结构,列出
src目录中的内容,并查找负责保存数据的代码。
智能体可以使用 workspace_open 获取项目摘要,使用 wincode_list_directory 浏览目录,再通过 wincode_search_text 定位代码。检查 UI 时,先在交互式 Windows 桌面会话中启动目标应用,再参考前面的使用示例。
每条连接在其生命周期内固定对应一个工作区。workspace_open 用于确认或恢复该工作区,不能切换项目;请求其他根目录会返回 WORKSPACE_MISMATCH。访问其他项目时,应使用单独配置的连接。如果省略 --workspace,连接将固定到服务器的启动目录。
客户端配置和可选的智能体 Skill 安装方式见 Skill 与 MCP 配置指南。重新构建后,需要重新连接客户端中的 MCP 服务器,才能加载更新后的进程和工具参数定义。
WinCode MCP questions
What tools does WinCode MCP provide?
It exposes 19 tools, including workspace_open, wincode_list_directory, wincode_analyze_workspace, wincode_search_text, wincode_file_outline.
Does WinCode require screenshots for UI inspection?
No, it supports text-only LLMs by returning control names, hierarchy, properties, and states as structured JSON. Screenshots are optional.
Can WinCode inspect applications without taking focus?
Yes, it provides background UI inspection that allows you to read controls in a running application without activating its window or changing keyboard focus.
What are the system requirements for WinCode?
It requires Windows x64, Git 2.36+, Node.js 22 or 24, and .NET SDK 10.0.303.
How does WinCode handle UI actions like clicking or typing?
It uses UI Automation patterns and keyboard input to act on unique controls without simulating mouse coordinates or explicitly activating the window.