@bigstrider/transcodes-cli 0.3.0 → 0.4.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 +7 -4
- package/dist/index.js +6525 -343
- package/package.json +7 -5
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @bigstrider/transcodes-cli
|
|
2
2
|
|
|
3
|
-
Token manager for the **
|
|
3
|
+
Token manager for the **transcodes-guard** plugins (Claude Code / Codex / Cursor / Antigravity).
|
|
4
4
|
|
|
5
5
|
The plugins and their hooks authenticate to the Transcodes backend with a member MCP JWT. This CLI is the safe way to store that token: you paste it into your terminal, **never into the agent chat** (which would leak it into the transcript).
|
|
6
6
|
|
|
@@ -21,13 +21,16 @@ Works the same on macOS, Linux, and Windows (Node ≥ 20).
|
|
|
21
21
|
|
|
22
22
|
| Command | What it does |
|
|
23
23
|
|---------|--------------|
|
|
24
|
-
| `transcodes` | Opens the dashboard
|
|
24
|
+
| `transcodes` | Opens the local dashboard (URL printed in the terminal; default port 3847, increments if busy) to paste, save, switch, label, or delete tokens (accepts `--port N` / `--no-open`). |
|
|
25
25
|
| `transcodes set <token> -l <label>` | Validates the JWT and saves it (label required) to `~/.transcodes/config.json` (dir `0700`, file `0600`), making it active. |
|
|
26
26
|
| `transcodes tokens` | Lists all saved tokens; the active one is marked with `*`. |
|
|
27
27
|
| `transcodes status` | Shows the active token source (env vs file) and its expiry. |
|
|
28
28
|
| `transcodes reset` | Deletes all saved tokens. |
|
|
29
|
+
| `transcodes policy refresh` | Force-refreshes the org policy bundle cache (same as MCP `refresh_rules`). |
|
|
29
30
|
| `transcodes help` | Shows the full command list and usage. |
|
|
30
31
|
|
|
32
|
+
Command descriptions are defined once in `cli/src/commands.ts` (SSOT) and shared with the dashboard CLI tab.
|
|
33
|
+
|
|
31
34
|
### Dashboard
|
|
32
35
|
|
|
33
36
|
```bash
|
|
@@ -43,7 +46,7 @@ Options:
|
|
|
43
46
|
|
|
44
47
|
## Token precedence
|
|
45
48
|
|
|
46
|
-
The plugins resolve the token in this order (see `@
|
|
49
|
+
The plugins resolve the token in this order (see `@transcodes-guard/stepup-core` `resolveToken()`):
|
|
47
50
|
|
|
48
51
|
1. `TRANSCODES_TOKEN` environment variable — overrides everything (CI / power users)
|
|
49
52
|
2. `~/.transcodes/config.json` — written by this CLI
|
|
@@ -51,5 +54,5 @@ The plugins resolve the token in this order (see `@ai-action-tracker/stepup-core
|
|
|
51
54
|
|
|
52
55
|
## Notes
|
|
53
56
|
|
|
54
|
-
- **Windows security**: the `0600` mode is a POSIX concept and is largely ignored on Windows. The file still lives under your user profile (`C:\Users\<you>\.transcodes\`) and is user-scoped by default. A hardware-backed OS keychain is
|
|
57
|
+
- **Windows security**: the `0600` mode is a POSIX concept and is largely ignored on Windows. The file still lives under your user profile (`C:\Users\<you>\.transcodes\`) and is user-scoped by default. A hardware-backed OS keychain is not yet implemented.
|
|
55
58
|
- The token never passes through the agent chat — this CLI writes the file directly.
|