Unclear It is not clear where the monorepo setting comes from or what sets it.
When claude --remote starts a cloud session, Claude Code can offer to sync your local directory to it. Sometimes that offer is put off because the anchor it needs is unavailable. In that case, its explanation is now added to the warning notices shown for the session. Before, only the notices from creating the session itself were shown, and this one was dropped without a word.
The sync offer and the session creation also both receive a monorepo setting now. A monorepo is a single repository that holds several projects.
You are now told why directory sync was not offered, instead of seeing nothing.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
To bring back a session you started with `claude --remote-control` or `/remote-control`, resume the conversation with `claude --continue` or `claude --resume`. For the permission mode that the resumed conversation starts in, see [permissio…remote-control see the edit
| `--push` | Push the tag to `--remote` after creating it |plugins/cli-reference see the edit
It is not clear where the monorepo setting comes from or what sets it.
Anthropic's documentation has since written up --remote, on Plugin commands reference.