@psnext/slingcli 3.0.20260827-1 → 3.3.20260911-1

package/skills/s-help/resources/commands.json

@@ -0,0 +1,78 @@
+{
+  "generatedFrom": [
+    "slingshot/src/index.ts",
+    "slingshot/src/footer/index.ts",
+    "slingshot/src/filechanges/index.ts",
+    "slingshot/src/context/context.ts",
+    "slingshot/src/context/index.ts",
+    "slingshot/src/promptlib/index.ts",
+    "slingshot/src/skillmanager/index.ts"
+  ],
+  "commands": [
+    {
+      "command": "/s:footer",
+      "description": "Powerline-style footer (status line) with presets, shortcuts, fixed editor layout, welcome overlay, and more.",
+      "source": "slingshot/src/footer/index.ts"
+    },
+    {
+      "command": "/s:stash-history",
+      "description": "Save current editor prompt into a stash history and browse/insert recent prompts.",
+      "source": "slingshot/src/footer/index.ts"
+    },
+    {
+      "command": "/s:bash-mode",
+      "description": "Toggle bash mode for the editor/footer integration (shell session, transcript, completion).",
+      "source": "slingshot/src/footer/index.ts"
+    },
+    {
+      "command": "/s:bash-reset",
+      "description": "Reset bash mode / shell session state (emergency recovery).",
+      "source": "slingshot/src/footer/index.ts"
+    },
+    {
+      "command": "/s:filechanges",
+      "description": "Show files changed by sling and inspect diffs; includes accept/decline actions.",
+      "source": "slingshot/src/filechanges/index.ts"
+    },
+    {
+      "command": "/s:filechanges-accept",
+      "description": "Accept sling made changes (keeps files, clears log).",
+      "source": "slingshot/src/filechanges/index.ts"
+    },
+    {
+      "command": "/s:filechanges-decline",
+      "description": "Decline sling made changes (reverts files, clears log).",
+      "source": "slingshot/src/filechanges/index.ts"
+    },
+    {
+      "command": "/s:context",
+      "description": "Show context usage visualization.",
+      "source": "slingshot/src/context/context.ts"
+    },
+    {
+      "command": "/s:acm",
+      "description": "Enable agentic context management for the current session (context_tag/log/checkout tools).",
+      "source": "slingshot/src/context/index.ts"
+    },
+    {
+      "command": "/s:promptlib",
+      "description": "A library of reusable prompts from Slingshot (via MCP server).",
+      "source": "slingshot/src/promptlib/index.ts"
+    },
+    {
+      "command": "/s:skills-manager",
+      "description": "Enable/disable skills.",
+      "source": "slingshot/src/skillmanager/index.ts"
+    },
+    {
+      "command": "/s:settings",
+      "description": "Edit Slingshot settings (base URL, analytics domain, and IDs).",
+      "source": "slingshot/src/index.ts"
+    },
+    {
+      "command": "/s:debug",
+      "description": "Toggle Slingshot debug logging.",
+      "source": "slingshot/src/index.ts"
+    }
+  ]
+}

package/skills/s-help/resources/s-acm.md

@@ -0,0 +1,26 @@
+# /s:acm
+
+**Source:** `slingshot/src/context/index.ts`
+
+## What it does
+
+Enables **Agentic Context Management (ACM)** for the current session.
+
+This extension registers the internal tools:
+
+- `context_tag`
+- `context_log`
+- `context_checkout`
+
+…and provides a workflow to tag, inspect, and “checkout” (branch-with-summary) session history to manage context window size.
+
+## Usage
+
+- `/s:acm`
+
+You can pass an optional argument; if provided, the command will re-send it as a user message after enabling ACM.
+
+## Notes
+
+- Once enabled, the extension may prompt the agent to “use context-management skill”.
+- `context_checkout` injects a summary and then navigates the session tree; it also aborts the current ctx after turn_end to force the navigation.

package/skills/s-help/resources/s-bash-mode.md

@@ -0,0 +1,23 @@
+# /s:bash-mode
+
+**Source:** `slingshot/src/footer/index.ts`
+
+## What it does
+
+Toggles **bash mode** integration in the Slingshot footer/editor.
+
+When enabled, a managed shell session is started and the editor/footer can:
+
+- run shell commands
+- keep a transcript
+- provide command completion suggestions
+- track cwd and session state
+
+## Usage
+
+- `/s:bash-mode`
+
+## Notes
+
+- If a shell command is currently running, bash mode may refuse to disable until it finishes.
+- The toggle shortcut is configurable in settings (see `bashMode.toggleShortcut` in settings; defaults exist in code).

package/skills/s-help/resources/s-bash-reset.md

@@ -0,0 +1,23 @@
+# /s:bash-reset
+
+**Source:** `slingshot/src/footer/index.ts`
+
+## What it does
+
+Emergency reset for the bash-mode / fixed-editor terminal integration.
+
+Use this if bash mode or terminal split gets into a broken state (stuck session, UI weirdness, etc.).
+
+## Usage
+
+- `/s:bash-reset`
+
+## Notes
+
+This command is meant as recovery. It may dispose/reset internal state like:
+
+- managed shell session
+- transcript buffers
+- fixed-editor compositor
+
+(Exact behavior is implemented inside the footer extension.)

package/skills/s-help/resources/s-context.md

@@ -0,0 +1,25 @@
+# /s:context
+
+**Source:** `slingshot/src/context/context.ts`
+
+## What it does
+
+Shows a **context usage visualization** for the current session.
+
+It uses `ctx.getContextUsage()` (tokens, context window, percent) and produces an overlay with a rough breakdown of token usage categories such as:
+
+- System prompt
+- System tools
+- Messages
+- Tool calls/results
+- Available remaining context
+
+## Usage
+
+- `/s:context`
+
+## Notes
+
+If context usage info is not available, it will show a warning:
+
+- “Context usage info not available.”

package/skills/s-help/resources/s-filechanges-accept.md

@@ -0,0 +1,25 @@
+# /s:filechanges-accept
+
+**Source:** `slingshot/src/filechanges/index.ts`
+
+## What it does
+
+Accepts all currently tracked sling-made file changes:
+
+- keeps the files as they are now
+- clears the filechanges log/state
+
+## Usage
+
+- `/s:filechanges-accept`
+
+### Headless / no-UI
+
+Requires a confirmation override:
+
+- `/s:filechanges-accept force`
+
+## See also
+
+- `/s:filechanges`
+- `/s:filechanges-decline`

package/skills/s-help/resources/s-filechanges-decline.md

@@ -0,0 +1,30 @@
+# /s:filechanges-decline
+
+**Source:** `slingshot/src/filechanges/index.ts`
+
+## What it does
+
+Declines (reverts) all currently tracked sling-made file changes:
+
+- restores original baseline contents for edited files
+- deletes files that were created during tracking
+- clears the filechanges log/state
+
+## Usage
+
+- `/s:filechanges-decline`
+
+### Headless / no-UI
+
+Requires a confirmation override:
+
+- `/s:filechanges-decline force`
+
+## Warnings
+
+This operation can overwrite files and delete created files.
+
+## See also
+
+- `/s:filechanges`
+- `/s:filechanges-accept`

package/skills/s-help/resources/s-filechanges.md

@@ -0,0 +1,38 @@
+# /s:filechanges
+
+**Source:** `slingshot/src/filechanges/index.ts`
+
+## What it does
+
+Tracks and visualizes **files modified by the agent** (via `write`/`edit` tool calls) during the current session/branch, then lets you inspect diffs and either:
+
+- **accept** the changes (keep current files, clear the log)
+- **decline** the changes (revert files back to baseline, clear the log)
+
+It also adds a small UI widget/status indicator in the footer.
+
+## Usage
+
+- `/s:filechanges`
+
+### Interactive mode (UI)
+
+Shows a picker list:
+
+- “Accept changes (clear log)”
+- “Undo changes (revert)”
+- Individual files (pick one to view a `diff`)
+
+### Non-interactive mode (no UI)
+
+Prints a summary of changed files to stdout.
+
+## Related commands
+
+- `/s:filechanges-accept`
+- `/s:filechanges-decline`
+
+## Notes / Safety
+
+- Declining changes can **overwrite** files and delete created files.
+- In non-UI mode, accept/decline require `force` confirmation flags (see the specific commands).

package/skills/s-help/resources/s-footer.md

@@ -0,0 +1,38 @@
+# /s:footer
+
+**Source:** `slingshot/src/footer/index.ts`
+
+## What it does
+
+Enables/configures the Slingshot **powerline-style footer** (status line) experience.
+
+The footer implementation is large and featureful; it includes (non-exhaustive):
+
+- Powerline segments (model, cwd, git, token usage, etc.)
+- Presets (`default`, etc.)
+- Optional secondary row for overflow segments
+- Fixed-editor layout integration (required for certain jump/scroll behaviors)
+- Keyboard shortcuts (stash/copy/cut/jump/scroll)
+- “Welcome” overlay/header on startup
+- Bash-mode integration (shell session + transcript)
+
+## Usage
+
+In pi, run:
+
+- `/s:footer` — opens an interactive configuration UI (if UI is available) or toggles/configures behavior depending on how the command handler is implemented.
+
+## Key settings & files
+
+- Global settings: `~/.sling/agent/settings.json`
+- Project settings: `<project>/.sling/settings.json`
+- Stash history persistence: `~/.sling/agent/sling-footer/stash-history.json`
+- Session prompt history storage: `~/.sling/agent/sling-footer/sessions/**`
+
+## Notes
+
+- Some chat-jump features explicitly require fixed-editor mode:
+  - “Chat message jumps require /s:footer fixed-editor on”
+  - “Chat bottom jump requires /s:footer fixed-editor on”
+
+If you see those warnings, enable fixed-editor within the footer config.

package/skills/s-help/resources/s-promptlib.md

@@ -0,0 +1,28 @@
+# /s:promptlib
+
+**Source:** `slingshot/src/promptlib/index.ts`
+
+## What it does
+
+Opens a **Slingshot Prompt Library** browser.
+
+Implementation details:
+
+- Temporarily registers an MCP server config named `Slingshot-PromptLibrary`
+- Calls the MCP tool `list_prompts`
+- Presents a multi-step picker UI:
+  1. Select Account
+  2. Select Project
+  3. Select Prompt
+- Sends the selected prompt text back into chat as a follow-up message
+
+## Usage
+
+- `/s:promptlib`
+
+## Requirements / Notes
+
+- Requires a valid provider API key (resolved from `ctx.modelRegistry.getApiKeyForProvider(...)`).
+- Uses Slingshot OAuth credentials (projectId/workspaceId) for MCP headers.
+- On shutdown it removes the MCP server config.
+- Writes debug output to `tmp/prompts.json` in the current working directory.

package/skills/s-help/resources/s-skills-manager.md

@@ -0,0 +1,31 @@
+# /s:skills-manager
+
+**Source:** `slingshot/src/skillmanager/index.ts`
+
+## What it does
+
+Interactive UI to **enable/disable skills** by updating pi settings (similar to `pi config`).
+
+Features:
+
+- grouped by source (top-level vs package, user vs project)
+- search/filter
+  - plain text: matches skill name
+  - `/query`: matches full skill path
+  - `@query`: matches package/source
+- view modes (Tab cycles): By source / A–Z / Active first
+- writes `+pattern` / `-pattern` entries to settings
+- optionally prompts to `/reload` to apply changes
+
+## Usage
+
+- `/s:skills-manager`
+
+Non-interactive listing:
+
+- `/s:skills-manager list`
+
+## Notes
+
+- Uses `SettingsManager` + `DefaultPackageManager` to resolve skills.
+- In headless/no-UI mode, it will fall back to listing output.

package/skills/s-help/resources/s-stash-history.md

@@ -0,0 +1,26 @@
+# /s:stash-history
+
+**Source:** `slingshot/src/footer/index.ts`
+
+## What it does
+
+Provides a quick way to **stash** the current editor text into a small history list, and then later browse/insert those stashed prompts.
+
+This is designed for prompt iteration: you can save a prompt before trying a variant, then quickly restore earlier versions.
+
+## Usage
+
+- `/s:stash-history`
+
+Typically used via the footer shortcut (default shown in the footer code as `ctrl+alt+h`), but the command is also registered.
+
+## Persistence
+
+Stash history is persisted at:
+
+- `~/.sling/agent/sling-footer/stash-history.json`
+
+## Notes
+
+- History is capped (see `STASH_HISTORY_LIMIT` in the footer implementation).
+- Entries are compacted/deduped (no consecutive duplicates; whitespace-only entries skipped).

package/skills/screenshot/SKILL.md

@@ -0,0 +1,267 @@
+---
+name: "screenshot"
+description: "Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed."
+---
+
+
+# Screenshot Capture
+
+Follow these save-location rules every time:
+
+1) If the user specifies a path, save there.
+2) If the user asks for a screenshot without a path, save to the OS default screenshot location.
+3) If Codex needs a screenshot for its own inspection, save to the temp directory.
+
+## Tool priority
+
+- Prefer tool-specific screenshot capabilities when available (for example: a Figma MCP/skill for Figma files, or Playwright/agent-browser tools for browsers and Electron apps).
+- Use this skill when explicitly asked, for whole-system desktop captures, or when a tool-specific capture cannot get what you need.
+- Otherwise, treat this skill as the default for desktop apps without a better-integrated capture tool.
+
+## macOS permission preflight (reduce repeated prompts)
+
+On macOS, run the preflight helper once before window/app capture. It checks
+Screen Recording permission, explains why it is needed, and requests it in one
+place.
+
+The helpers route Swift's module cache to `$TMPDIR/codex-swift-module-cache`
+to avoid extra sandbox module-cache prompts.
+
+```bash
+bash <path-to-skill>/scripts/ensure_macos_permissions.sh
+```
+
+To avoid multiple sandbox approval prompts, combine preflight + capture in one
+command when possible:
+
+```bash
+bash <path-to-skill>/scripts/ensure_macos_permissions.sh && \
+python3 <path-to-skill>/scripts/take_screenshot.py --app "Codex"
+```
+
+For Codex inspection runs, keep the output in temp:
+
+```bash
+bash <path-to-skill>/scripts/ensure_macos_permissions.sh && \
+python3 <path-to-skill>/scripts/take_screenshot.py --app "<App>" --mode temp
+```
+
+Use the bundled scripts to avoid re-deriving OS-specific commands.
+
+## macOS and Linux (Python helper)
+
+Run the helper from the repo root:
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py
+```
+
+Common patterns:
+
+- Default location (user asked for "a screenshot"):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py
+```
+
+- Temp location (Codex visual check):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --mode temp
+```
+
+- Explicit location (user provided a path or filename):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --path output/screen.png
+```
+
+- App/window capture by app name (macOS only; substring match is OK; captures all matching windows):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --app "Codex"
+```
+
+- Specific window title within an app (macOS only):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --app "Codex" --window-name "Settings"
+```
+
+- List matching window ids before capturing (macOS only):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --list-windows --app "Codex"
+```
+
+- Pixel region (x,y,w,h):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --mode temp --region 100,200,800,600
+```
+
+- Focused/active window (captures only the frontmost window; use `--app` to capture all windows):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --mode temp --active-window
+```
+
+- Specific window id (use --list-windows on macOS to discover ids):
+
+```bash
+python3 <path-to-skill>/scripts/take_screenshot.py --window-id 12345
+```
+
+The script prints one path per capture. When multiple windows or displays match, it prints multiple paths (one per line) and adds suffixes like `-w<windowId>` or `-d<display>`. View each path sequentially with the image viewer tool, and only manipulate images if needed or requested.
+
+### Workflow examples
+
+- "Take a look at <App> and tell me what you see": capture to temp, then view each printed path in order.
+
+```bash
+bash <path-to-skill>/scripts/ensure_macos_permissions.sh && \
+python3 <path-to-skill>/scripts/take_screenshot.py --app "<App>" --mode temp
+```
+
+- "The design from Figma is not matching what is implemented": use a Figma MCP/skill to capture the design first, then capture the running app with this skill (typically to temp) and compare the raw screenshots before any manipulation.
+
+### Multi-display behavior
+
+- On macOS, full-screen captures save one file per display when multiple monitors are connected.
+- On Linux and Windows, full-screen captures use the virtual desktop (all monitors in one image); use `--region` to isolate a single display when needed.
+
+### Linux prerequisites and selection logic
+
+The helper automatically selects the first available tool:
+
+1) `scrot`
+2) `gnome-screenshot`
+3) ImageMagick `import`
+
+If none are available, ask the user to install one of them and retry.
+
+Coordinate regions require `scrot` or ImageMagick `import`.
+
+`--app`, `--window-name`, and `--list-windows` are macOS-only. On Linux, use
+`--active-window` or provide `--window-id` when available.
+
+## Windows (PowerShell helper)
+
+Run the PowerShell helper:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1
+```
+
+Common patterns:
+
+- Default location:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1
+```
+
+- Temp location (Codex visual check):
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 -Mode temp
+```
+
+- Explicit path:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 -Path "C:\Temp\screen.png"
+```
+
+- Pixel region (x,y,w,h):
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 -Mode temp -Region 100,200,800,600
+```
+
+- Active window (ask the user to focus it first):
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 -Mode temp -ActiveWindow
+```
+
+- Specific window handle (only when provided):
+
+```powershell
+powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 -WindowHandle 123456
+```
+
+## Direct OS commands (fallbacks)
+
+Use these when you cannot run the helpers.
+
+### macOS
+
+- Full screen to a specific path:
+
+```bash
+screencapture -x output/screen.png
+```
+
+- Pixel region:
+
+```bash
+screencapture -x -R100,200,800,600 output/region.png
+```
+
+- Specific window id:
+
+```bash
+screencapture -x -l12345 output/window.png
+```
+
+- Interactive selection or window pick:
+
+```bash
+screencapture -x -i output/interactive.png
+```
+
+### Linux
+
+- Full screen:
+
+```bash
+scrot output/screen.png
+```
+
+```bash
+gnome-screenshot -f output/screen.png
+```
+
+```bash
+import -window root output/screen.png
+```
+
+- Pixel region:
+
+```bash
+scrot -a 100,200,800,600 output/region.png
+```
+
+```bash
+import -window root -crop 800x600+100+200 output/region.png
+```
+
+- Active window:
+
+```bash
+scrot -u output/window.png
+```
+
+```bash
+gnome-screenshot -w -f output/window.png
+```
+
+## Error handling
+
+- On macOS, run `bash <path-to-skill>/scripts/ensure_macos_permissions.sh` first to request Screen Recording in one place.
+- If you see "screen capture checks are blocked in the sandbox", "could not create image from display", or Swift `ModuleCache` permission errors in a sandboxed run, rerun the command with escalated permissions.
+- If macOS app/window capture returns no matches, run `--list-windows --app "AppName"` and retry with `--window-id`, and make sure the app is visible on screen.
+- If Linux region/window capture fails, check tool availability with `command -v scrot`, `command -v gnome-screenshot`, and `command -v import`.
+- If saving to the OS default location fails with permission errors in a sandbox, rerun the command with escalated permissions.
+- Always report the saved file path in the response.