microsoft / microsoft/vscode

test: remote agent host connection diagnostics

Open
#336,852 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

testplan-item
Dominant language
TypeScript
Stars
193k
Forks
42.7k
PR merge metrics
PR metrics pending

Description

Refs: #336443, #336487

  • web
  • web (mobile)

Complexity: 3

Authors: @amunger


Verify that remote Agent Host connection state and diagnostic evidence are actionable and accurate in the web Agents Window, including its mobile layout.

Feel free to create issues around connectivity problems that come up during testing, but this is mostly about enabling us to troubleshoot those issues through the collected diagnostics, especially on mobile, where logs are much more difficult to see.

Set up

  1. Make sure you have at least one remote agent host enabled
    a. with CLI: code-insiders agent --tunnel
    b. in agents window: click the "allow connections..." button in the top right

Testing

  1. Open insiders.vscode.dev/agents (or even better, download/open the PWA on mobile)
  2. click the info icon to see the diagnostic view of the remote connections (within the host list on mobile)
Image
  1. try to transfer that information into a chat session and see if the agent has context to diagnose questions you have

e.g. "why is ... not connected?", "how long does it take to connect to my dev tunnel?"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use a build containing #336443 and #336487, open the web Agents Window at /agents, and enable chat.remoteAgentHostsEnabled. Verify that remote Agent Host connection state and diagnostic evidence are understandable and accurate in the web layout and in mobile or phone emulation; completion means both checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.