open-usage 0.2.0 → 0.3.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.
Files changed (2) hide show
  1. package/README.md +16 -1
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -83,6 +83,17 @@ open-usage --help
83
83
 
84
84
  Every control is also clickable, and the mouse wheel scrolls views taller than the terminal.
85
85
 
86
+ ### Staying current
87
+
88
+ When a newer version has been published, the header says so:
89
+
90
+ ```
91
+ OPEN USAGE v0.4.0 available ▏ 3 providers ▏ ✓ all clear ▏ updated now
92
+ ```
93
+
94
+ Update with the same command that installed it - `bun install -g open-usage@latest`, or the npm, pnpm or yarn equivalent.
95
+ The check runs at most once a day, and [Configuration](#configuration) below covers switching it off.
96
+
86
97
  ## What it reads
87
98
 
88
99
  | Provider | Limits from | History from |
@@ -96,7 +107,10 @@ It reuses the logins your CLIs already have: Claude and Codex limits come from t
96
107
  The one credential file it opens is OpenCode's `auth.json`, and only to show connection status - the key is masked on read and never displayed, logged, or sent anywhere.
97
108
 
98
109
  Nothing is written outside its own config directory, and there is no telemetry or analytics of any kind.
99
- The only outbound request it makes on its own is to `opencode.ai`, and only if you opt in by configuring the cookie below.
110
+ It makes two outbound requests of its own accord.
111
+ One is to `opencode.ai`, and only if you opt in by configuring the cookie below.
112
+ The other asks `registry.npmjs.org` whether a newer version has been published, so an installed copy can tell you it is out of date - it sends nothing but the request, caches the answer for a day, gives up after 1.5 seconds, and stays silent on any failure.
113
+ Set `OPEN_USAGE_NO_UPDATE_CHECK` to switch it off.
100
114
 
101
115
  OpenCode Go does not publish per-account limits, so its percentages are local estimates and are labelled as such in the UI.
102
116
  Configuring the cookie below replaces those estimates with exact figures, and is enough on its own: OpenCode itself need not be installed, though without it the Go card has no token history to chart.
@@ -113,6 +127,7 @@ They persist to `~/.config/open-usage/preferences.json` (or `$XDG_CONFIG_HOME/op
113
127
  | `CODEX_HOME` | non-default Codex home |
114
128
  | `OPENCODE_DB` | non-default `opencode.db` path, for history |
115
129
  | `OPEN_USAGE_OPENCODE_COOKIE` | exact OpenCode Go windows, no install needed |
130
+ | `OPEN_USAGE_NO_UPDATE_CHECK` | set to anything to stop the daily version check |
116
131
 
117
132
  ## Development
118
133
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "open-usage",
3
- "version": "0.2.0",
3
+ "version": "0.3.1",
4
4
  "description": "A terminal dashboard for unified AI plan usage across Claude Code, Codex, and OpenCode Go",
5
5
  "type": "module",
6
6
  "license": "GPL-3.0-only",
@@ -54,10 +54,10 @@
54
54
  "typescript": "^5"
55
55
  },
56
56
  "optionalDependencies": {
57
- "@open-usage/darwin-arm64": "0.2.0",
58
- "@open-usage/linux-arm64": "0.2.0",
59
- "@open-usage/linux-x64": "0.2.0",
60
- "@open-usage/win32-arm64": "0.2.0",
61
- "@open-usage/win32-x64": "0.2.0"
57
+ "@open-usage/darwin-arm64": "0.3.1",
58
+ "@open-usage/linux-arm64": "0.3.1",
59
+ "@open-usage/linux-x64": "0.3.1",
60
+ "@open-usage/win32-arm64": "0.3.1",
61
+ "@open-usage/win32-x64": "0.3.1"
62
62
  }
63
63
  }