Skip to content

Workspace DNS routing behavior with multiple agents #19056

@blink-so

Description

@blink-so

Problem

Coder Desktop changed workspace addressing behavior when devcontainers are involved. Previously <workspace>.coder worked, but now requires dev.<workspace>.me.coder format.

Current Behavior

  • Coder Desktop doesn't program <workspace>.coder when it would be ambiguous (multiple agents)
  • Forces use of more specific addressing like dev.<workspace>.me.coder

Technical Constraint

If both workspace and devcontainer used the same hostname, their SSH server host keys would need to match. This creates complications depending on whether the devcontainer is running or not, as users would encounter different SSH fingerprints for the same hostname.

Discussion Points

  1. Routing Logic: When there's exactly one regular agent and one sub-agent, should requests route to:

    • Sub-agent (Matthias's suggestion)
    • Parent agent (team consensus: Ethan, Danny, Danielle prefer this)
  2. Principle of Least Surprise: Team agrees parent agent routing would be less surprising to users

Context

Original discussion: https://codercom.slack.com/archives/C07GPPG05UN/p1749577514699789

Team Consensus

Majority prefers routing to parent agent for predictability and user experience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions