@yu_robotics/remote-cli 1.6.11 → 1.6.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,6 +8,7 @@ Remote control your [Claude Code](https://claude.ai/code) CLI from anywhere usin
|
|
|
8
8
|
- **Secure**: Directory whitelisting, command filtering, and device authentication
|
|
9
9
|
- **Mobile-Optimized**: Simplified commands and rich text formatting for Feishu
|
|
10
10
|
- **Multi-Backend Support**: Supports Claude Code and Gemini CLI
|
|
11
|
+
- **Image Input**: Forward Feishu images to Claude Persistent and Codex App Server backends
|
|
11
12
|
- **Multi-session (Threads)**: Create independent chat threads to parallelize tasks
|
|
12
13
|
- **Remote Machine Management**: Control remote servers or Docker via SSH
|
|
13
14
|
- **Persistent Process**: Long-running AI process with bidirectional streaming
|
|
@@ -18,6 +19,8 @@ Remote control your [Claude Code](https://claude.ai/code) CLI from anywhere usin
|
|
|
18
19
|
- **Claude Code CLI** installed and configured
|
|
19
20
|
- Access to a Feishu (Lark) bot connected to a [remote-cli-router](https://www.npmjs.com/package/@yu_robotics/remote-cli-router) server
|
|
20
21
|
|
|
22
|
+
The client is normally installed and run directly on the developer's machine rather than in Docker, so it can access local project directories and the installed AI CLI binaries. Docker is recommended for the shared Router server instead.
|
|
23
|
+
|
|
21
24
|
## Installation
|
|
22
25
|
|
|
23
26
|
```bash
|
|
@@ -113,6 +116,27 @@ All commands/skills supported by local Claude Code or Gemini CLI are passed thro
|
|
|
113
116
|
- `/test` - Run tests
|
|
114
117
|
- And all other built-in AI engine commands
|
|
115
118
|
|
|
119
|
+
## Advanced Usage
|
|
120
|
+
|
|
121
|
+
Use one thread per project or task so each thread keeps its own working directory, backend session, model, and queue. Use `/backend <index>` for a global switch, or `/backend <index> @` to override only the current thread. `/backend default @` removes that override.
|
|
122
|
+
|
|
123
|
+
When a thread is busy, ordinary messages require confirmation before they enter its queue. Use `/queue` to inspect pending work, `/queue clear` to discard queued messages, and `/abort` to stop the active task and clear that thread's queue. Context-changing commands such as `/model`, `/effort`, `/cd`, `/compact`, and `/clear` are handled separately rather than queued as ordinary messages.
|
|
124
|
+
|
|
125
|
+
## Expert Usage
|
|
126
|
+
|
|
127
|
+
For a shared deployment, run the Router with Docker Compose on an internal server and run one CLI client on each developer machine. Keep project directories and Claude Code, AGY, or Codex credentials on the client machine; the Router persists its configuration and bindings in `./router-data`.
|
|
128
|
+
|
|
129
|
+
To update a Router deployment without losing bindings:
|
|
130
|
+
|
|
131
|
+
```bash
|
|
132
|
+
git pull --ff-only
|
|
133
|
+
docker compose build --pull
|
|
134
|
+
docker compose up -d
|
|
135
|
+
docker compose logs --tail=100 router
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
When diagnosing a task, check `/status`, then `/context`, then `/queue`. Use `/abort` only when you intend to discard the active task and queued messages.
|
|
139
|
+
|
|
116
140
|
## Security
|
|
117
141
|
|
|
118
142
|
- **Directory whitelisting**: Only explicitly allowed directories are accessible
|
|
@@ -127,3 +151,7 @@ For full documentation including router server deployment, see the [project READ
|
|
|
127
151
|
## License
|
|
128
152
|
|
|
129
153
|
MIT
|
|
154
|
+
|
|
155
|
+
## Changelog
|
|
156
|
+
|
|
157
|
+
See the project [CHANGELOG.md](../../CHANGELOG.md) for release notes and user-visible changes.
|