@naarang/ccc 1.1.0-beta.2 → 1.1.0-beta.3

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 CHANGED
@@ -78,11 +78,11 @@ The server will start and display:
78
78
  ✓ Claude Chat Backend v1.1.0 started successfully
79
79
 
80
80
  Server URLs (Add one of these in the app settings):
81
- Localhost: localhost:8080
82
- Network: 192.168.1.100:8080
81
+ Localhost: localhost:8883
82
+ Network: 192.168.1.100:8883
83
83
 
84
84
  Services:
85
- MQTT: Port 8883 (via /mqtt)
85
+ MQTT: Port 8884 (via /mqtt)
86
86
  ```
87
87
 
88
88
  ### 2. Configure the Mobile App
@@ -115,12 +115,12 @@ Options:
115
115
  --debug Enable debug logging
116
116
  -u, --username <user> MQTT broker username
117
117
  -p, --password <pass> MQTT broker password
118
- --mqtt-port <port> Internal MQTT broker port (default: 8883)
118
+ --mqtt-port <port> Internal MQTT broker port (default: 8884)
119
119
  --port <port> [DEPRECATED] Use --mqtt-port instead
120
- --router-port <port> Router port for ngrok (default: 8080)
120
+ --router-port <port> Internal Request Router port. This is what the app connects to (default: 8883)
121
121
  --terminal-port <port> Internal terminal server port (default: 3001)
122
- --terminal-username <user> Terminal authentication username (enables terminal)
123
- --terminal-password <pass> Terminal authentication password (enables terminal)
122
+ --terminal-username <user> Terminal authentication username
123
+ --terminal-password <pass> Terminal authentication password
124
124
  -t, --ngrok-token <token> ngrok auth token (enables public tunnel)
125
125
  --ngrok-domain <domain> ngrok static domain
126
126
  --no-auto-update Disable automatic updates (enabled by default)
@@ -144,7 +144,11 @@ ccc -u admin -p secret
144
144
 
145
145
  **With terminal access (Beta):**
146
146
  ```bash
147
+ # Using separate terminal credentials
147
148
  ccc --terminal-username admin --terminal-password secret
149
+
150
+ # Or reuse MQTT credentials for terminal (if -u and -p are provided)
151
+ ccc -u admin -p secret # Terminal will also use these credentials
148
152
  ```
149
153
 
150
154
  **With ngrok for remote access:**
@@ -170,12 +174,12 @@ Create a `.env` file in your working directory:
170
174
 
171
175
  ```env
172
176
  # MQTT Configuration
173
- MQTT_BROKER_PORT=8883
177
+ MQTT_BROKER_PORT=8884
174
178
  MQTT_USERNAME=your-username
175
179
  MQTT_PASSWORD=your-password
176
180
 
177
181
  # Router Configuration
178
- ROUTER_PORT=8080
182
+ ROUTER_PORT=8883
179
183
 
180
184
  # Terminal Configuration (Beta)
181
185
  TERMINAL_PORT=3001
@@ -197,16 +201,29 @@ CCC now includes a built-in web terminal that can be accessed directly from the
197
201
 
198
202
  Terminal access is **opt-in** for security reasons. To enable it, you must provide authentication credentials:
199
203
 
204
+ **Option 1: Using separate terminal credentials**
200
205
  ```bash
201
206
  ccc --terminal-username admin --terminal-password your-secure-password
202
207
  ```
203
208
 
204
- Or via environment variables:
209
+ **Option 2: Reusing MQTT credentials** (fallback behavior)
210
+ ```bash
211
+ # Terminal will automatically use MQTT credentials if terminal-specific ones aren't provided
212
+ ccc -u admin -p your-secure-password
213
+ ```
214
+
215
+ **Option 3: Via environment variables**
205
216
  ```env
206
217
  TERMINAL_USERNAME=admin
207
218
  TERMINAL_PASSWORD=your-secure-password
219
+
220
+ # Or just set MQTT credentials
221
+ MQTT_USERNAME=admin
222
+ MQTT_PASSWORD=your-secure-password
208
223
  ```
209
224
 
225
+ > **Note:** If you don't provide any credentials (neither terminal-specific nor MQTT), the terminal server will not start.
226
+
210
227
  ### How It Works
211
228
 
212
229
  1. **Architecture:**
@@ -318,9 +335,9 @@ CCC offers four permission modes to balance convenience and security:
318
335
 
319
336
  When you start CCC, it:
320
337
 
321
- 1. **Starts MQTT Broker** - Embedded broker on port 8883 (localhost)
322
- 2. **Starts Path Router** - HTTP router on port 8080 proxying MQTT and terminal
323
- 3. **Starts Terminal Server** (Optional) - Web terminal on port 3001 if credentials provided
338
+ 1. **Starts MQTT Broker** - Embedded broker on port 8884 (localhost)
339
+ 2. **Starts Path Router** - HTTP router on port 8883 proxying MQTT and terminal
340
+ 3. **Starts Terminal Server** (Optional) - Web terminal on port 3001 if credentials provided (falls back to MQTT credentials)
324
341
  4. **Sets Up ngrok Tunnel** (Optional) - Public URL pointing to router
325
342
  5. **Sets Up Projects** - Auto-configures permission hooks
326
343
  6. **Manages Sessions** - Persistent sessions across disconnects
@@ -392,16 +409,19 @@ The CCC mobile app is required to interact with the backend.
392
409
 
393
410
  **Error: `EADDRINUSE: address already in use`**
394
411
 
395
- Another process is using port 8883:
412
+ Another process is using the default ports. Find and kill the process, or use different ports:
396
413
  ```bash
397
- # Find the process
414
+ # Find the process using router port (8883)
398
415
  lsof -i :8883
399
416
 
417
+ # Or MQTT port (8884)
418
+ lsof -i :8884
419
+
400
420
  # Kill it
401
421
  kill -9 <PID>
402
422
 
403
- # Or use a different port
404
- ccc --port 9000
423
+ # Or use different ports
424
+ ccc --router-port 9000 --mqtt-port 9001
405
425
  ```
406
426
 
407
427
  ### Connection Issues
@@ -411,8 +431,8 @@ ccc --port 9000
411
431
  **Checklist:**
412
432
  1. Check you're on the same WiFi network (for local)
413
433
  2. Verify server is running (`ccc` should show "started successfully")
414
- 3. Check firewall settings allow port 8080 (router) and 8883 (MQTT)
415
- 4. Use correct format: `hostname:port` (no `http://`)
434
+ 3. Check firewall settings allow port 8883 (router port that app connects to)
435
+ 4. Use correct format: `hostname:8883` (no `http://`)
416
436
  5. Enable debug mode: `ccc --debug`
417
437
 
418
438
  ### Permission Hook Errors
@@ -483,4 +503,38 @@ Make quick code changes without opening your laptop.
483
503
  Learn coding concepts by chatting with Claude from mobile.
484
504
 
485
505
  ### Pair Programming
486
- Co @naarang/ccc && ccc`
506
+ Collaborate with Claude on coding tasks remotely.
507
+
508
+ ## Comparison
509
+
510
+ ### vs Claude Web
511
+ - ✅ Mobile access
512
+ - ✅ Offline project access
513
+ - ✅ Real-time streaming
514
+ - ✅ Local file system access
515
+
516
+ ### vs Claude Desktop
517
+ - ✅ Mobile control
518
+ - ✅ Remote access
519
+ - ✅ Multi-device support
520
+ - ✅ Session persistence
521
+
522
+ ## Performance
523
+
524
+ - **Startup Time**: ~2 seconds
525
+ - **Response Latency**: <100ms (local network)
526
+ - **Concurrent Sessions**: Unlimited
527
+ - **Memory Usage**: ~150MB (varies with active sessions)
528
+
529
+ ## Support & Community
530
+
531
+ - **Issues**: Report bugs and request features
532
+ - **Discussions**: Ask questions and share ideas
533
+ - **Updates**: Check npm for latest version
534
+ - **Contact**: Email us at cccuiapp@gmail.com
535
+
536
+ **Made with ❤️ by naarang**
537
+
538
+ > **Note**: This tool requires an active Claude subscription and Claude Code to function properly.
539
+
540
+ **Get Started:** `npm install -g @naarang/ccc && ccc`