npm - @pasko70/pibo - Versions diffs - 3.1.4 → 3.2.0 - Mend

@pasko70/pibo 3.1.4 → 3.2.0

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 (30) hide show

package/dist/apps/chat-vscode-web/index.html CHANGED Viewed

@@ -5,8 +5,8 @@
 		<meta name="viewport" content="width=device-width, initial-scale=1.0" />
 		<meta name="theme-color" content="#101d22" />
 		<title>Pibo</title>
-		<script type="module" crossorigin src="/apps/chat-vscode/assets/index-zQ1fNz5K.js"></script>
-		<link rel="stylesheet" crossorigin href="/apps/chat-vscode/assets/index-SluZr_-r.css">
+		<script type="module" crossorigin src="/apps/chat-vscode/assets/index-nHYofa-e.js"></script>
+		<link rel="stylesheet" crossorigin href="/apps/chat-vscode/assets/index-b18ZkEo0.css">
 	</head>
 	<body>
 		<div id="root"></div>

package/dist/setup/cli.js CHANGED Viewed

@@ -128,7 +128,7 @@ export function createUserHostSetupPlan(options = {}) {
     if (!options.domain)
         warnings.push("No production domain was provided; generated Caddy/Auth examples use placeholders.");
     if (process.platform === "win32" && !isWsl()) {
-        warnings.push("Pibo host setup targets Linux. Native Windows is not supported. Install WSL2 (https://aka.ms/wsl) and run setup inside the WSL distribution. See docs/guides/pibo-on-windows-via-wsl.md.");
+        warnings.push("Pibo host setup targets Linux. Native Windows is not supported. Install WSL2 (https://aka.ms/wsl) and run setup inside the WSL distribution. See docs/project/guides/pibo-on-windows-via-wsl.md.");
     }
     const generatedFiles = [
         {
@@ -201,7 +201,7 @@ export function createDeveloperHostSetupPlan(options = {}) {
     if (!options.prodDomain || !options.devDomain)
         warnings.push("Production and dev domains should both be configured before requesting HTTPS certificates.");
     if (process.platform === "win32" && !isWsl()) {
-        warnings.push("Pibo developer-host setup targets Linux. Native Windows is not supported. Install WSL2 (https://aka.ms/wsl) and run setup inside the WSL distribution. See docs/guides/pibo-on-windows-via-wsl.md.");
+        warnings.push("Pibo developer-host setup targets Linux. Native Windows is not supported. Install WSL2 (https://aka.ms/wsl) and run setup inside the WSL distribution. See docs/project/guides/pibo-on-windows-via-wsl.md.");
     }
     const generatedFiles = [
         {
@@ -496,13 +496,13 @@ async function createDoctorStatus(options) {
     if (wslInfo.isWsl) {
         const versionLabel = wslInfo.version ? `WSL${wslInfo.version}` : "WSL";
         const distroLabel = wslInfo.distro ? ` (${wslInfo.distro})` : "";
-        checks.push({ name: "platform.wsl", status: "ok", detail: `Running inside ${versionLabel}${distroLabel}; Pibo is fully supported here. See docs/guides/pibo-on-windows-via-wsl.md.` });
+        checks.push({ name: "platform.wsl", status: "ok", detail: `Running inside ${versionLabel}${distroLabel}; Pibo is fully supported here. See docs/project/guides/pibo-on-windows-via-wsl.md.` });
     }
     else if (process.platform === "win32") {
         checks.push({
             name: "platform.wsl",
             status: "fail",
-            detail: "Native Windows is not supported. Install WSL2 (https://aka.ms/wsl) and run Pibo inside the WSL distribution. See docs/guides/pibo-on-windows-via-wsl.md.",
+            detail: "Native Windows is not supported. Install WSL2 (https://aka.ms/wsl) and run Pibo inside the WSL distribution. See docs/project/guides/pibo-on-windows-via-wsl.md.",
         });
     }
     checks.push(...swapCheck(options.minSwapGb));
@@ -610,7 +610,7 @@ async function createDoctorStatus(options) {
         recommendations.push("Browser-Use and Agent-Browser work directly under WSLg on Windows 11. On Windows 10, install an X server (e.g. VcXsrv) and export DISPLAY=:0 inside WSL.");
     }
     else if (process.platform === "win32") {
-        recommendations.push("Pibo does not run natively on Windows. Install WSL2 with `wsl --install` and follow docs/guides/pibo-on-windows-via-wsl.md.");
+        recommendations.push("Pibo does not run natively on Windows. Install WSL2 with `wsl --install` and follow docs/project/guides/pibo-on-windows-via-wsl.md.");
     }
     return {
         node: process.versions.node,

package/docs/project/guides/pibo-on-windows-via-wsl.md ADDED Viewed

@@ -0,0 +1,292 @@
+---
+type: "Guide"
+title: "Pibo on Windows via WSL"
+description: "Guides Windows users through installing Pibo and the VS Code extension inside WSL2."
+tags: ["installation", "windows", "wsl", "vscode"]
+status: "draft"
+authority: "directive"
+generated:
+  by: "openai/codex"
+  at: "2026-08-30T15:47:50Z"
+sources:
+  - id: "foundation-relocation-source"
+    resource: "https://github.com/Pascapone/pibo/blob/2aef244301f5d181624662fdad53e18e83e80bd9/docs/guides/pibo-on-windows-via-wsl.md"
+    title: "Original byte-preserved Pibo on Windows via WSL guide"
+    commit: "2aef244301f5d181624662fdad53e18e83e80bd9"
+    path: "docs/guides/pibo-on-windows-via-wsl.md"
+    sha256: "132f00469edcfa8915525bff4d0c9d82573ae53868a74db81d5224d354ce1d25"
+    relation: "Byte-identical body lineage before Foundation relocation."
+---
+# Pibo on Windows via WSL
+Pibo is a Linux-first tool. Native Windows is **not** supported, but Pibo runs unmodified inside **WSL2** because WSL2 is a real Linux kernel with full filesystem, symlink, and process semantics. This guide walks a Windows user from a fresh machine to a working `pibo` install, including the Pibo VSCode extension.
+Total setup time: **15–25 minutes** on Windows 11 with WSLg enabled.
+## Why WSL and not native Windows?
+| | Native Windows | WSL2 |
+|---|---|---|
+| **Code changes** | 12+ POSIX assumptions would need workarounds | 0 — Pibo already runs on Linux |
+| **Docker workers** | Docker Desktop only, paths are awkward | Docker Desktop integrates with WSL2, no friction |
+| **Browser-Use / Agent-Browser** | Need WSL or WSLg anyway | Works directly under WSLg |
+| **`pibo setup` (systemd, caddy)** | Would need a Windows port | Works as on Linux |
+| **Symlinks, file modes, line endings** | Pain | Native |
+| **Long-term maintenance** | Two code paths | One code path |
+Microsoft itself recommends WSL for Linux-style development on Windows. The VSCode "WSL" extension, Docker Desktop's WSL2 backend, and Windows 11's WSLg GUI integration make WSL a first-class dev environment.
+## Prerequisites
+- **Windows 10 version 2004+** or **Windows 11** (any edition)
+- Administrator access for the WSL install
+- About 5 GB free disk space (WSL image + Pibo + node_modules)
+## Step 1 — Install WSL (5 min, one-time)
+Open **PowerShell as Administrator** and run:
+```powershell
+wsl --install
+```
+Default settings install Ubuntu. Reboot when prompted. On first boot, Ubuntu sets a username and password.
+Verify the install:
+```powershell
+wsl --status
+# Default Distribution: Ubuntu
+# Default Version: 2
+```
+> **Tip:** If you want a different distro (Debian, openSUSE, Alpine…), run `wsl --install -d <DistroName>`. The rest of this guide works for any of them.
+## Step 2 — Verify the WSL version (1 min)
+Inside the WSL shell (run `wsl` in PowerShell to enter it), confirm WSL2:
+```bash
+cat /proc/sys/kernel/osrelease
+# Look for "microsoft-standard-WSL2" or "WSL2" in the output.
+```
+If you see "Microsoft" without the WSL2 marker, your distro is on WSL1. Convert it:
+```powershell
+# PowerShell
+wsl --set-version Ubuntu 2
+```
+WSL1 cannot run Docker well and lacks the full Linux kernel Pibo expects. Use WSL2.
+## Step 3 — Install Node.js 24+ inside WSL (3 min)
+The Ubuntu default Node is often too old. Use NodeSource:
+```bash
+# Inside WSL
+sudo apt update
+sudo apt install -y ca-certificates curl gnupg
+curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
+sudo apt install -y nodejs build-essential
+node --version    # must print v24.x.x or higher
+npm --version
+```
+## Step 4 — Install Pibo inside WSL (1 min)
+```bash
+# Inside WSL
+npm install -g @pasko70/pibo
+pibo --version
+```
+Pibo's data lives in `~/.pibo` inside the WSL filesystem. This is intentional: WSL-native paths are fast, while `/mnt/c/...` mounts are slow. Keep Pibo's working data inside WSL.
+## Step 5 — Install VSCode and the WSL extension (3 min)
+1. Install **VSCode for Windows** from <https://code.visualstudio.com/> (the standard Windows .exe, not the .deb).
+2. In VSCode, open the **Extensions** panel (Ctrl+Shift+X) and install **WSL** by Microsoft.
+3. **Open your project folder inside WSL.** In the WSL terminal:
+   ```bash
+   cd ~/projects/my-app    # or wherever your project lives
+   code .
+   ```
+   VSCode opens a second VSCode window. Title bar shows the distro name in green (`[WSL: Ubuntu]`). File editing, terminal, and extensions all run inside WSL.
+> **Why this step matters:** when you run `code .` from inside WSL, VSCode installs its Linux server binary inside the WSL distro, the integrated terminal becomes a WSL bash, and `code` is added to WSL's `PATH`. That is what makes `pibo vscode install` work seamlessly.
+## Step 6 — Configure Pibo auth (3 min)
+Pibo uses [Better Auth](https://www.better-auth.com/) with Google OAuth. Set the keys once:
+```bash
+# Inside WSL
+pibo config set auth.baseURL http://127.0.0.1:4788
+pibo config set auth.secret "$(openssl rand -hex 32)"
+pibo config set auth.googleClientId <your-google-oauth-client-id>
+pibo config set auth.googleClientSecret <your-google-oauth-client-secret>
+pibo config set auth.allowedEmails you@example.com
+```
+To get Google OAuth credentials, create a Web Application client at <https://console.cloud.google.com/apis/credentials>. The redirect URI is `http://127.0.0.1:4788/api/auth/callback/google`. See the [Quick Start Guide](./pibo-vscode-ext-quickstart.md) for the full walkthrough.
+## Step 7 — Start the Pibo gateway (1 min)
+```bash
+# Inside WSL, leave this running in a terminal
+pibo gateway:web
+```
+The gateway listens on `127.0.0.1:4788` **inside WSL**. Windows can reach this URL because WSL2 forwards localhost from Windows to the WSL2 VM by default.
+Open a **second** WSL terminal and verify:
+```bash
+curl -s http://127.0.0.1:4788/api/health
+# or open in your Windows browser:
+# http://127.0.0.1:4788/apps/chat
+```
+> **If localhost does not work in the Windows browser:** the WSL2 localhost forwarder is disabled or blocked. See [Troubleshooting](#localhost-forwarding-not-working) below.
+## Step 8 — Install the Pibo VSCode extension (2 min)
+### Option A — from the WSL terminal (recommended)
+```bash
+# Inside the WSL VSCode terminal (Ctrl+`)
+pibo vscode install
+```
+This downloads the latest VSIX from GitHub Releases and runs `code --install-extension` against the WSL `code` binary.
+### Option B — from the Marketplace
+Search **Pibo** by publisher `pibo` in the Extensions panel. Install the one named **Pibo** by `pibo`.
+### Verify
+```bash
+pibo vscode status
+# Should print the installed extension ID and the gateway URL.
+```
+Click the **Pibo** icon in the VSCode sidebar (left rail). A web view opens. Sign in with Google. The status bar at the bottom should show the room you are in.
+## Step 9 — Optional — Docker workers
+Pibo's compute workers run as Docker containers. To enable them on WSL:
+1. Install **Docker Desktop for Windows**: <https://www.docker.com/products/docker-desktop/>
+2. Open Docker Desktop → **Settings** → **Resources** → **WSL Integration**.
+3. Enable the toggle for **Ubuntu** (or whichever distro you use).
+4. Click **Apply & Restart**.
+Test from WSL:
+```bash
+docker run --rm hello-world
+# Should print "Hello from Docker!"
+```
+Pibo will detect Docker automatically. `pibo compute dev spawn --worktree <name>` now works.
+## Step 10 — Optional — Browser-Use and Agent-Browser
+Both tools need a graphical browser under the hood.
+- **Windows 11 with WSLg** (default on fresh installs): no extra setup. Browser windows appear as regular Windows windows.
+- **Windows 10 or older Windows 11 without WSLg**: install an X server in Windows (e.g. [VcXsrv](https://sourceforge.net/projects/vcxsrv/)) and export the display in WSL:
+  ```bash
+  # Inside WSL ~/.bashrc
+  export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0
+  ```
+  Launch VcXsrv in Windows with "Disable access control" ticked.
+To install the tools:
+```bash
+pibo tools install browser-use
+pibo tools install agent-browser
+pibo tools env browser-use
+```
+## Where Pibo stores things on WSL
+| Path (inside WSL) | What |
+|---|---|
+| `~/.pibo/config.json` | Pibo configuration (auth, ports, etc.) |
+| `~/.pibo/pibo.sqlite` | Sessions, rooms, signals |
+| `~/.pibo/vscode/cache/` | VSIX cache for `pibo vscode install` |
+| `<workspace>/.pibo/` | Per-workspace room state |
+> Keep these inside the WSL filesystem (not under `/mnt/c/...`). Cross-FS access is slow and breaks symlinks.
+## Troubleshooting
+### Localhost forwarding not working
+WSL2 forwards `localhost` from Windows to the WSL VM by default. If the gateway at `http://127.0.0.1:4788` is unreachable from a Windows browser:
+1. **Check Windows version.** Localhost forwarding works on Windows 11 and on Windows 10 22H2+. Older builds had bugs.
+2. **Check the WSL version.** Run `wsl --status` — `Default Version: 2`.
+3. **Check Windows Firewall.** Allow inbound to WSL. Run in PowerShell as Admin:
+   ```powershell
+   New-NetFirewallRule -DisplayName "WSL" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow
+   ```
+4. **Fallback:** use the WSL2 VM's IP. Inside WSL run:
+   ```bash
+   hostname -I
+   # e.g. prints 172.21.123.45
+   ```
+   Then in your Windows browser use `http://172.21.123.45:4788`. The IP changes on each WSL boot, so this is a workaround, not a permanent solution.
+5. **Last resort:** set up `netsh interface portproxy`:
+   ```powershell
+   # PowerShell as Admin
+   $wslIp = wsl hostname -I
+   netsh interface portproxy add v4tov4 listenport=4788 listenaddress=0.0.0.0 connectport=4788 connectaddress=$wslIp
+   ```
+### `pibo setup doctor` warns about native Windows
+You are running Pibo from a Windows PowerShell or `cmd.exe`, not from inside WSL. Open the **WSL** terminal (or run `wsl` from PowerShell) and try again.
+### Browser-Use opens a blank window
+The DISPLAY is not set or the X server is not running. On Windows 11 with WSLg, `echo $DISPLAY` should print something like `:0` or `wayland-0`. On Windows 10, start VcXsrv and export `DISPLAY` as shown above.
+### `pibo vscode install` cannot find `code`
+This means VSCode's WSL server is not active in the current VSCode window. Run `code .` from inside WSL once, restart VSCode, then try again. If you opened VSCode directly from the Start Menu (not via `code .` in WSL), you are in the Windows VSCode instance, not the WSL one.
+### File edits are slow
+You are editing files on `/mnt/c/...` (the Windows drive). Move the project into the WSL filesystem (`/home/<you>/projects/...`). NTFS access from WSL is slow because of `metadata` and `umask` differences.
+### Docker commands fail inside WSL
+Open Docker Desktop → Settings → Resources → WSL Integration → enable your distro → **Apply & Restart**. Verify with `docker run --rm hello-world`.
+## Verifying everything works
+Run the following inside WSL:
+```bash
+pibo --version                          # 1.3.0 or higher
+pibo setup doctor                       # all checks should be OK or WARN
+pibo vscode status                      # extension should be installed
+pibo tools list                         # should list browser-use, agent-browser, etc.
+```
+Open the VSCode sidebar → Pibo icon → web view loads → sign in with Google → create a new session → send a message. The status bar at the bottom should show a green dot and your room name.
+If all of that works, you are fully set up.
+## What we deliberately do not support
+- **Native Windows** (no WSL). Pibo will print a clear error pointing you back to this guide.
+- **WSL1.** WSL1 lacks the full Linux kernel Pibo expects. Use WSL2.
+- **Cygwin, MSYS2, Git Bash.** These are POSIX shims, not real Linux. Pibo will not work; use WSL2.
+- **Windows Containers in Docker.** Pibo compute workers target Linux containers.

package/docs/project/guides/pibo-vscode-ext-quickstart.md ADDED Viewed

@@ -0,0 +1,287 @@
+---
+type: "Guide"
+title: "Pibo Quick Start — CLI + VS Code Extension"
+description: "Provides a German-language quick start for installing Pibo and using its VS Code extension."
+tags: ["cli", "installation", "quickstart", "vscode"]
+status: "draft"
+authority: "directive"
+generated:
+  by: "openai/codex"
+  at: "2026-08-30T15:47:50Z"
+sources:
+  - id: "foundation-relocation-source"
+    resource: "https://github.com/Pascapone/pibo/blob/2aef244301f5d181624662fdad53e18e83e80bd9/docs/guides/pibo-vscode-ext-quickstart.md"
+    title: "Original byte-preserved Pibo VS Code extension quick start"
+    commit: "2aef244301f5d181624662fdad53e18e83e80bd9"
+    path: "docs/guides/pibo-vscode-ext-quickstart.md"
+    sha256: "ff1b33edf70c89ce9b128382d05d5fa28735ede3fc3ba40429bece172fc2d716"
+    relation: "Byte-identical body lineage before Foundation relocation."
+---
+# Pibo Quick Start — CLI + VS Code Extension
+Diese Anleitung bringt dich in ungefähr 15 Minuten vom frischen Laptop zur
+laufenden Pibo-VSCode-Extension.
+## Was du am Ende hast
+- `pibo` CLI global installiert
+- Ein laufendes `pibo gateway:web` (Auth-Gateway) auf `http://127.0.0.1:4788`
+- Die Pibo VS Code Extension in deinem Editor
+- Eine erste Session in deinem aktuellen Projekt-Workspace
+## 0. Voraussetzungen
+| Was | Warum | Wie prüfen |
+|---|---|---|
+| **Node.js 24+** | Pibo läuft auf Node 24 (steht so in `package.json#engines`) | `node --version` |
+| **VS Code** (oder Insiders / VSCodium) | Ziel der Extension | `code --version` |
+| **Internet** | npm + GitHub Releases | ping `registry.npmjs.org` |
+| Optional: **Google OAuth Client** | Echter Login via Google | Console holen: <https://console.cloud.google.com/apis/credentials> |
+Falls dein `apt`-Node zu alt ist: <https://nodejs.org/en/download> oder `fnm`/`nvm` benutzen.
+## 1. Pibo CLI installieren
+```bash
+npm install -g @pasko70/pibo
+pibo --version        # soll 1.3.0 (oder neuer) zeigen
+pibo --help           # zeigt die Top-Level-Commands
+```
+Falls du eine Permission-Fehlermeldung bekommst (Linux/macOS):
+```bash
+mkdir -p ~/.local
+npm config set prefix ~/.local
+export PATH="$HOME/.local/bin:$PATH"
+npm install -g @pasko70/pibo
+```
+Diese PATH-Zeile am besten in deine `~/.bashrc` / `~/.zshrc` schreiben.
+## 2. Auth einrichten (einmalig)
+Pibo nutzt Better Auth + Google OAuth. Die Werte landen in `~/.pibo/config.json`.
+```bash
+pibo config set auth.baseURL http://127.0.0.1:4788
+pibo config set auth.secret "$(openssl rand -hex 32)"   # beliebiger 32+ Zeichen-String
+pibo config set auth.googleClientId     <aus-google-console>
+pibo config set auth.googleClientSecret <aus-google-console>
+pibo config set auth.allowedEmails      deine@email.com
+```
+**Woher bekomme ich die Google-Werte?**
+1. <https://console.cloud.google.com/apis/credentials> öffnen
+2. "OAuth 2.0 Client IDs" → "Create OAuth client ID" → Typ "Web application"
+3. Authorized redirect URIs: `http://127.0.0.1:4788/api/auth/callback/google` eintragen
+4. Client ID und Client Secret in die Config setzen
+5. In deiner Google-Console unter "OAuth consent screen" die gewünschten Test-User hinzufügen
+**Lokal ohne Google testen?** Setze `auth.baseURL=http://localhost:4788` und melde dich ohne externe Auth an (Pibo akzeptiert auf Loopback auch direkten Zugriff). Für die VSCode-Extension reicht das zum Ausprobieren.
+Verify:
+```bash
+pibo config show
+```
+## 3. Gateway starten
+In einem Terminal (das Terminal offen lassen):
+```bash
+pibo gateway:web
+```
+Erwartete Ausgabe (ungefähr):
+```text
+[gateway:web] listening on http://127.0.0.1:4788
+[gateway:web] auth baseURL = http://127.0.0.1:4788
+```
+Im Browser öffnen: <http://127.0.0.1:4788>. Du solltest die Pibo-Web-Oberfläche sehen und dich einloggen können.
+> Tipp: Wenn du das Gateway dauerhaft laufen lassen willst (z.B. auf einem
+> Server), schau dir `pibo gateway web status/start/restart` an — das ist
+> der produktive Pfad mit `pibo-web.service` dahinter.
+## 4. VS Code Extension installieren
+Du hast zwei Wege.
+### Weg A: Über die CLI (empfohlen)
+```bash
+pibo vscode install
+```
+Das Script:
+1. Findet deine `code` (oder `code-insiders` / `codium`) Binary im PATH
+2. Lädt die neueste VSIX aus dem GitHub Release von `Pascapone/pibo`
+3. Installiert sie via `code --install-extension <vsix>`
+4. Verifiziert mit `code --list-extensions --show-versions`
+Verify:
+```bash
+pibo vscode status
+```
+Erwartete Ausgabe:
+```text
+extension:   pibo.pibo-vscode@1.3.0 installed
+binary:      code (at /usr/bin/code)
+latest:      v1.3.0
+cache:       /home/<du>/.pibo/vscode/cache/v1.3.0/pibo.vsix
+```
+### Weg B: Über den VS Code Marketplace
+1. VS Code öffnen
+2. Sidebar → Extensions (`Ctrl+Shift+X` / `Cmd+Shift+X`)
+3. Suchen nach "Pibo" (Publisher: `pibo`)
+4. "Install" klicken
+Falls die Extension noch nicht im Marketplace sichtbar ist, nimm Weg A — der lädt direkt aus dem GitHub Release.
+## 5. Erste Session in VS Code
+1. **VS Code öffnen**, einen Projektordner als Workspace laden
+   (z.B. `File → Open Folder` → irgendein Repo)
+2. **Pibo-Sidebar** öffnen: Klick auf das Pibo-Icon in der linken
+   Activity Bar (es heißt einfach "Pibo")
+3. Beim ersten Öffnen passiert automatisch:
+   - Die Extension mappt deinen Workspace-Folder auf einen Pibo-Room
+   - Falls noch kein Room existiert: einer wird angelegt
+   - Falls genau ein Room existiert: direkt rein
+   - Falls mehrere existieren: ein Room-Picker erscheint
+4. **Neue Session starten**: in der Sidebar auf "New Session" klicken
+   (oder Command Palette → `Pibo: New Session`)
+5. **Chatten**: im Composer Loss tippen, Enter
+Die Session erscheint automatisch auch in der Web App unter
+<http://127.0.0.1:4788> — und umgekehrt.
+## 6. Nützliche Kommandos
+In der **Command Palette** (`Ctrl+Shift+P` / `Cmd+Shift+P`):
+| Kommando | Was es tut |
+|---|---|
+| `Pibo: New Session` | Neue Session im aktuellen Room |
+| `Pibo: Delete Current Session` | Aktuelle Session löschen |
+| `Pibo: Rename Current Session` | Session umbenennen |
+| `Pibo: Open in Chat Web` | Springt zur aktuellen Session im Browser |
+| `Pibo: Sign In` | Login mit openai/anthropic/google Provider |
+In der **CLI**:
+| Kommando | Was es tut |
+|---|---|
+| `pibo vscode install` | Extension installieren / upgraden |
+| `pibo vscode status` | Installations-Status prüfen |
+| `pibo vscode uninstall` | Extension entfernen |
+| `pibo vscode install --vsix <pfad>` | Lokale VSIX installieren (z.B. selbst gebaute) |
+| `pibo vscode install --from-url <url>` | VSIX von beliebiger URL (z.B. internem Mirror) |
+| `pibo vscode install --version v1.4.0` | Bestimmte Version installieren |
+| `pibo config show` | Config anzeigen (Werte sind redacted) |
+| `pibo data rooms` | Rooms / Workspaces anzeigen |
+| `pibo debug session <id>` | Session-Details inspizieren |
+## 7. Konfiguration
+Die Extension kennt folgende Einstellungen:
+- **`pibo.chatWebUrl`** (default: `http://127.0.0.1:4788`)
+  → URL des laufenden Gateway. Anpassen, wenn dein Gateway woanders läuft
+  (anderer Port, LAN-IP, Tunnel, etc.). Per-Workspace oder global setzen.
+- **`pibo.sidecar.port`** (default: `4789`)
+  → Loopback-Port für den eingebetteten Sidecar, der ab VS Code 1.117.0
+  die Web-App im Sidebar hostet. Wird automatisch auf einen freien
+  Loopback-Port umgestellt, wenn der Default belegt ist.
+- **`pibo.sidecar.gatewayProbeTimeoutMs`** (default: `1500`)
+  → Timeout für die Erreichbarkeits-Probe des Gateway. Wenn die Probe
+  fehlschlägt, fällt die Sidebar auf den Empty-State-Shell zurück.
+Ändern via:
+- VS Code: Settings → "Pibo"
+- JSON: `"pibo.chatWebUrl": "http://192.168.1.50:4788"` in `.vscode/settings.json`
+- Env: `PIBO_CHAT_WEB_URL=http://...` (überschreibt alles)
+## 7a. Architektur (ab 1.4.0): Sidecar + Inlined SPA
+VS Code ab 1.117.0 hat die Workbench-CSP für Webviews verschärft
+(`frame-src 'self'`). Die ältere Sidebar-Implementierung hat das
+Chat-vscode-SPA über `window.location.replace('http://127.0.0.1:4788/...')`
+geladen — das wird seit 1.117.0 von der Workbench blockiert.
+Die neue Architektur umgeht die Sperre, ohne die Workbench-CSP zu lockern:
+1. **Sidecar** — eine kleine Node.js HTTP-Server-Instanz im Extension-Host,
+   gebunden an `127.0.0.1:<port>` (Default 4789). Proxied `/api/...`-Calls
+   vom Webview zum Gateway, hält die dev-auth-Cookie-Session im Speicher
+   und streamt Antworten 1:1 (wichtig für SSE). Bindet ausschließlich auf
+   Loopback, erzwingt `vscode-webview://`-CORS, niemals extern erreichbar.
+2. **Port-Mapping** — VS Code routet Anfragen an
+   `https://<webviewId>.vscode-resource.vscode-cdn.net:<port>` intern
+   auf `http://127.0.0.1:<port>` weiter. Diese Origin ist in der
+   Workbench-`connect-src` whitelisted.
+3. **Inlined Bundle** — der gebaute Vite-Output (`assets/index-*.js`,
+   `assets/index-*.css`) wird in den Webview-HTML als `<script nonce=...>`
+   und `<style nonce=...>` inlined. Dadurch umgehen wir die strikte
+   `script-src`-Direktive der Workbench.
+4. **Health-Probe** — beim Webview-Setup prüft der Sidecar, ob das
+   Gateway erreichbar ist. Wenn ja, inlined SPA. Wenn nein, klassische
+   Empty-State-Shell mit `pibo gateway:web`-Hinweis.
+Trade-offs und Sicherheitsanalyse stehen im Implementierungs-Plan
+`docs/plans/vscode-webview-sidecar-implementation-plan-2026-06-15.md`.
+## 8. Troubleshooting
+**"Gateway not available" / Sidebar zeigt Fehler**
+→ Ist `pibo gateway:web` gestartet? Auf `curl http://127.0.0.1:4788/api/chat/bootstrap` testen.
+**Sidebar zeigt "Swap fehlgeschlagen: dev-auth handshake did not complete"**
+→ Du betreibst das Production-Gateway (Better Auth / Google OAuth). Die VS-Code-Extension hat keinen Browser, kann den OAuth-Flow nicht durchlaufen, und braucht den lokalen Dev-Auth-Flow. Lösung: `pibo gateway:web --auth=local` starten oder `pibo config set auth.mode local && pibo gateway:web`. Die Sidebar swapt dann automatisch von der Shell zur inlined SPA.
+**Login funktioniert nicht**
+→ Google OAuth Client korrekt? Redirect-URI `http://127.0.0.1:4788/api/auth/callback/google` eingetragen? `pibo config show` zeigt deine Werte (redacted)?
+**Extension findet das Gateway nicht**
+→ Andere URL? `pibo.chatWebUrl` Setting prüfen. Für andere Maschine: `--web-host 0.0.0.0` beim Start, dann `pibo.chatWebUrl=http://<lan-ip>:4788` setzen.
+**Sidebar bleibt leer nach Workspace-Öffnen**
+→ In der Output-Panel → "Pibo" schauen. Steht dort der Grund? Meist: fehlender `code`-Binary auf PATH (Extension kann sich dann nicht installieren) oder Auth-Bridge-Problem.
+**Updates installieren**
+→ `pibo vscode install` zieht die neueste GitHub-Release-VSIX. So upgrade-st du.
+**Komplett zurücksetzen**
+```bash
+pibo vscode uninstall
+pibo vscode install
+```
+Plus VS Code: `Developer: Reload Window`.
+## 9. Wo die Daten liegen
+```text
+~/.pibo/                                    Pibo-User-State
+├── config.json                             deine `pibo config set` Werte
+├── pibo.sqlite                             Sessions, Rooms, Events (geteilt mit Web)
+└── vscode/cache/                           VSIX-Cache pro Release-Tag
+    ├── v1.3.0/pibo.vsix
+    └── last-installed.json
+<dein-workspace>/.pibo/                     Workspace-scoped State
+├── PROMPTS.md                              Custom Prompts
+└── pi-package.json                         Pi-Package-Registrierung
+```
+Mehr Details: <https://github.com/Pascapone/pibo>