Issue handling problem: bug still in main, fix PR ignored, no one assigned

@microsoft/vscode @Yoyokrazy @benvillalobos @roblourens @connor4312 @joshspicer @mjbvz @mrleemurray @benibenj @bpasero @Tyriar @lszomoru @sandy081 @osortega

I am opening this issue because the way #333154 and #333155 were handled does not make sense.

This is separate from the bug itself.

## What happened

#333154 reports a VS Code core bug. The report includes:

- clear steps to show the bug;
- the saved value that causes it: `chat.userSelectedSessionType`;
- the exact code path in VS Code;
- the exact condition that causes the wrong result;
- a small fix;
- tests for the fix;
- and PR #333155.

The report also says the same problem exists in the current `main` code.

But the only reply on #333154 was an automatic message saying that VS Code 1.135.0 was newer and asking the reporter to update and try again.

That reply did not answer the report. The report was not only about an old build. It already pointed to the code in `main` and included a fix PR with tests.

## Then the assigned person removed their assignment

The issue history shows this:

1. On August 28, 2026, `vs-code-engineering[bot]` assigned @joshspicer to #333154.
2. No maintainer posted a technical review of the bug or PR.
3. On September 3, 2026, @joshspicer removed their assignment:
https://github.com/microsoft/vscode/issues/333154#event-30521735793
4. No one else was assigned after that.
5. #333154 stayed open.
6. #333155 stayed open and was not merged.

Removing an assignment can be normal. The problem is that no one else took the issue, no review was posted, and no reason was given for leaving the bug and PR as they were.

## The bug is still in `main`

The code in `main` still keeps the saved Agent Host choice before the Local default in this case.

So when this value is saved:

```text
chat.userSelectedSessionType = agent-host-copilotcli
```

new chats can still keep using Agent Host even after the user changes the settings back to Local.

That is the bug reported in #333154.

If this has already been fixed by another change, please link the exact PR or commit that fixed it.

## Why I am reporting this

I do not expect every PR to be merged quickly.

I do expect a bug report with clear steps, the exact code, a fix, and tests to get a real answer.

What happened here was:

1. bug reported;
2. bug found in VS Code code;
3. fix PR sent with tests;
4. report says the bug is also in `main`;
5. bot says to update to a newer version;
6. a person is assigned;
7. no technical review is posted;
8. that person removes their assignment;
9. no one else is assigned;
10. issue and PR stay open with no clear answer.

This is the part I am asking the project owners to look at.

## What I am asking for

Please give a clear answer for #333154 and #333155:

1. Is the bug real?
2. If it is already fixed, which PR or commit fixed it?
3. If #333155 is wrong, what is wrong with it?
4. If the current behavior is wanted, please say so and explain why.
5. Why was #333154 left with no one assigned after @joshspicer removed their assignment?
6. Should the bot tell people to update when the report already says the same bug exists in `main` and already links a fix PR?
7. If there is a better public place to report problems with how VS Code issues are handled, please link it.

I am asking for a clear review and a clear answer.