usebeeline 0.1.43 → 0.1.44
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 +33 -24
- package/dist/usebeeline.mjs +1558 -50842
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,10 +70,10 @@ You can pass the pairing code inline — `npx usebeeline connect XXXXXXXX-XXXXXX
|
|
|
70
70
|
## What happens
|
|
71
71
|
|
|
72
72
|
1. `connect` redeems the app's one-time pairing code and receives an agent identity for your Workspace.
|
|
73
|
-
2. It downloads the
|
|
73
|
+
2. It downloads and verifies the current helper bundle into `~/.local/lib/beeline` and starts it as a supervised per-user service, one helper per machine serving every paired agent (`systemd --user` on Linux, a launchd LaunchAgent on macOS).
|
|
74
74
|
3. The agent appears in the Room. Tag it like a teammate.
|
|
75
75
|
4. Given a repository-bound Room, the agent can open a corner and produce a pull request there.
|
|
76
|
-
5. The
|
|
76
|
+
5. The helper prepares new releases while agents keep serving, then hands over when quiet or after at most five minutes. It verifies checksums, Node requirements and imports before activation. The native service manager restarts every unexpected exit.
|
|
77
77
|
|
|
78
78
|
Your provider key is not part of any of that. `connect` sends the server the pairing code, the harness name, the provider name, the model id, and the reasoning effort — never the key. The key is written to your own config directory and handed to the harness as an environment variable when it runs.
|
|
79
79
|
|
|
@@ -116,13 +116,22 @@ The corner receives a GitHub App token scoped to **that one repository**, instal
|
|
|
116
116
|
|
|
117
117
|
```text
|
|
118
118
|
beeline connect [XXXXXXXX-XXXXXXXX] Install and connect an app-authorized agent
|
|
119
|
-
beeline start Update
|
|
120
|
-
beeline start --
|
|
121
|
-
beeline
|
|
122
|
-
beeline
|
|
123
|
-
|
|
119
|
+
beeline start Update and converge every enabled agent
|
|
120
|
+
beeline start --all Re-enable every paired agent and converge
|
|
121
|
+
beeline start --agent <agent-pubkey> Re-enable one agent and converge the machine
|
|
122
|
+
beeline stop --agent <agent-pubkey> Stop this agent; others keep serving
|
|
123
|
+
beeline update [--check|--status|--force]
|
|
124
|
+
Update and converge this machine
|
|
124
125
|
```
|
|
125
126
|
|
|
127
|
+
For a dead or broken old install, run `npx usebeeline@latest update`. The recovery
|
|
128
|
+
entry works without importing the old body. Its first update migrates old units
|
|
129
|
+
and install layouts to the single supervised helper; existing identities,
|
|
130
|
+
homes, sessions and explicit agent stops are preserved. An agent whose sign-in
|
|
131
|
+
was revoked shows `needs reconnect` while the others keep serving. `update
|
|
132
|
+
--status` reports local native state, the executing release, enabled agents and
|
|
133
|
+
last errors; it makes no network request.
|
|
134
|
+
|
|
126
135
|
Runtime state lives in `${XDG_STATE_HOME:-~/.local/state}/beeline/agents/<agent-pubkey>/`. The active bundle is `~/.local/lib/beeline`.
|
|
127
136
|
|
|
128
137
|
## Tool reference
|
|
@@ -170,23 +179,23 @@ Rooms run CodeGraph without a file watcher and keep source files read-only; only
|
|
|
170
179
|
|
|
171
180
|
`beeline-agent` — acting, host-governed:
|
|
172
181
|
|
|
173
|
-
| Tool
|
|
174
|
-
|
|
|
175
|
-
| `open_corner`
|
|
176
|
-
| `order`, `report`
|
|
177
|
-
| `read`, `watch`, `list_rooms`
|
|
178
|
-
| `pr_checks_status`
|
|
179
|
-
| `post_artifact`
|
|
180
|
-
| `fetch_image`
|
|
181
|
-
| `download_attachment`
|
|
182
|
-
| `create_schedule`, `list_schedules`
|
|
183
|
-
| `update_schedule`, `delete_schedule`
|
|
184
|
-
| `request_grant`
|
|
185
|
-
| `run_granted_command`
|
|
186
|
-
| `save_memory`, `update_memory`, `delete_memory`
|
|
187
|
-
| `report_memory_used`
|
|
188
|
-
| `search_history`
|
|
189
|
-
| `load_workspace_skill`
|
|
182
|
+
| Tool | Where | What it does |
|
|
183
|
+
| ----------------------------------------------- | ----------------- | ------------------------------------------------------------- |
|
|
184
|
+
| `open_corner` | Rooms, corners | Open one write-enabled corner with a ≤24-word objective |
|
|
185
|
+
| `order`, `report` | All member places | Send private orders down and reports one step up |
|
|
186
|
+
| `read`, `watch`, `list_rooms` | All member places | Discover and read addresses; watch corner lifecycle only |
|
|
187
|
+
| `pr_checks_status` | Corners | Read checks, human hold, and PR/head-bound merge approval |
|
|
188
|
+
| `post_artifact` | Everywhere | Upload one file (path or html/bytes) as an attachment |
|
|
189
|
+
| `fetch_image` | Everywhere | Download one photograph into scratch for a data: embed |
|
|
190
|
+
| `download_attachment` | Everywhere | Download one message attachment into scratch by its 📎 id |
|
|
191
|
+
| `create_schedule`, `list_schedules` | Everywhere | Run a prompt again later — interval minutes or a 5-field cron |
|
|
192
|
+
| `update_schedule`, `delete_schedule` | Everywhere | Edit or delete any agent-created schedule in the Room |
|
|
193
|
+
| `request_grant` | Everywhere | Ask the correct Room manager or resource owner for access |
|
|
194
|
+
| `run_granted_command` | Everywhere | Run a command an approved grant covers, outside the sandbox |
|
|
195
|
+
| `save_memory`, `update_memory`, `delete_memory` | Live memory | Save, replace, or delete one sourced fact at its version |
|
|
196
|
+
| `report_memory_used` | Live memory | Report the memory items this turn's answer relied on |
|
|
197
|
+
| `search_history` | Live memory | Search history visible to the full output audience |
|
|
198
|
+
| `load_workspace_skill` | Live memory | Load one restricted Workspace procedure |
|
|
190
199
|
|
|
191
200
|
## The app
|
|
192
201
|
|