bridge-agent 0.1.0-beta.0 → 0.1.0-beta.2

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
@@ -1,6 +1,12 @@
1
1
  # bridge-agent
2
2
 
3
- Bridge local agent connects your AI tools to Jerico
3
+ Connects your local AI tools (Claude Code, Qwen CLI, Kimi, Codex, etc.) to Jerico — a browser-based multi-agent orchestration platform.
4
+
5
+ ## Requirements
6
+
7
+ - Node.js >= 20
8
+ - A running Jerico server
9
+ - AI agents you want to use (each must be installed and authenticated)
4
10
 
5
11
  ## Installation
6
12
 
@@ -8,59 +14,117 @@ Bridge local agent — connects your AI tools to Jerico
8
14
  npm install -g bridge-agent
9
15
  ```
10
16
 
11
- ## Usage
17
+ ## Quick Start
12
18
 
13
19
  ### 1. Authenticate
14
20
 
15
- Get a token from your Jerico server (Settings → Daemon Tokens), then:
21
+ Get a daemon token from your Jerico server (**Settings → Daemon Tokens**), then:
16
22
 
17
23
  ```bash
18
24
  bridge-agent auth --server https://your-server.com --token YOUR_TOKEN
19
25
  ```
20
26
 
21
- Or with interactive browser flow:
27
+ For interactive browser flow (opens your default browser):
22
28
 
23
29
  ```bash
24
30
  bridge-agent auth --server https://your-server.com
25
31
  ```
26
32
 
27
- ### 2. Start the Daemon
33
+ ### 2. Start
28
34
 
29
35
  ```bash
30
36
  bridge-agent start
31
37
  ```
32
38
 
33
39
  The daemon will:
34
- - Connect to your Jerico server via WebSocket
35
- - Detect installed AI agents (Claude, Qwen, Kimi, etc.)
36
- - Allow spawning terminals from the web interface
40
+ - Connect to the Jerico server via WebSocket
41
+ - Auto-detect installed AI agents on your machine
42
+ - Spawn PTY sessions for terminal emulation
43
+ - Report usage metrics (Claude context window, 5h prompt quota)
44
+
45
+ ### 3. Done — open Jerico in your browser
46
+
47
+ Your machine will appear in the Machines page. Spawn panels and orchestrate agents from the web UI.
48
+
49
+ ## Commands
50
+
51
+ | Command | Description |
52
+ |---|---|
53
+ | `bridge-agent start` | Start the daemon (connects to server from config) |
54
+ | `bridge-agent auth [options]` | Authenticate with a Jerico server |
55
+ | `bridge-agent status` | Show current connection status and config |
56
+
57
+ ## Auth Options
58
+
59
+ ```
60
+ --server, -s Jerico server URL (required)
61
+ --token, -t Daemon token (skip browser flow)
62
+ --no-browser Print auth URL instead of opening browser
63
+ ```
64
+
65
+ ## Configuration
66
+
67
+ Config is stored at `~/.bridge/config.json`:
68
+
69
+ ```json
70
+ {
71
+ "server": "wss://your-server.com/ws/daemon",
72
+ "token": "brg_...",
73
+ "name": "my-machine"
74
+ }
75
+ ```
37
76
 
38
- ### 3. Check Status
77
+ ### Claude Quota Tracking
78
+
79
+ Set your Claude tier in `~/.jerico/settings.json`:
80
+
81
+ ```json
82
+ {
83
+ "claudeTier": "pro"
84
+ }
85
+ ```
86
+
87
+ Supported tiers: `free` (10 prompts/5h), `pro` (40), `max_5x` (200), `max_20x` (200)
88
+
89
+ ### MCP Server (Production)
90
+
91
+ In production, set `BRIDGE_MCP_URL` to enable HTTP MCP transport:
39
92
 
40
93
  ```bash
41
- bridge-agent status
94
+ BRIDGE_MCP_URL=https://your-server.com bridge-agent start
42
95
  ```
43
96
 
44
97
  ## Supported Agents
45
98
 
46
- - **Claude Code** (`claude`) - Requires `claude` CLI
47
- - **Qwen CLI** (`qwen`) - Requires `qwen` CLI
48
- - **Kimi Code** (`kimi`) - Requires `kimi` CLI
49
- - **Codex CLI** (`codex`) - Requires `codex` CLI
50
- - **Gemini** (`gemini`) - Requires `gemini` CLI
51
- - **Ollama** (`ollama`) - Requires `ollama`
52
- - **Aider** (`aider`) - Requires `aider`
53
- - **Shell** (`sh`) - System shell (always available)
99
+ | Agent | Key | Notes |
100
+ |---|---|---|
101
+ | Claude Code | `claude` | MCP + session support |
102
+ | Qwen CLI | `qwen` | MCP + session support |
103
+ | Kimi Code | `kimi` | MCP + session support |
104
+ | Codex CLI | `codex` | MCP enabled |
105
+ | Gemini | `gemini` | CLI only |
106
+ | Ollama | `ollama` | CLI only |
107
+ | Aider | `aider` | MCP enabled |
108
+ | Shell | `sh` | Always available |
54
109
 
55
- ## Configuration
110
+ ## Troubleshooting
56
111
 
57
- Config is stored in:
58
- - macOS/Linux: `~/.bridge/config.json` or `~/.jerico/settings.json`
112
+ **Daemon not connecting?**
113
+ ```bash
114
+ bridge-agent status
115
+ # Check server URL and token are correct
116
+ ```
59
117
 
60
- ## Requirements
118
+ **Need to re-authenticate?**
119
+ ```bash
120
+ bridge-agent auth --server https://your-server.com --token YOUR_NEW_TOKEN
121
+ ```
61
122
 
62
- - Node.js >= 20
63
- - For each AI agent: the respective CLI tool installed and authenticated
123
+ **View logs:**
124
+ The daemon outputs to stdout. Redirect to a file if needed:
125
+ ```bash
126
+ bridge-agent start > ~/bridge-daemon.log 2>&1 &
127
+ ```
64
128
 
65
129
  ## License
66
130