Desktop: suggested-task chip truncates IP-address remote label at the first dot — "Start on deploy@65"

Summary

In the desktop app, on a remote SSH session whose target is a bare IPv4 address, the "Suggested task" chip (created by the agent's spawn_task session tool) renders its action button as Start on deploy@65 — the remote user@IP truncated at the first dot.

The label logic appears to apply FQDN-style shortening — keep only the first dot-separated label, so web01.internal.example → web01 — to the remote host string. Applied to an IPv4 address, that keeps just the first octet, which reads as nonsense.

Steps to reproduce

1. Desktop app → environment dropdown → + Add SSH connection, with SSH Host set to a bare IPv4 target, e.g. user@203.0.113.7.
2. Start a session on that remote and have the agent call the spawn_task session tool so a "Suggested task" chip pops up.
3. The chip reads Start on user@203.

Expected: Start on user@203.0.113.7 — or better, the connection's friendly Name from the sshConfigs entry when one is set.

Observed environment

• Desktop app; remote SSH session (isRemote: true) to an Ubuntu 24.04 host addressed as deploy@65.… (bare IPv4) — chip showed Start on deploy@65.
• Remote-side Claude Code CLI: 2.1.247.

Suggested fix

• Skip first-label shortening when the host parses as an IP address (IPv4; IPv6 has no dots so it is presumably unaffected).
• And/or prefer the sshConfigs entry's name for display surfaces like this chip.

Cosmetic as far as observed — the spawned task targets the correct remote; only the label is wrong.

🤖 Filed with Claude Code on the user's behalf.