Running /update from a resumed session leaves conflicting --session-id and --resume flags

[jay-tau]

Summary

When I resume a Copilot CLI session with copilot -r, then run /update because an update is available, the CLI fails after the update instead of resuming the session. It appears to restart with both --session-id and -r/--resume set.

Steps to reproduce

1. Start Copilot CLI by resuming a previous session:

   copilot -r

2. In the resumed session, when an update is available, run:

   /update
   

3. After the update finishes/restarts, try to continue the resumed session.

Actual behavior

The CLI prints resume/session info, then exits with this error:

╭─╮╭─╮   Changes    +705 -11
╰─╯╰─╯   AI Credits 0 (49h 52m 6s)
█ ▘▝ █   Resume     copilot --resume="juby-tax"
 ▔▔▔▔

error: option '--session-id <id>' cannot be used with option '-r, --resume[=value]'

It does not resume the previous session.

Expected behavior

After /update from a resumed session, Copilot CLI should continue/resume the same session without passing mutually exclusive flags, or it should restart with only the correct resume/session flag.

Environment

• Copilot CLI version: 1.0.63
• OS: Linux

[dimanardiyansah123-stack]

***@***.***

…

---------- Forwarded message --------- Dari: Joel Tony ***@***.***> Date: Sel, 16 Jun 2026, 20.20 Subject: [github/copilot-cli] Running /update from a resumed session leaves conflicting --session-id and --resume flags (Issue #3821) To: github/copilot-cli ***@***.***> Cc: Subscribed ***@***.***> *jay-tau* created an issue (github/copilot-cli#3821) <#3821> Summary When I resume a Copilot CLI session with copilot -r, then run /update because an update is available, the CLI fails after the update instead of resuming the session. It appears to restart with both --session-id and -r/--resume set. Steps to reproduce 1. Start Copilot CLI by resuming a previous session: copilot -r 2. In the resumed session, when an update is available, run: /update 3. After the update finishes/restarts, try to continue the resumed session. Actual behavior The CLI prints resume/session info, then exits with this error: ╭─╮╭─╮ Changes +705 -11 ╰─╯╰─╯ AI Credits 0 (49h 52m 6s) █ ▘▝ █ Resume copilot --resume="juby-tax" ▔▔▔▔ error: option '--session-id <id>' cannot be used with option '-r, --resume[=value]' It does not resume the previous session. Expected behavior After /update from a resumed session, Copilot CLI should continue/resume the same session without passing mutually exclusive flags, or it should restart with only the correct resume/session flag. Environment - Copilot CLI version: 1.0.63 - OS: Linux — Reply to this email directly, view it on GitHub <#3821?email_source=notifications&email_token=CFNECYSZ4QDOUSYCKOXUMBD5AE3SHA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG42DANZRGE3DNJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFNECYT2FPMNRKW4KLI4MKL5AE3SHAVCNFSNUABFKJSXA33TNF2G64TZHM2TQNJYGYYDMNRUHNEXG43VMU5TINRXGQYDOMJRGY3KC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CFNECYSVWOODNNCY7IDP3U35AE3SHA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG42DANZRGE3DNJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CFNECYX2ANXSK4ANP6ZHCZ35AE3SHA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBWG42DANZRGE3DNJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>