usebeeline 0.0.90 → 0.0.92
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 +6 -3
- package/dist/usebeeline.mjs +677 -298
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -39,7 +39,7 @@ On any machine that already runs your coding agents:
|
|
|
39
39
|
npx usebeeline connect
|
|
40
40
|
```
|
|
41
41
|
|
|
42
|
-
The command asks for the pairing code shown in the Beeline app, then
|
|
42
|
+
The command asks for the pairing code shown in the Beeline app, then five questions and no more:
|
|
43
43
|
|
|
44
44
|
| Step | What it asks |
|
|
45
45
|
| -------- | ----------------------------------------------------------------------------------------------------------------- |
|
|
@@ -47,6 +47,9 @@ The command asks for the pairing code shown in the Beeline app, then four questi
|
|
|
47
47
|
| Provider | Goose and Pi only — OpenRouter (default), OpenAI, Anthropic, Google, or xAI |
|
|
48
48
|
| API key | Goose and Pi only — verified against the provider, then saved to `~/.config/beeline/providers.json` (mode `0600`) |
|
|
49
49
|
| Model | Whatever the harness advertises, filtered as you type; OpenRouter defaults to GLM 5.3 Flash |
|
|
50
|
+
| Effort | The reasoning effort your harness advertises for that model; skipped by a harness that has no such setting |
|
|
51
|
+
|
|
52
|
+
A harness that is already set up answers the provider and key questions itself, but model and effort are still asked, with its own current settings pre-selected.
|
|
50
53
|
|
|
51
54
|
It does **not** ask for a name or a soul. The server assigns the agent one of twelve animals nobody in your Workspace is already wearing, and prints it:
|
|
52
55
|
|
|
@@ -72,7 +75,7 @@ You can pass the pairing code inline — `npx usebeeline connect XXXXXXXX-XXXXXX
|
|
|
72
75
|
4. Given a repository-bound Room, the agent can open a corner and produce a pull request there.
|
|
73
76
|
5. The daemon updates itself when a new release ships, draining any turn in flight first, and rolls back if the new bundle cannot answer.
|
|
74
77
|
|
|
75
|
-
Your provider key is not part of any of that. `connect` sends the server the pairing code, the harness name, the provider name,
|
|
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.
|
|
76
79
|
|
|
77
80
|
## Rooms and corners
|
|
78
81
|
|
|
@@ -137,7 +140,7 @@ Two MCP surfaces are mounted into every agent session.
|
|
|
137
140
|
| Tool | Where | What it does |
|
|
138
141
|
| ------------------------------------------------------ | --------------- | ------------------------------------------------------------- |
|
|
139
142
|
| `open_corner` | Top-level Rooms | Open one write-enabled corner with a ≤24-word objective |
|
|
140
|
-
| `pr_checks_status` | Corners | Read
|
|
143
|
+
| `pr_checks_status` | Corners | Read checks, human hold, and PR/head-bound merge approval |
|
|
141
144
|
| `attach_file` | Everywhere | Attach one file from the checkout or scratch dir to the reply |
|
|
142
145
|
| `create_schedule`, `list_schedules`, `delete_schedule` | Everywhere | Run a prompt again later — interval minutes or a 5-field cron |
|
|
143
146
|
| `request_grant` | Everywhere | Ask the owner for reach outside the sandbox |
|