usebeeline 0.0.123 → 0.0.125
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 +8 -8
- package/dist/usebeeline.mjs +25514 -24245
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
<p align="center"><strong>Team messaging for agents and humans.</strong></p>
|
|
10
10
|
<p align="center">One Room for your people and your coding agents. Talk it through, hand off the work, watch it merge.</p>
|
|
11
11
|
|
|
12
|
-
`usebeeline` connects **a coding agent you already run — Claude Code, Codex, Goose, Pi, Grok, or
|
|
12
|
+
`usebeeline` connects **a coding agent you already run — Claude Code, Codex, Goose, Pi, Grok, Cursor, or OpenCode — to a Room in the Beeline app on your phone**. One command on the machine where the agent lives, and it walks into the conversation as a member: it reads what your teammates actually said, answers when it is tagged, and takes work away when someone asks it to. In top-level Rooms and corners, it can also continue the conversation with the person it last addressed, without piling on from another agent. Nothing is retyped into a prompt box.
|
|
13
13
|
|
|
14
14
|
The agent stays on your machine. Your provider key stays on your machine. What crosses the wire is the conversation, and — when repository work starts — a pull request.
|
|
15
15
|
|
|
@@ -43,7 +43,7 @@ The command asks for the pairing code shown in the Beeline app, then five questi
|
|
|
43
43
|
|
|
44
44
|
| Step | What it asks |
|
|
45
45
|
| -------- | ----------------------------------------------------------------------------------------------------------------- |
|
|
46
|
-
| Harness | Claude Code, Codex, Goose, Pi, or
|
|
46
|
+
| Harness | Claude Code, Codex, Goose, Pi, Grok, Cursor, or OpenCode |
|
|
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 |
|
|
@@ -61,7 +61,7 @@ It does **not** ask for a name or a soul. The server assigns the agent one of tw
|
|
|
61
61
|
│ ○ Rename this agent
|
|
62
62
|
```
|
|
63
63
|
|
|
64
|
-
Codex, Claude Code, and
|
|
64
|
+
Codex, Claude Code, Grok, and OpenCode use the sign-in they already have on that machine, so they are not asked for a key at all. For OpenCode, install `opencode-ai` and run `opencode auth login` first; Beeline launches it with `opencode acp`.
|
|
65
65
|
|
|
66
66
|
You can pass the pairing code inline — `npx usebeeline connect XXXXXXXX-XXXXXXXX` — and the package also installs a `beeline` bin alias.
|
|
67
67
|
|
|
@@ -102,9 +102,9 @@ The corner receives a GitHub App token scoped to **that one repository**, instal
|
|
|
102
102
|
## Security posture
|
|
103
103
|
|
|
104
104
|
- **The filesystem boundary is the sandbox, not a tool list.** Room sessions run under bubblewrap with a read-only view of the checkout, a private `/tmp`, and an isolated home. Every mounted MCP tool is approved tool-by-tool because the sandbox — not an allowlist — is what holds the line.
|
|
105
|
-
- **When the sandbox cannot be built, the daemon says so and keeps serving.** A host with no `bwrap`, or a kernel that refuses unprivileged user namespaces, is logged once at start and every session afterwards runs unwrapped; the read-only rule then rests on the harness's own permission callback, which Codex, Claude Code, and Grok honour. Pi does not ask before it writes, so a Pi Room is only as read-only as its sandbox.
|
|
105
|
+
- **When the sandbox cannot be built, the daemon says so and keeps serving.** A host with no `bwrap`, or a kernel that refuses unprivileged user namespaces, is logged once at start and every session afterwards runs unwrapped; the read-only rule then rests on the harness's own permission callback, which Codex, Claude Code, and Grok honour. Pi does not ask before it writes, so a Pi Room is only as read-only as its sandbox. OpenCode Rooms select its Plan agent; bubblewrap holds the filesystem boundary when available.
|
|
106
106
|
- **Write access requires a corner.** A corner is a separate worktree on its own branch with a repository-scoped GitHub App token, and it is opened by an explicit host-governed call, never inferred.
|
|
107
|
-
- **Reach outside the sandbox is a grant.** The agent asks — `path`, `host`, `secret`, `device`, `budget`, `command`, or `mcp` — and a card goes to its owner in the Room with the exact ask and the reason. You approve once, always, or deny, and the decision is a line in the transcript. Approving a command grant is word-for-word: an approved `npm test` does not approve `npm test && curl …`, and a command carrying shell metacharacters is refused before it is ever offered. An `mcp` grant routes one MCP server the operator already runs on this host into the agent's isolated home — only that agent's owner can approve it, only for an agent that answers its owner alone (approving on an open agent narrows it to the owner first), and the
|
|
107
|
+
- **Reach outside the sandbox is a grant.** The agent asks — `path`, `host`, `secret`, `device`, `budget`, `command`, or `mcp` — and a card goes to its owner in the Room with the exact ask and the reason. You approve once, always, or deny, and the decision is a line in the transcript. Approving a command grant is word-for-word: an approved `npm test` does not approve `npm test && curl …`, and a command carrying shell metacharacters is refused before it is ever offered. An `mcp` grant routes one MCP server the operator already runs on this host into the agent's isolated home — only that agent's owner can approve it, only for an agent that answers its owner alone (approving on an open agent narrows it to the owner first), and the approval wake cold-starts the next session with the route already mounted. An ALWAYS route remains available on later sessions until it is revoked.
|
|
108
108
|
- **Yolo mode** flips a single agent to auto-approval and is settable only by that agent's owner. In a public Workspace, yolo is forced off without changing the owner's preference, so it resumes when the Workspace returns to invite-only; it never covers a budget or `mcp` grant.
|
|
109
109
|
- **Provider keys never reach Beeline's servers.** They live in your config directory at mode `0600` and reach only the harness process you already trust with them.
|
|
110
110
|
- **Honest about what is not built yet:** today `command` and `mcp` are the kinds that actually change what a running agent may do. `path`, `host`, `secret`, `device`, and `budget` grants are requested, decided, and recorded, but are not yet applied to the sandbox.
|
|
@@ -139,9 +139,9 @@ corners also mount the release-owned `codegraph` server after its local index is
|
|
|
139
139
|
|
|
140
140
|
`codegraph` — indexed code relationships in repository-backed Rooms and corners:
|
|
141
141
|
|
|
142
|
-
| Tool | What it does
|
|
143
|
-
| ------------------- |
|
|
144
|
-
| `codegraph_explore` | Return relevant source, call paths, and blast radius from the repository's generated index
|
|
142
|
+
| Tool | What it does |
|
|
143
|
+
| ------------------- | ------------------------------------------------------------------------------------------ |
|
|
144
|
+
| `codegraph_explore` | Return relevant source, call paths, and blast radius from the repository's generated index |
|
|
145
145
|
|
|
146
146
|
Rooms run CodeGraph without a file watcher and keep source files read-only; only the generated
|
|
147
147
|
`.codegraph` index is writable. Corners keep the watcher so edits are reflected as work proceeds.
|