zchee / zchee/ganja-code

Reconsidering the Remote Control probe on the claude-code wire

Open
#101 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

idea
Dominant language
Rust
Stars
2
Forks
0
Avg merge
1h
Merged PRs (30d)
17

Description

What it does

Reopens the question of whether ganja's claude-code wire (D556) should ask Claude Code's own Remote Control to start for its claude child, so that a ganja session can be reached from Anthropic's remote clients. The idea is the one recorded in #68, which was dropped on 2026-09-19.

The open questions the probe was meant to answer are: whether a control_request of subtype remote_control succeeds on a -p stream-json child, what the session URL looks like, whether Anthropic's apps list the session, and what the child prints on stdout when an app sends a prompt (replayed user messages would have to be adopted into ganja's session store).

Source

ganja-code-7gjf (probe Remote Control on the claude-code wire), closed on 2026-09-19 with its external reference at #68. The owner asked on 2026-09-20 to reconsider the verdict.

This issue is a new question and does not reopen the bead: beads carry work, and ideas live on GitHub issues (#37, #38).

File and line references in this issue are to main as of 22ad864.

Against the three criteria

  • Direction (README): Remote access sits near the README's control-plane direction (README.md:16-18), but the README does not name Remote Control.
  • Today's terminal users: A user could reach a running session from another device without ganja serve. Today the road that exists for that is serve and attach, in the theme "Serve, attach and remote access" (#52).
  • Evidence: Nothing in the tree implements it. The reasons recorded for the drop were the token and identity risk (D521): a native worker for this protocol was refused because ganja would have to hold a vendor's OAuth token and present a borrowed identity. The probe road avoids both, because the token stays inside the unmodified claude binary and ganja only sends one control request. The reasons for reconsidering are the owner's to add in a comment; the comment below records the facts read while reopening the question.

Depends on

Nothing.

Verdict

  • Verdict: none yet. Verdicts are the captain's (#36), so this issue carries idea and no verdict:* label until the owner rules.
  • Earlier verdict: drop on 2026-09-19 (#68, verdict ticket #46). #68 stays closed. If this issue ends in a different verdict, it supersedes #68.
  • Size or reopening condition or reason: to be set with the verdict.
  • Date opened: 2026-09-20

Theme: #52

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

No implementation file or test is named; start with README.md:16-18, then read the closed ganja-code-7gjf probe and #68. Investigate the listed Remote Control questions on the claude-code wire, including the -p stream-json behavior and session handling. Done means recording the evidence and obtaining the captain's verdict.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.