Skip to content

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

Description

@github-actions

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

Detected changes

Gemini CLI — v0.49.0 → v0.50.0

  • Release: Release v0.50.0 (published 2026-07-08)
  • 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

Codex CLI (App Server Protocol) — rust-v0.142.5 → rust-v0.144.3

  • Release: 0.144.3 (published 2026-07-13)
  • 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

  • Published a version-only release with no merged pull request changes since rust-v0.144.2.

Changelog

Full Changelog: openai/codex@rust-v0.144.2...rust-v0.144.3

GitHub Copilot CLI — v1.0.68 → v1.0.70

  • Release: 1.0.70 (published 2026-07-10)
  • 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-07-09

  • Add GPT-5.6 model support
  • Show a single Error prefix for mcp and skill command failures
  • Show the real parse error when --agent selects a malformed custom agent
  • web_fetch works through mandatory HTTPS proxies
  • Hide / search on the Gists tab
  • Treat superseded subagent runs as cancellations instead of failures
  • Add paginated session.mcp.resources read/list/listTemplates RPCs for MCP server resources
  • preToolUse hooks that exit with code 2 deny tool calls
  • Create draft skills when Forge finds a clear workflow pattern
  • Hide the GitHub App install nudge in remote terminals
  • Pin plugins to an exact commit SHA using the sha field in plugin source configuration
  • Add --sandbox and --no-sandbox flags to turn the OS-level shell sandbox on or off for the current session only, without changing your saved sandbox setting (useful with -p)
  • Add /refine to rewrite a rough, stream-of-consciousness prompt into a clear one
  • Add --repo and --local flags to /settings and /model
  • Add a setting to show or hide timeline timestamps
  • Let a trusted repository pin the model, effort level, and context tier and extend the URL/MCP/skill deny lists via .github/copilot/settings.json
  • Expose SDK APIs to manage live MCP servers in running sessions
  • Show the active user's models after /user switch
  • Declining an extension's permission prompt no longer disables tool approvals for the rest of the session
  • Avoid redundant background agent notifications after a blocking read_agent returns its result
  • Startup auth errors recommend the real copilot login command
  • Keep merge-semantics settings editable in /settings
  • Re-sync managed plugins when their cache is missing or empty
  • Copy the last assistant response even after command echoes
  • Persist the last-logged-in user on every login so a restarted runtime client stays authenticated
  • Hide /agent picker navigation hints when there is nothing to select
  • Open the plan file or research report with Ctrl+Y in any mode
  • Keep terminal color scheme changes in sync over SSH and remote shells
  • Prefill /chronicle search so it can accept a query

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

Qwen Code — v0.19.6 → v0.19.9

  • Release: Release v0.19.9 (published 2026-07-10)
  • 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