Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

bug: ssh to a multi-agent workspace from CLI is unintuitive #19812

Closed
Assignees
kacpersaw
Labels
cliArea: CLIs2Broken use cases or features (with a workaround). Only humans may set this.
@matifali

Description

@matifali

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When I try to SSH into my workspace with multiple agents. It does not provide an intuitive way to do that successfully and instead misguides by printing wrong instructions.

Relevant Log Output

$ coder lsWORKSPACE           TEMPLATE  STATUS   HEALTHY  LAST BUILT  CURRENT VERSION  OUTDATED  STARTS AT                      STOPS AFTER★ matifali/dogfood  coder     Startedtrue     2h52m       3ac36b8false     9:30AM Mon-Fri (Asia/Karachi)  12h$ coder config-ssh> The following changes will be made to your SSH configuration:* Update the coder sectionin /Users/matifali/.ssh/config  Continue? (yes/no) yesUpdated"/Users/matifali/.ssh/config"You should now be able to ssh into your workspace.For example, try running:        $ ssh dogfood.coder$ ssh dogfood.coderEncountered an error running"coder ssh", see"coder ssh --help"for more informationerror: multiple agents found, please specify the agent name, available agents: [coder dev]

Expected Behavior

CLI should provide a clear example of how to SSH into a workspace.
I would expect instructions like

error: multiple agents found, please specify the agent name, available agents: [coder dev]Try running:        $ ssh dev.dogfood.me.coder        $ ssh coder.dogfood.me.coder

Steps to Reproduce

  1. Runcoder config-ssh
  2. Follow instructions and runssh <workspace>
  3. Follow instructions and try to guess the correct format to connect to a workspace with multiple agents.

Environment

Additional Context

I have tested this on the latest version, The issue happens on multiple deployments, The issue occurs consistently

Metadata

Metadata

Assignees

Labels

cliArea: CLIs2Broken use cases or features (with a workaround). Only humans may set this.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp