You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -239,10 +239,11 @@ Local transaction-id conversion helpers:
239
239
240
240
Auth resolution order for commands is:
241
241
242
-
1.`--api-key` or `BRAINTRUST_API_KEY` (unless `--prefer-profile` is set)
243
-
2.`--profile` or `BRAINTRUST_PROFILE`
244
-
3. Org-based profile match (profile whose org matches `--org`/config org)
245
-
4. Single-profile auto-select (if only one profile exists)
242
+
1. Explicit `--profile`
243
+
2.`--api-key` or `BRAINTRUST_API_KEY` (unless `--prefer-profile` is set)
244
+
3.`BRAINTRUST_PROFILE`
245
+
4. Org-based profile match (profile whose org matches `--org`/config org)
246
+
5. Single-profile auto-select (if only one profile exists)
246
247
247
248
On Linux, secure storage uses `secret-tool` (libsecret) with a running Secret Service daemon. On macOS, it uses the `security` keychain utility. If a secure store is unavailable, `bt` falls back to a plaintext secrets file with `0600` permissions.
0 commit comments