@henryqw/pi-footer 5.1.1 → 5.1.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.
Files changed (2) hide show
  1. package/README.md +7 -18
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # `@henryqw/pi-footer`
2
2
 
3
- Keep footer identity, model usage, agent-work time, and extension status visible in Pi. Use `/open` to open the current working directory. Enable the footer and open commands independently.
3
+ Keep footer identity, model usage, agent-work time, and extension status visible in Pi. Enable the footer and open commands independently.
4
4
 
5
5
  ![Pi footer showing repository, pull request, quota, usage, model, and extension status](./example.png)
6
6
 
@@ -10,15 +10,6 @@ Keep footer identity, model usage, agent-work time, and extension status visible
10
10
  pi install npm:@henryqw/pi-footer
11
11
  ```
12
12
 
13
- This package replaces `@henryqw/pi-open-in`. Remove that package before you upgrade to prevent duplicate `/open` and `/set-open-in` commands:
14
-
15
- ```bash
16
- pi remove npm:@henryqw/pi-open-in
17
- pi install npm:@henryqw/pi-footer
18
- ```
19
-
20
- For project-local installations, add `--local` to both commands. Remove manually configured paths to the old package, then restart Pi. Keep the existing open command configuration at `config/pi-open-in/config.json`; do not move it.
21
-
22
13
  Both entry points load by default. To select only the open commands, use Pi's resource filter in `settings.json`:
23
14
 
24
15
  ```json
@@ -32,7 +23,7 @@ Both entry points load by default. To select only the open commands, use Pi's re
32
23
  }
33
24
  ```
34
25
 
35
- Select `extensions/footer.ts` for only the footer, or use `pi config` to toggle either resource. No package activation config is necessary.
26
+ Select `extensions/footer.ts` for only the footer, or use `pi config` to toggle either resource.
36
27
 
37
28
  ## Works with
38
29
 
@@ -69,7 +60,7 @@ Virtual models show the latest successful physical model and thinking level afte
69
60
 
70
61
  Thinking colors are dim grey for `off` and the model name, then green `minimal`, yellow-green `low`, lime `medium`, yellow `high`, orange `xhigh`, and red `max`. Active levels use ANSI-256 colors. `ultra` uses a rainbow only when the runtime supports it; unsupported levels do not appear.
71
62
 
72
- CodeGraph shows `✓ CG` with an index, `○ CG` in Git without an index, and no index badge outside Git. Setup shows a dim spinner and elapsed time, such as `⠋ CG · indexing 8s`. Persistent failures retain their theme-colored `!` and error text. Direct `codegraph_explore` calls temporarily show `● CG`; queries inside scripted tools do not.
63
+ For CodeGraph badges, see [`@henryqw/pi-codegraph`](https://pi.henry.wang/extensions/pi-codegraph).
73
64
 
74
65
  Other dependency statuses, such as `⠋ deps · installing 12s`, disappear after completion. Middle dots separate statuses. The footer preserves colors, links, glyphs, and interior spacing, trims outer whitespace, replaces line breaks with spaces, and shortens long statuses.
75
66
 
@@ -95,7 +86,7 @@ Local Git data comes from `git status --porcelain=v2 --branch --untracked-files=
95
86
  Package-owned paths under `getAgentDir()` (normally `~/.pi/agent`):
96
87
 
97
88
  - `~/.pi/agent/config/pi-footer/config.json`: footer colors.
98
- - `~/.pi/agent/config/pi-open-in/config.json`: open command, retained from `pi-open-in`.
89
+ - `~/.pi/agent/config/pi-open-in/config.json`: open command.
99
90
 
100
91
  | Name | Description | Values | Default |
101
92
  | --- | --- | --- | --- |
@@ -141,13 +132,9 @@ Theme tokens: `accent`, `dim`, `muted`, `text`, `success`, `warning`, `error`, a
141
132
  }
142
133
  ```
143
134
 
144
- ### Open command
145
-
146
- `/open` reads config on each run. Missing config silently uses `code`. Reads never create or write the config home; only `/set-open-in` writes the file, atomically.
147
-
148
135
  ## API
149
136
 
150
- Consumers must use the owner API, not read config directly. Replace `@henryqw/pi-open-in/open-uri` imports with `@henryqw/pi-footer/open-uri`:
137
+ Consumers must use the owner API, not read config directly:
151
138
 
152
139
  ```ts
153
140
  import { loadOpenInConfig } from "@henryqw/pi-footer/open-uri";
@@ -169,6 +156,8 @@ if (loaded.status === "ok") console.log(loaded.value.command, loaded.issues);
169
156
 
170
157
  Open commands split on whitespace. Quoting and tokens with spaces are unsupported; use a wrapper script for executable paths with spaces.
171
158
 
159
+ `/open` reads config on each run. Missing config silently uses `code`. Only `/set-open-in` writes the file, atomically.
160
+
172
161
  Open config must be a JSON object with one non-empty string `command`. Unknown keys, invalid commands, or malformed files produce warnings at session start or the next `/open`, including footer-only installations. Each issue shows once per session, never during rendering. Invalid commands and malformed files use `code` without changing the file.
173
162
 
174
163
  Fix config or run `/set-open-in <command>` to replace it; the command reports new issues before replacement. If the command fails, Pi reports its error output or exit code. Fix the command and retry `/open`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@henryqw/pi-footer",
3
- "version": "5.1.1",
3
+ "version": "5.1.2",
4
4
  "description": "Show repository and usage details in the Pi footer and open the current working directory.",
5
5
  "keywords": [
6
6
  "pi-package",