opencode-supabase 0.0.4-alpha.1 → 0.0.4
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 +8 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,13 +22,18 @@ Connect your account and ask your agent about Supabase capabilities.
|
|
|
22
22
|
|
|
23
23
|
## Debug Logging
|
|
24
24
|
|
|
25
|
-
If you hit auth or tool errors and need logs for an issue,
|
|
25
|
+
If you hit auth or tool errors and need logs for an issue, collect the newest OpenCode session log from its default log directory:
|
|
26
|
+
|
|
27
|
+
- macOS/Linux: `~/.local/share/opencode/log/`
|
|
28
|
+
- Windows: `%USERPROFILE%\.local\share\opencode\log`
|
|
29
|
+
|
|
30
|
+
Run OpenCode with debug logging enabled while reproducing the problem:
|
|
26
31
|
|
|
27
32
|
```bash
|
|
28
|
-
opencode --log-level DEBUG --print-logs
|
|
33
|
+
opencode --log-level DEBUG --print-logs
|
|
29
34
|
```
|
|
30
35
|
|
|
31
|
-
|
|
36
|
+
Then share that newest session log file in the issue. In our testing, the session log file is more reliable than redirecting `stderr` with `2>` for capturing plugin activity.
|
|
32
37
|
|
|
33
38
|
## Available today
|
|
34
39
|
|