Skip to content

Upstream changes detected: ACP spec, Gemini CLI, GitHub Copilot CLI, Qwen Code #4

@github-actions

Description

@github-actions

This issue was opened automatically by upstream-watch.yml on 2026-05-18 because at least one upstream project this plugin depends on shipped a new release.

Detected changes

ACP spec — v0.12.2 → v0.13.2

  • Release: v0.13.2 (published 2026-05-17)
  • Why this matters for the plugin: Defines the JSON-RPC methods the plugin's acp-client.mjs implements. Spec changes can introduce new methods we should handle (e.g. terminal/*, session/request_permission, cursor/ask_question).
Release notes excerpt

Fixed

  • (unstable) Update additionalDirectories guidance (#1227)

Gemini CLI — v0.41.2 → v0.42.0

  • Release: Release v0.42.0 (published 2026-05-12)
  • Why this matters for the plugin: Drives plugins/multi/scripts/lib/adapters/gemini.mjs. Watch for changes to ACP handshake, model alias resolution, MCP support, or new approval modes.
Release notes excerpt

What's Changed

…(release notes truncated; click the link above for the full text)

GitHub Copilot CLI — v1.0.44 → v1.0.48

  • Release: 1.0.48 (published 2026-05-14)
  • Why this matters for the plugin: Drives plugins/multi/scripts/lib/adapters/copilot.mjs. Watch for ACP changes, slash-command additions/removals, or auth flow changes.
Release notes excerpt

2026-05-14

  • Model picker displays actual token prices instead of dot indicators for token-based billing users
  • Instruction files with unquoted glob patterns in applyTo frontmatter (e.g. applyTo: */.ts) are now applied correctly
  • Input text with CJK characters or emoji renders without blank gaps between lines
  • /context shows correct token limits for all models instead of always showing 128k
  • Auto-disable the built-in github-mcp-server in Azure DevOps-only workspaces when running in prompt/headless mode, matching interactive mode behavior
  • Terminal cursor positions correctly on the input field instead of on decorative elements like the selected tab
  • ACP clients receive updated config options when the active model is changed
  • /ask dialog no longer prompts for follow-up replies it cannot receive
  • Skill content injected to the model no longer includes YAML frontmatter metadata

Qwen Code — v0.15.10 → v0.15.11

  • Release: Release v0.15.11 (published 2026-05-13)
  • Why this matters for the plugin: Drives plugins/multi/scripts/lib/adapters/qwen.mjs. Watch for ACP support changes (the --acp flag graduated from --experimental-acp recently).
Release notes excerpt

What's Changed

…(release notes truncated; click the link above for the full text)

Also worth checking (manual — Copilot, please research these too)

  • Cursor agent CLI — changelog: https://cursor.com/changelog · forum (bug reports): https://forum.cursor.com/c/bug-report/6
    • Drives plugins/multi/scripts/lib/adapters/cursor.mjs. The plugin currently works around the 2026.04.17-787b533 ACP regression (see maybeWarnAboutCursorVersion and ensureCursorAllowlist). When Cursor ships a fix, both workarounds can likely be simplified or removed.

Plugin files most likely to need updates

  • plugins/multi/scripts/lib/acp-client.mjs (shared ACP JSON-RPC client; buildAutoApproveRequestHandler)
  • plugins/multi/scripts/lib/acp-terminals.mjs (client-side terminal services)
  • plugins/multi/scripts/lib/mcp-servers.mjs (MCP wiring for ACP session/new)
  • plugins/multi/scripts/lib/adapters/{codex,gemini,cursor,copilot,qwen}.mjs (per-CLI adapters)
  • plugins/multi/scripts/multi-cli-companion.mjs (companion runtime + dispatch)

What I'd like you to do, @copilot

  1. Read the linked release notes for each detected change above, plus the manual-reference changelogs.
  2. Compare what changed against the relevant adapter / shared code in this repo. Look specifically for:
    • New ACP methods we should handle in acp-client.mjs's buildAutoApproveRequestHandler
    • Renamed / deprecated CLI flags or model IDs hardcoded in any adapter
    • New CLI capabilities that obsolete a workaround we currently ship (e.g., the Cursor 2026.04.17 regression workaround in cursor.mjs — check if a newer Cursor release fixes it, and if so, propose removing maybeWarnAboutCursorVersion and the allowlist-injection or scoping it tighter)
    • Breaking changes that would silently break the plugin
  3. For each change that warrants action, open a focused PR against master with the minimal fix. Reference the upstream release / commit / forum thread in the PR description.
  4. If a detected change does NOT need any plugin update, reply on this issue with a short note saying "no plugin updates needed for X — reason: …" and close it.
  5. If something is ambiguous (you can't tell from release notes whether the plugin is affected), ask in a comment rather than guessing.

You may use ACP_TRACE=1 and the rest of the diagnostic patterns documented in plugins/multi/skills/customize/SKILL.md if you want to verify behavior empirically.


State tracked in .github/upstream-state.json — bumped by this same workflow. If you want to suppress a noisy upstream from this watch, edit .github/scripts/upstream-watch.mjs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    upstream-watchAuto-opened by upstream-watch.yml when an upstream releases

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions