pi-runline 0.6.0 → 0.7.1
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 +4 -4
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Code mode for [pi](https://github.com/mariozechner/pi).
|
|
4
4
|
|
|
5
|
-
An extension that plugs [runline](https://www.npmjs.com/package/runline) into coding agents. The agent gets one native tool, in-sandbox action discovery, a fuzzy picker for choosing which of the
|
|
5
|
+
An extension that plugs [runline](https://www.npmjs.com/package/runline) into coding agents. The agent gets one native tool, in-sandbox action discovery, a fuzzy picker for choosing which of the 202 built-in plugins to expose, and a guided credential prompt for the ones it hasn't seen before.
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
@@ -38,11 +38,11 @@ return await github.issue.create({ owner: "acme", repo: "api", title: "Bug" });
|
|
|
38
38
|
|
|
39
39
|
## `/runline-plugins` — the picker
|
|
40
40
|
|
|
41
|
-
Typing `/runline-plugins` in a pi session opens a fuzzy multi-select over all
|
|
41
|
+
Typing `/runline-plugins` in a pi session opens a fuzzy multi-select over all 202 built-in plugins.
|
|
42
42
|
|
|
43
43
|
```
|
|
44
44
|
╭─────────────────────────────────────────────╮
|
|
45
|
-
│ runline plugins · 5/
|
|
45
|
+
│ runline plugins · 5/202 enabled │
|
|
46
46
|
│ type to filter · space toggle · ^A toggle │
|
|
47
47
|
│ │
|
|
48
48
|
│ filter ❯ gith │
|
|
@@ -85,6 +85,6 @@ Fallback used when the current cwd has no `.runline/` anywhere up the tree. Usef
|
|
|
85
85
|
|
|
86
86
|
## How plugin allow-listing works
|
|
87
87
|
|
|
88
|
-
The extension deliberately exposes nothing by default. That's on purpose — 2,
|
|
88
|
+
The extension deliberately exposes nothing by default. That's on purpose — 2,614 actions is a lot of context budget. You pick the plugins that matter for a given project, commit the allowlist to `.runline/config.json`, and the agent only ever sees the ones you enabled in its primer.
|
|
89
89
|
|
|
90
90
|
Note that the QuickJS sandbox itself still registers every runline plugin as a global (and `actions.list()` will surface them all), so in principle an agent could guess and call a disabled plugin. In practice the primer only advertises the allowlisted ones, and unconfigured plugins error out at first action call anyway. Plumbing the allowlist into the sandbox registry is on the roadmap.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-runline",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.7.1",
|
|
4
4
|
"description": "Code mode for pi",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"keywords": [
|
|
@@ -22,7 +22,7 @@
|
|
|
22
22
|
"lint:fix": "biome check --write extensions/"
|
|
23
23
|
},
|
|
24
24
|
"dependencies": {
|
|
25
|
-
"runline": "^0.
|
|
25
|
+
"runline": "^0.7.1"
|
|
26
26
|
},
|
|
27
27
|
"peerDependencies": {
|
|
28
28
|
"@mariozechner/pi-coding-agent": "*",
|