Remote Control boxes: a manifest permission mode, and moving a running box's session into Remote Control

Open
#285 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start in wicket_agent::claude_code_remote_control_plan, which hard-codes --permission-mode default, and read the manifest's agent.remote settings and the adapter Mode from #255. The permission mode should come from agent.remote.permission_mode, with default for human-driven sessions. Done when a Remote Control box with bypassPermissions runs unattended and shows in the app, and the session-move option is either built or documented as impossible. Depends on #169's live check, so confirm that first.

Written by the indexing model from the issue text.

Description

Running wicket's own development in boxes, every box should be a Remote Control session the owner can watch and steer from the Claude app. Two gaps:

1. Permission mode. The Remote Control plan (wicket_agent::claude_code_remote_control_plan) hard-codes --permission-mode default, so Claude Code asks in the app before each action and an unattended box stalls on prompts nobody is watching. wicket's proxies decide what the box can reach either way, as for the driven mode's bypassPermissions. claude remote-control takes --permission-mode (acceptEdits, auto, bypassPermissions, default, dontAsk, plan): take it from the manifest (agent.remote.permission_mode, default default for a human-driven session), through the Claude adapter (#255), so other harnesses map or refuse it.

2. Move a running session into Remote Control. A box started driven (claude -p) can't become a Remote Control session: claude remote-control --continue and --session-id reattach only to sessions Remote Control recorded itself. Today the only way is to stop the box and start a new one, losing the conversation. Options to evaluate:

  • hibernate the driven box (its Claude session files are in the bundle) and wake it in the remote mode, resuming the same session id, if Claude Code can start a Remote Control session from an existing session's transcript;
  • an operator command (wicket remote <run>) that does that hibernate-and-wake in one step, keeping the box's identity, grants and volumes;
  • if Claude Code can't resume into Remote Control, say so in the docs and make remote the default mode for long-lived boxes instead.

Harness-agnostic: modes are per adapter (#255's Mode); an adapter without a remote mode refuses the switch.

Done when. A Remote Control box with permission_mode: bypassPermissions works unattended and shows in the app; a running driven box is moved into Remote Control with its conversation, or the docs say why it can't be and remote is the default for long-lived boxes. Depends on #169's live check.

Dominant language
Rust
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
190

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from public/wicket

All issues in public/wicket

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.