WisCode Computer Use

WisCode fork of the cross-platform Open Computer Use MCP server, packaged for WisCode computer-use permission gating.

This package bundles native runtimes for these supported platforms and lets the Node launcher choose the current process.platform / process.arch pair:

• darwin-arm64
• darwin-x64
• linux-arm64
• linux-x64
• win32-arm64
• win32-x64

Global commands:

• wiscode-computer-use
• wiscode-computer-use-mcp

Install

npm install -g wiscode-computer-use

The root launcher resolves the current process.platform / process.arch pair and runs the matching bundled native runtime.

MCP config

If your MCP client accepts a stdio-style mcpServers JSON config, this is the default setup:

{
  "mcpServers": {
    "open-computer-use": {
      "command": "wiscode-computer-use",
      "args": ["mcp"]
    }
  }
}

Package: wiscode-computer-use

Use

wiscode-computer-use --version
wiscode-computer-use --help
wiscode-computer-use mcp
wiscode-computer-use call list_apps

# macOS machine-readable permission gate, with no onboarding side effects
wiscode-computer-use permissions status --json --no-open

# macOS permission check and onboarding
wiscode-computer-use doctor

# Installer helpers for MCP-capable CLIs
wiscode-computer-use install-claude-mcp
wiscode-computer-use install-gemini-mcp
wiscode-computer-use install-gemini-mcp --scope user
wiscode-computer-use install-codex-mcp
wiscode-computer-use install-opencode-mcp
wiscode-computer-use install-codex-plugin

The macOS app bundle is WisCode Computer Use.app with bundle identifier com.qihoo.coding.wiscode-computer-use. macOS treats it as a separate app from upstream, so users must grant Accessibility and Screen Recording to WisCode Computer Use.

Notes

• Version: 0.1.55-wiscode.0
• Supported npm platforms: darwin-arm64, darwin-x64, linux-arm64, linux-x64, win32-arm64, win32-x64
• macOS still requires Accessibility and Screen Recording permissions.
• After code changes, regenerate the latest signed app and npm tarball with ./scripts/rebuild-latest-app.sh. Add --install to reinstall the generated package globally after packaging.
• Sign and notarize releases with scripts/sign-and-notarize-macos-app.sh. The script builds dist/WisCode Computer Use.app, signs it with Developer ID Application and hardened runtime, submits it to Apple notarization, staples the ticket, validates the app, and writes an npm tarball to release/.
• The signing script uses the same environment names as WisCode: CSC_NAME, CSC_LINK, CSC_KEY_PASSWORD, APPLE_API_KEY, APPLE_API_KEY_ID, and APPLE_API_ISSUER. Put them in ./.mac-signing.env or export them before running the script.
• If the Developer ID identity must be imported into a temporary keychain, place Developer ID intermediate certificates under ./mac_cer/ or set MAC_SIGN_DEVELOPER_ID_CA_PATHS.
• Linux requires a signed-in desktop session with AT-SPI2 / D-Bus accessibility available for real app control.
• Windows requires a signed-in desktop session for UI Automation access.

Forked from [email protected].