github / github/copilot-cli

Copilot dissapeared while working in two terminals, now won't run, says it is not installed. Ubuntu 24.04 LTS Guake and Terminal.

Open
#3,967 0 comments 0 reactions 0 assignees View on GitHub
area:installation area:platform-linux
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

On my first try of copilot, I was thrilled by its performance. It made a gist for me containing commands etc. I made a macro for me to invoke it with one word. It was great. Then it dissapeared, never to return.

**What happened:**
Using Guake, it was making a gist with keyboard commands, help tips, often used routines etc, and made it availble in Terminal.
Then copilot dissapeared from Guake as I was using it. My hands were on my keyboard a the time, its not impossible I inadvertently touch the q ket, or it crashed - I can't be sure.

_Side note_ - Copilot had said I must log in and out of Gnome desktop to make permanent some edits it made. I said no as I have an open project in use.ai in Chrome that was paused for 24 hours because of use,ai's unbeleivable nasty token cutoff nonsense. I need to continue that this afternoon.

Ater it dissapeared, on trying to reload it in Guake, it said it copilot was not installed, install it with snap.
I have never used snap, I installed it with curl, and I still use apt-install for installs on Ubuntu.
So I double clicked the app instead, it gave an auth code, the code was accepted, but still no copilot. That happened a few times, now it tells me I need an account, which I have. Stuck.
Copilot's online help ai tells me it is too scared to help.

Copilot had been joyfully rewiring stuff under the hood, but the session is no longer available, I can't track what it did to undo it.
Any ideas?
Bear in mind I've only used copilot for a couple of hours, not exactly familiar with it.

Contributor guide

Open the contributing guide

Research direction

The report names Ubuntu 24.04, Guake and Terminal, curl installation, and an auth-code flow, but no repository files or failing test. Start by reproducing the disappearance and “not installed” or account errors in that setup; done means identifying a reliable cause and documenting a recovery path.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, shell, ubuntu
Domain
authentication, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.