ghosty-acp 0.0.54 → 0.0.56
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.62"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -144,6 +144,7 @@ legacy and always `true`.)
|
|
|
144
144
|
| "what did this agent run / did it leak anything" (support) | staff only: `ghosty conversations show <agent> <conversation> --tools` — every tool with its command (secrets masked) and the external domains it named; never while a turn runs there. Who sees a thread: `--why`; someone's threads: `ghosty conversations ls --user <email>` |
|
|
145
145
|
| "are images being metered / how much do images cost on Free" | staff only: `ghosty usage --images --plan free --since 7d [--by user]` — charges vs images agents delivered (far more deliveries than charges = the meter isn't reporting) and stored cost vs the table |
|
|
146
146
|
| "did the push reach them / did the announcement go out" | staff only: `ghosty push log --user <email> --since 2d` (announcements show as `novedad`); `ghosty novedades ls` shows delivered/rejected per announcement |
|
|
147
|
+
| "my site is paused / will pause", "keep my page online", "pin my site", "reactivate my page" | `ghosty sites ls` (state: pinned, paused, pauses on…), then `ghosty sites pin <slug>` — «Sitios fijos»: $49 USD/yr or $5 USD/mo ($990 / $99 MXN), includes up to 3 sites; never pauses, no banner. With a free slot it pins at once; otherwise it prints a card-payment link to hand over as is; `needs_pack` = all slots used: ask, then `--add-pack`. `--interval month`, `--currency mxn`. `ghosty sites unpin <slug>` frees a slot; `ghosty sites pins [--cancel]` |
|
|
147
148
|
| "publish this demo / landing as a Ghosty site", "change its URL / slug" | staff only: `ghosty sites publish <file.html|folder> --title T [--slug S]` (house site on EasyBits: no owner, no expiry, no banner); update it with `--site <slug>` (without it a NEW site is created); `ghosty sites slug <slug> <new-slug>`; `ghosty sites ls --house`. Exit 1 with `slug_unsupported` = EasyBits does not accept a slug yet: say so, don't retry |
|
|
148
149
|
| "turn this tool off for customers / in WhatsApp" | `ghosty agents get <id> --fields tools --json` → `tools.canales`, then `ghosty agents set <id> --tool wa:<tool>=off` (no channel = everywhere) |
|
|
149
150
|
| "put this face / avatar on the agent" | `ghosty agents set <id> --avatar <https-url or local png/jpg/webp>` → updates every Teams where it's active |
|
|
@@ -163,7 +164,7 @@ legacy and always `true`.)
|
|
|
163
164
|
| "how much have I used? / am I out of usage?" | `ghosty usage --json` → `plan.name`, `week.pct` / `month.pct` (0–1), `exhausted` |
|
|
164
165
|
| "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
166
|
| "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
|
+
| "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, typing bounce|flow|flashing|shimmer + typingColor for the "typing" dots; colors `#rrggbb`; patch per key, null resets one, `--style none` all). "Make the typing dots my brand color" → `--typing-color #rrggbb` (and `--typing flow|flashing|shimmer` to change the animation). 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
168
|
| "change what the widget says while it thinks / «Me estoy poniendo los lentes» doesn't fit my business / waiting messages" | `ghosty agents embed <id> --copy '{"waking":"Un momento, por favor","connecting":"Abriendo su expediente","thinking":["Revisando su consulta…","Consultando el expediente…"],"stillWorking":"Seguimos revisando su caso","showDuration":false}'` (keys: waking, connecting, thinking = 1–8 that rotate every 4 s, stillWorking (after 90 s), cantStart, interrupted, retryLabel — plain text ≤ 80 chars, no `<>` —, showDuration, showCopyButton true/false). Patch per key, `null` = Ghosty's phrase, `--copy none` all; `--copy-file texts.json`. Also in the card (Channels → Web widget → Advanced → Texts) and `<GhostyWidget copy>` / `useGhostyChat().copy` in React. Match the business tone (a law firm: formal «usted») |
|
|
168
169
|
| "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) |
|
|
169
170
|
| "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id>` |
|