anthropics / anthropics/claude-code

[FEATURE] Show Remote Control sessions in the `claude agents` view (follow-up to #77720)

Open
#95,581 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:agent-view enhancement platform:linux
Dominant language
TypeScript
Stars
147k
Forks
24k
PR merge metrics
PR metrics pending

Description

Problem

Sessions started through Remote Control (claude remote-control, spawned from the mobile app or claude.ai) never appear in the claude agents terminal view. They do appear in the mobile app and in Claude Desktop, so the terminal is the only surface where they are missing.

This is a follow-up to #77720, which asked for the same thing and was auto-closed as stale on 2026-09-18 without a response.

What I observed (Claude Code 2.1.278, Linux)
  • The sessions are registered locally: ~/.claude/sessions/<pid>.json has kind: "interactive", entrypoint: "sdk-cli", peerProtocol: 1, a fresh updatedAt, and a bridgeSessionId.
  • claude agents --json lists them.
  • The interactive claude agents view does not show them.
  • The view appears to already contain code for showing such sessions as "peer" rows, gated behind the tengu_fleetview_peers feature flag. With that flag forced on locally in 2.1.2xx (August), the rows did appear. In 2.1.278 they no longer appear even with the flag on, so this path seems unfinished or regressed.
Proposal

Show Remote Control sessions in the claude agents view, at least as read-only rows with status and the option to reply. That way all sessions on a machine can be seen in one place, matching what the mobile app and Desktop already show.

Environment
  • Claude Code 2.1.278
  • Ubuntu 26.04, KDE Plasma (X11)
  • Remote Control run as a systemd user service: claude remote-control --name <x> --spawn worktree

Contributor guide

No contributing guide indexed for this repository

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

Start by tracing the interactive claude agents view and its tengu_fleetview_peers feature-flag path, comparing it with the sessions returned by claude agents --json. Verify how Remote Control sessions are represented in ~/.claude/sessions/<pid>.json. Done means those sessions appear as read-only rows with status and an option to reply.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.