claudelink-bridge 0.1.2 → 0.1.4
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 +121 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -64,13 +64,104 @@ Download from the [latest GitHub release](https://github.com/devops-monk/claude-
|
|
|
64
64
|
|
|
65
65
|
---
|
|
66
66
|
|
|
67
|
-
## Auto-start
|
|
67
|
+
## Auto-start setup by platform
|
|
68
68
|
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
69
|
+
Running `npx claudelink-bridge setup` does everything automatically. Here's what happens on each platform and how to verify it worked.
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
|
|
73
|
+
### macOS
|
|
74
|
+
|
|
75
|
+
`setup` creates a **launchd plist** and loads it immediately. The bridge will start automatically every time you log in.
|
|
76
|
+
|
|
77
|
+
```bash
|
|
78
|
+
npx claudelink-bridge setup
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
**Verify it's running:**
|
|
82
|
+
```bash
|
|
83
|
+
npx claudelink-bridge status
|
|
84
|
+
# or check directly:
|
|
85
|
+
launchctl list | grep claudelink
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
**View logs:**
|
|
89
|
+
```bash
|
|
90
|
+
tail -f ~/.claudelink/bridge.log
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
**If it stops unexpectedly:**
|
|
94
|
+
```bash
|
|
95
|
+
launchctl unload ~/Library/LaunchAgents/com.devops-monk.claudelink.plist
|
|
96
|
+
launchctl load ~/Library/LaunchAgents/com.devops-monk.claudelink.plist
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
**Config file location:** `~/Library/LaunchAgents/com.devops-monk.claudelink.plist`
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
### Linux
|
|
104
|
+
|
|
105
|
+
`setup` creates a **systemd user service** and enables it so it starts on login. No root/sudo required.
|
|
106
|
+
|
|
107
|
+
```bash
|
|
108
|
+
npx claudelink-bridge setup
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
**Verify it's running:**
|
|
112
|
+
```bash
|
|
113
|
+
npx claudelink-bridge status
|
|
114
|
+
# or check directly:
|
|
115
|
+
systemctl --user status claudelink
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
**View live logs:**
|
|
119
|
+
```bash
|
|
120
|
+
journalctl --user -u claudelink -f
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
**If it stops unexpectedly:**
|
|
124
|
+
```bash
|
|
125
|
+
systemctl --user restart claudelink
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
**Lingering (start on boot without login):** If you want the bridge to run even when you're not logged in interactively:
|
|
129
|
+
```bash
|
|
130
|
+
loginctl enable-linger $USER
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
**Config file location:** `~/.config/systemd/user/claudelink.service`
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
### Windows
|
|
138
|
+
|
|
139
|
+
`setup` creates a **Task Scheduler entry** that runs the bridge at login. Run this in **PowerShell** (no admin required):
|
|
140
|
+
|
|
141
|
+
```powershell
|
|
142
|
+
npx claudelink-bridge setup
|
|
143
|
+
```
|
|
144
|
+
|
|
145
|
+
**Verify it's running:**
|
|
146
|
+
```powershell
|
|
147
|
+
npx claudelink-bridge status
|
|
148
|
+
# or check directly in Task Scheduler:
|
|
149
|
+
schtasks /Query /TN ClaudeLinkBridge
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
**View logs:**
|
|
153
|
+
```powershell
|
|
154
|
+
Get-Content "$env:USERPROFILE\.claudelink\bridge.log" -Wait
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
**If it stops unexpectedly:**
|
|
158
|
+
```powershell
|
|
159
|
+
schtasks /Run /TN ClaudeLinkBridge
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
**Manually open Task Scheduler** to verify: press `Win+R` → type `taskschd.msc` → look for `ClaudeLinkBridge` in the task list.
|
|
163
|
+
|
|
164
|
+
**Config:** Task Scheduler entry named `ClaudeLinkBridge`, visible in Task Scheduler Library.
|
|
74
165
|
|
|
75
166
|
---
|
|
76
167
|
|
|
@@ -128,6 +219,30 @@ npx claudelink-bridge setup # re-registers the service
|
|
|
128
219
|
|
|
129
220
|
---
|
|
130
221
|
|
|
222
|
+
## Changelog
|
|
223
|
+
|
|
224
|
+
### 0.1.3
|
|
225
|
+
- Expanded platform setup docs with per-platform verify, log, and restart steps
|
|
226
|
+
|
|
227
|
+
### 0.1.2
|
|
228
|
+
- Added full README with quick-start, commands, platform setup, troubleshooting, and security sections
|
|
229
|
+
- Added `repository`, `homepage`, `bugs` metadata to package
|
|
230
|
+
- Added `files` whitelist — cleaner published package
|
|
231
|
+
|
|
232
|
+
### 0.1.1
|
|
233
|
+
- Initial README added
|
|
234
|
+
|
|
235
|
+
### 0.1.0
|
|
236
|
+
- Initial release
|
|
237
|
+
- WebSocket bridge server on `localhost:9999`
|
|
238
|
+
- Streams Claude Code CLI responses token by token
|
|
239
|
+
- Auto-start service installer for macOS (launchd), Linux (systemd), Windows (Task Scheduler)
|
|
240
|
+
- `setup`, `start`, `stop`, `status`, `kill`, `uninstall` commands
|
|
241
|
+
- Handles screenshots as base64 inline images for Claude
|
|
242
|
+
- 50MB max payload for large screenshots
|
|
243
|
+
|
|
244
|
+
---
|
|
245
|
+
|
|
131
246
|
## Links
|
|
132
247
|
|
|
133
248
|
- [ClaudeLink Chrome Extension](https://github.com/devops-monk/claude-link)
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claudelink-bridge",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.4",
|
|
4
4
|
"description": "Bridge your browser to Claude Code CLI. The local server for the ClaudeLink Chrome extension — send screenshots, page content, and custom commands from any webpage directly to Claude Code.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|