ghosty-acp 0.0.50 → 0.0.52
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/package.json
CHANGED
|
@@ -5,7 +5,7 @@ license: MIT
|
|
|
5
5
|
compatibility: Needs Node 22+ (for npx @ghostystudio/cli) or curl, and network access to https://www.ghosty.studio
|
|
6
6
|
metadata:
|
|
7
7
|
author: ghosty-studio
|
|
8
|
-
version: "1.
|
|
8
|
+
version: "1.57"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -162,7 +162,9 @@ legacy and always `true`.)
|
|
|
162
162
|
| "remove this skill" | `ghosty skills rm <id> <slug> --yes` keeps a local copy and returns `restore`; `ghosty skills get <id> <slug> --out DIR` to back one up first (without `--out` it only lists) |
|
|
163
163
|
| "how much have I used? / am I out of usage?" | `ghosty usage --json` → `plan.name`, `week.pct` / `month.pct` (0–1), `exhausted` |
|
|
164
164
|
| "let people try it without an account / share a demo" | `ghosty agents demo <id> --slug <name> [--expires "YYYY-MM-DDTHH:MM"] [--welcome T] [--starter T] [--chips "a\|b"] --json` then `ghosty agents demo enable <id>` → `url`; no flags = status; `--rotate` if the link leaked, `--off` to stop |
|
|
165
|
-
| "put the agent on my website / chat bubble / web widget / embed" | `ghosty agents embed enable <id> --domains "<their-domain>,*.<their-domain>" [--welcome T] --json` → `snippet` (one `<script>`, paste before `</body>`; works on WordPress/Shopify/Wix). It only loads on those domains (ask the user which ones; https only). Needs engine `claude` (`engineOk`); if not, offer `ghosty agents set <id> --engine claude`. No flags = state; `--rotate` if the code leaked; `disable` to stop. Visitors are customers, each isolated; caps `--per-visitor`/`--per-ip`; failures in `lastError` |
|
|
165
|
+
| "put the agent on my website / chat bubble / web widget / embed" | `ghosty agents embed enable <id> --domains "<their-domain>,*.<their-domain>" [--welcome T] --json` → `snippet` (one `<script>`, paste before `</body>`; works on WordPress/Shopify/Wix). It only loads on those domains (ask the user which ones; https only). Needs engine `claude` or `ghosty-lite` (MiniGhosty) (`engineOk`); if not, offer `ghosty agents set <id> --engine claude`. No flags = state; `--rotate` if the code leaked; `disable` to stop. Visitors are customers, each isolated; caps `--per-visitor`/`--per-ip`; failures in `lastError` |
|
|
166
|
+
| "make the widget look like my site / change its name, avatar, colors, side, suggestions" | Same command, no re-paste needed (the bubble fetches its look): `--title T --subtitle T --avatar <https image>|none --icon chat|avatar|ghost --placeholder T --position right|left --offset X,Y --theme light|dark|auto --bubble-text T --auto-open S|off --starters "a|b"` (≤4 of THEIR suggestions; Ghosty's never show) and `--welcome T` = the first message. Fine style, no free CSS: `--style '{"fontFamily":"Barlow","radius":0,"headerBg":"#2d4a2e","titleUppercase":true,"statusDot":"#c8a96a","panelBg":"#fbf9f4","userBubbleBg":"#2d4a2e","agentBubbleBg":"#f3efe6","sendBg":"#f3efe6","sendArrow":"right","launcherBg":"#2d4a2e"}'` (keys: fontFamily from an allow-list, radius 0–24, headerBg/headerText, titleUppercase, statusDot, headerAvatar, panelBg, userBubbleBg/Text, agentBubbleBg/Text, inputBg, sendBg/sendIcon/sendArrow, launcherBg/launcherIcon; colors `#rrggbb`; patch per key, null resets one, `--style none` all). Take it from their brand: `--theme-source teams [--workspace SLUG]` or `--theme-source site --site-url <their site>` (imported as editable values). `ghosty agents embed <id> theme --json` exports it; `--style-file theme.json` applies it back. Errors come back as 400 with the reason |
|
|
167
|
+
| "use the widget from React / Next.js / draw my own chat / my design is very custom" | Pick by need: plain site (WordPress/Shopify/HTML) → the `<script>` (`snippet`). React and the usual bubble → `npm i @ghostystudio/widget` + `<GhostyWidget token="emb_…" />` (`ghosty agents embed <id> --json` → `react.install`/`react.code`; props `position`, `offsetX/Y`, `bubbleText`, `open`/`onOpenChange`, `style` = same keys as `--style`). Own UI with the logic solved → `useGhostyChat({ token })` → `{messages, send, stop, status, error}`. Own UI with NO dependency, code they edit (shadcn style) → `ghosty agents embed <id> --out src/components/GhostyChat.tsx` (`.jsx` without types; token + current theme baked as constants; `--force` to overwrite). Headless and `--out` call Ghosty from THEIR page: only works on the widget's `--domains` over https (CORS by exact origin; localhost is rejected) |
|
|
166
168
|
| "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id>` |
|
|
167
169
|
| "download / export / back up my files", "I want my files like in EasyBits" | `ghosty me files export --dry-run` (how many files and MB per folder), then `ghosty me files export --out <folder>` → `documents/`, `conversations/`, `library/`; rerunning only brings what's new. One file: `ghosty me files get <file-id> --out <path>` |
|
|
168
170
|
| "download / export / back up this database", "give me the table in Excel" | `ghosty dbs export <id> <db>` → `<db>.sqlite` (whole database); one table as CSV: `ghosty dbs export <id> <db> --table <t>` (`--out` to choose the path). On the web: /app/datos?tab=dbs → the database → **.sqlite** / **table.csv** |
|