[Bug] SSH remote session only visible on the initiating Mac — not on the Mac that actually runs it
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
提交前确认 · Pre-submission checklist
- I searched existing issues and confirmed this isn't a duplicate.
- I've read CONTRIBUTING.md.
问题类别 · Category
UI / 界面体验 · UI / UX
涉及的 Agent 框架 · Agent framework
ZCode Agent(自研)
严重程度 · Severity
影响体验 · Major (功能可用但体验受损 / works but degraded)
复现频率 · Reproducibility
必现 · Always
问题描述 · Description
Sessions started via the SSH remote feature are only visible on the machine that initiated them, never on the machine that actually runs them.
My setup: a workhorse MacBook at home (always plugged in, running ZCode) and a travel MacBook. From the travel MacBook I start ZCode sessions on the workhorse over SSH. Those sessions appear only in the session list of the travel MacBook. On the workhorse itself — the machine executing the session — the session does not appear anywhere: not in the session list, not in the group/paired-devices view.
So when I am physically at the workhorse, I cannot open, monitor, or continue a session that the machine is already running. The session is invisible exactly on the machine doing the work.
Workarounds already tried, per suggestions in the Discord support thread:
- "group" view → the remote-started session does not appear there.
- Pairing with Telegram → works, but not a good option for coding work.
复现步骤 · Steps to reproduce
- On MacBook B ("workhorse"), have ZCode running and signed in.
- From MacBook A, start a ZCode session on MacBook B via the SSH remote feature.
- Let the session run (agent actively processing on B).
- Sit down at MacBook B and open the ZCode session list, then the group view.
- The remote-started session is listed on neither — it exists only in the session list on MacBook A.
期望表现 · Expected behavior
A session running on MacBook B should also be visible and openable on MacBook B itself, so I can check its progress and continue it locally when I'm at that machine.
实际表现 · Actual behavior
The session is only visible in the session list of the initiating machine (A). Machine B, which is actually executing the session, shows nothing — no entry in the session list, none in the group view.
ZCode 版本 · ZCode version
zcode-app-cli 3.11.2-25 / zcode-runtime 0.16.5
设备 / 系统 / 浏览器 · Device / OS / Browser
2× MacBook (Apple Silicon), macOS 26.x. Same repro on every attempt regardless of which machine initiates.
截图 / 录屏 / 日志 · Screenshots / Recordings / Logs
Screen recordings of the repro are available and can be attached on request; debug logs can be provided too if useful.
Context: discussed in the official ZCode Discord support thread ("Any way to locally check a session that was started remotely?"); staff suggested escalating here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the SSH remote session flow between two Apple Silicon Macs, then inspect the session list and group/paired-devices view on the executing Mac. Use the reported zcode-app-cli 3.11.2-25 and zcode-runtime 0.16.5 versions, with debug logs if needed. Done means a session started remotely on Mac B is visible, openable, and continuable there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100