镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Computer Use plugin unavailable in ACP mode despite being enabled in CLI (Windows, 1.0.91) #5049

Description

@formulahendry

Description

Computer Use is enabled in the CLI, but an ACP session reports the bundled plugin as unavailable. The ACP server advertises the /computer command, so the command is recognized, but the plugin and its MCP server are not available in the session.

Environment

  • OS: Windows
  • Copilot CLI: 1.0.91 (also confirmed by ACP initialize response)
  • Bundled computer-use plugin: 0.1.92
  • Transport: ACP stdio

Steps to reproduce

  1. With Computer Use already enabled, run copilot plugin list. It reports computer-use (v0.1.92) [enabled] under built-in plugins.
  2. Start copilot --acp --stdio.
  3. Connect an ACP client, send initialize, then session/new with a local working directory and mcpServers: [].
  4. Observe that available_commands_update includes computer.
  5. Send /computer show as a single text block in session/prompt.
  6. Also query /plugin list and /mcp list through ACP.

Actual behavior

/computer show returns:

Computer Use:

Plugin: Unavailable
MCP   : Disabled

The bundled computer-use plugin is absent from ACP /plugin list, and its server is absent from ACP /mcp list.

Expected behavior / clarification requested

If Computer Use is supported over ACP, the enabled bundled plugin and MCP server should be available to local ACP sessions on supported operating systems. If ACP is intentionally unsupported, please document this limitation and make the command output explain it.

Additional context

The October 1 announcement describes availability in Copilot CLI and the Copilot app, while the setup documentation describes interactive CLI sessions without explicitly addressing ACP:

Activity

  1. added
    area:non-interactiveNon-interactive mode (-p), CI/CD, ACP protocol, and headless automation
    area:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agents
    and removed on Oct 4, 2026
  2. ShaunLawrie commented on Oct 11, 2026

    @ShaunLawrie

    This bug is wider than the ACP functionality. It doesn't load on Mac OS either in CLI or ACP mode.

    I've been losing my mind thinking I was doing something wrong because the documentation is pretty clear with how they expect you to enable it but it doesn't work, I tried quite a few different supported CLI versions and also tried them with --experimental but I had no luck. The CLI is mostly JS so I took a look at the cli-main.js in the package and found that there's an environment variable gating access to computer use.

    To enable the computer use plugin, set the COMPUTER_USE environment variable to true before launching copilot CLI.

    e.g. on my machine in bash with export COMPUTER_USE=true before running copilot CLI I get:

    Image

    Or on Windows with a PowerShell host:

    $env:COMPUTER_USE = "true"; copilot plugin list

    After the plugin loads you still need to enable computer use with /computer on.

    This either needs the documentation updated to reflect this pre-requisite or the env var gating should be removed in the CLI. There is precedent in having an environment variable to opt-in to allowing the computer to be controlled, I can see other references to COMPUTER_USE=1 in various agent frameworks online but it's inconsistently applied as a truthy flag to opt-in and an env var isn't a very strong security control. IMO it's not required as you need to turn it on with /computer on in the harness anyway, the extra layer seems redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:non-interactiveNon-interactive mode (-p), CI/CD, ACP protocol, and headless automationarea:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agents

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions