# Fix: Copilot 1.4.0 Session Unavailable Error

> Source: <https://dev.to/debugradar/fix-copilot-140-session-unavailable-error-3ebo>
> Published: 2026-11-22 07:00:31+00:00

**Key takeaway:** Copilot desktop 1.4.0 detaches sessions after a few idle minutes, and recovery requires restoring the data.db.pre-update-backup-1.4.0 file before downgrading to 1.3.0 — a plain downgrade leaves sessions broken.

*Originally published on [DebugRadar](https://debugradar.com/fix-copilot-1-4-0-session-unavailable-error/).*

| Error Code | Affected Version | Root Cause | Current Status | 
|---|---|---|---|
| "This conversation is still saved on this device — the agent just couldn't reattach to it. Try again. If it keeps failing, start a new session." + "Failed to list plugins" + "Session unavailable" + "Failed to create session" | GitHub Copilot desktop app 1.4.0 (reporter: macOS 26.7.3) | 1.4.0 breaks session resume/reattach — the session works while you are working on it, but when you leave it for a few minutes the Copilot process detaches and the session no longer works. New sessions in 1.4.0 also break after a few minutes. No cause published by GitHub beyond the issue. | Still open as of Nov 13, 2026 — github/app#5743, 13 comments, no staff reply. v1.4.1 and v1.4.2 shipped Nov 14 and fix adjacent session-start problems, but GitHub has not confirmed the reattach error itself is fixed | 

Update to 1.4.2 before anything else and test whether your sessions reattach. Version 1.4.2 (Nov 14 18:45 UTC) fixes sessions failing to start or resume with "Session plugin inputs changed during reload" when an organisation policy turns off Computer Use, and 1.4.1 (Nov 14 04:47 UTC) fixes sessions hanging at start when another Copilot process holds the shared log lock. Neither names the "couldn't reattach" error, so treat the update as a first test, not a guaranteed fix — if sessions reattach, you are done.

If 1.4.2 does not fix it, roll back to 1.3.0 using the database backup 1.4.0 made before updating. This is user-verified (kuisathaverat, Nov 13 13:15 UTC). Close GitHub Copilot, then:

```
mv ~/.copilot/data.db ~/.copilot/data.db.bak
mv ~/.copilot/data.db.pre-update-backup-1.4.0-1794558622835 ~/.copilot/data.db
```

Then install 1.3.0 and start it. Note honestly: a plain downgrade without the database restore does not recover the sessions — the reporter tried that first and the sessions stayed broken. The database backup is the part that matters.

Turn off auto-update after the rollback so 1.4.0 is not reinstalled on top of your recovered sessions. Check for the update setting in Copilot's settings before you start working again.

The reporter tried all three and all failed: restoring a session by its ID in a new session, archiving and restoring a session, and saving a Gist and importing the full session (which would also consume a large number of tokens). New sessions start empty — recover your changes manually from the worktree instead of chasing the session itself.

If you need to keep working now, open VS Code from the broken session — the reporter confirmed the broken sessions work fine in VS Code Insiders chat (version 1.147.0-insider). Your code and your changes are in the worktree; only the Copilot desktop app's session resume is broken.

A related note: 1.4.0 also broke custom model providers (github/app#5738) — 1.4.1 notes say local models are no longer blocked in enterprise / business accounts. The same discipline applied to the GitHub Copilot model outage in [Fix: GitHub Copilot Models Not Working](https://debugradar.com/fix-github-copilot-models-not-working/) — check the vendor's status and release notes first, then work around it. And the same pattern showed up in the Cursor crash in [Fix: Cursor Crashes With 0x80000003 Error](https://debugradar.com/fix-cursor-crashes-0x80000003-error/) — when the vendor has to fix it, your job is evidence and a workaround, not a fake fix.

**Is the "Session unavailable" error fixed in 1.4.2?**

Not confirmed. Version 1.4.2 fixes sessions failing to start or resume with "Session plugin inputs changed during reload" when an organisation policy turns off Computer Use, and 1.4.1 fixes a log-lock hang at session start. Neither release names the "couldn't reattach" / "Session unavailable" error, and the issue is still open with no staff reply. Update to 1.4.2 first and test — if sessions still won't reattach, use the 1.3.0 rollback below.

**Will rolling back to 1.3.0 recover my sessions?**

Yes — with the database backup. A plain downgrade does not recover them. You must restore the pre-update backup file (`~/.copilot/data.db.pre-update-backup-1.4.0-…`) as `~/.copilot/data.db` after moving the broken database aside. That procedure is user-verified (Nov 13).

**Why does Health Check say "Healthy" when everything is broken?**

Health Check reports the app's own components as healthy — it does not test session resume/reattach, which is exactly the part 1.4.0 broke. A "Healthy" result does not mean your sessions work. Test reattach directly instead of trusting the check.

*Sources: GitHub issue github/app#5743, November 13, 2026 ([https://github.com/github/app/issues/5743](https://github.com/github/app/issues/5743)); GitHub Copilot releases 1.4.0, 1.4.1 and 1.4.2 ([https://github.com/github/app/releases](https://github.com/github/app/releases)).*

*Read the full guide on DebugRadar: [Fix: Copilot 1.4.0 Session Unavailable Error](https://debugradar.com/fix-copilot-1-4-0-session-unavailable-error/)*
