Skip to content

Upstream changes detected: ACP spec, Gemini CLI, Codex CLI (App Server Protocol), GitHub Copilot CLI, Qwen Code #10

Description

@github-actions

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

Detected changes

ACP spec — schema-v1.14.0 → schema-v1.17.0

  • Release: Schema v1.17.0 (published 2026-06-29)
  • 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

Added

  • (schema) Stabilize request cancellation (#1549)

Fixed

  • Deserialization leniency part 2 (#1526)
  • (unstable-v2) make mcpServers optional in new sessions (#1523)

Other

  • (unstable-v2) Clean up client schema types (#1540)
  • (schema) correct Implementation description (#1518)

Gemini CLI — v0.47.0 → v0.49.0

  • Release: Release v0.49.0 (published 2026-06-25)
  • 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

New Contributors

Codex CLI (App Server Protocol) — rust-v0.141.0 → rust-v0.142.4

  • Release: 0.142.4 (published 2026-06-29)
  • Why this matters for the plugin: Drives plugins/multi/scripts/lib/adapters/codex.mjs and app-server.mjs. Watch for sandbox mode changes, new approval policies, or app-server protocol updates.
Release notes excerpt

Chores

  • No user-facing changes were identified for this release.

Changelog

Full Changelog: openai/codex@rust-v0.142.3...rust-v0.142.4

GitHub Copilot CLI — v1.0.63 → v1.0.65

  • Release: 1.0.65 (published 2026-06-24)
  • 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-06-24

  • /cd now persists the working directory so resuming a session returns to it, and discovers custom agents in the new directory
  • Commands with slash-prefixed string arguments (e.g. --body "/azp run") no longer trigger spurious filesystem permission prompts
  • Fullscreen timeline stays anchored when older content is trimmed
  • Resume open canvases automatically after restarting the CLI
  • Add an opt-in status bar item showing CI check status (passing/running/failing) for the current branch
  • Add a copilot skill subcommand (and a /skill alias for /skills) to list, add, and remove skills from a file, URL, or directory
  • Prevent the GitHub background from flashing on startup with non-GitHub themes
  • Prevent brief console windows from flashing on Windows when the agent runs hook commands or resolves command paths
  • Include userPromptSubmitted hook additionalContext in the model-facing prompt
  • Keep Windows paths intact when adding stdio MCP servers
  • Stop MCP shutdown from waiting on in-flight server connects
  • Restart the CLI without shutdown timeouts
  • Remove syntax highlighting from shell commands in the timeline
  • Keep custom-agent subagent model selections when using BYOK providers
  • Parse /every schedules on the session's main model
  • Render inline images reliably in tmux
  • The ask_user freeform option wraps text and keeps the cursor aligned
  • Save custom status line commands in /settings
  • Show the streaming byte count separately from the cancel hint
  • Handle wakeup misfires with a graceful message when no self-paced schedule is active
  • Silent MCP OAuth refresh reuses the granted scope so reconnects stay signed in
  • Up/down history and Ctrl+R reverse search now include past shell commands while in normal mode, so you can recall and re-run a shell command without first typing ! to enter shell mode

Qwen Code — v0.18.5 → v0.19.3

  • Release: Release v0.19.3 (published 2026-06-28)
  • 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