ghosty-acp 0.0.66 → 0.0.67
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.94"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -192,6 +192,7 @@ legacy and always `true`.)
|
|
|
192
192
|
| "answer in this WhatsApp group / make the group team or customer" | personal WhatsApp only: `ghosty channels wa groups ls <id> --json`, then confirm with the user and `ghosty channels wa groups enable <id> "<group>" --role equipo\|cliente --yes` (`--dry-run` first); a newly enabled group only answers when mentioned — `--wake all` to answer every message |
|
|
193
193
|
| "move / migrate this WhatsApp number from EasyBits or Formmy" | Business: find its Integration id and who answers it today with `ghosty channels whatsapp integrations <id> --json`, then `ghosty channels whatsapp link <id> --integration <formmy-id> --answer on\|off --dry-run --json` → show `plan`; confirm with the user (on = answers real customers), then without `--dry-run` and `--yes`; back: `unlink`. Its recent cards/messages/orders: `ghosty channels whatsapp history <id> --integration <formmy-id> --days 7 --dry-run` (works before linking), then without `--dry-run` (`--yes`; re-running never duplicates; it retries by itself during a deploy). It reports conversations that arrive paused by Formmy: list them with `ghosty cards ls <id> --paused --limit 200` and tell the user the agent won't answer those until they're resumed. Personal: `ghosty channels wa import <id> --from easybits:<agent-id> --own-number yes\|no --dry-run` (needs `EASYBITS_API_KEY`; prints whether the origin session is alive — if not, pair again instead), or `--from-file F` (EasyBits JSON) or `--from-dir DIR` (Baileys multi-file folder) `--own-number yes\|no --dry-run` (the user turns off EasyBits WITHOUT logout first), then `wa status` |
|
|
194
194
|
| "answer this WhatsApp number" | confirm with the user (real customers), then `ghosty channels whatsapp enable <id> <number> --yes`; `--dry-run` shows the plan |
|
|
195
|
+
| "is my Facebook page answering?", "turn the Messenger page on/off" | `ghosty channels messenger status <id>` (who answers each page, last webhook, token health from Meta); to switch: confirm with the user (real customers), then `ghosty channels messenger on <id> <page> --yes` (`--take` if another agent has it; `--dry-run` first); `off` keeps logging to the board |
|
|
195
196
|
| "save my ElevenLabs / MercadoPago key" | never put the key in a command: ask the user to run `ghosty credentials set <provider>` themselves (hidden prompt), or use `--from-env VAR` |
|
|
196
197
|
| "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) |
|
|
197
198
|
| "how much have I used? / am I out of usage?" | `ghosty usage --json` → `plan.name`, `week.pct` / `month.pct` (0–1), `exhausted` |
|
|
@@ -200,7 +201,8 @@ legacy and always `true`.)
|
|
|
200
201
|
| "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 |
|
|
201
202
|
| "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») |
|
|
202
203
|
| "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) |
|
|
203
|
-
| "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id
|
|
204
|
+
| "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id>[,<file-id>…] --yes` (or `--q <name> --dry-run` first) |
|
|
205
|
+
| "what did I attach / what is left in that conversation's box?" (pool agent) | `ghosty files ls <agent> adjuntos --session <conversation-id> --json`; `ghosty files rm <agent> <path> --session <conversation-id> --yes`. A paused box answers `paused` (it is never woken for this) |
|
|
204
206
|
| "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>` |
|
|
205
207
|
| "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** |
|
|
206
208
|
| "use my browser / do it in my Chrome" | install Ghosty for Chrome (https://www.ghosty.studio/chrome), stay signed in to ghosty.studio and open /c: it pairs alone. In personal chats and scheduled tasks the agent gets `browser_*` tools (never in customer channels); never types passwords. Guide: https://www.ghosty.studio/docs/navegador |
|
|
@@ -247,7 +249,7 @@ Read `references/api.md` for exact request/response shapes before calling.
|
|
|
247
249
|
- **Restart is not free**: it cuts a turn in progress. Batch changes, restart once at the end.
|
|
248
250
|
- Files go to the agent's working directory; tell the user the agent can `ls` them. Max 10 MB each.
|
|
249
251
|
- Never print the token back to the user or into logs.
|
|
250
|
-
- **Destructive commands need `--yes`** when you run them (no terminal): `agents rm`, `files rm`, `skills rm`, `credentials rm`, `board archive`, `dbs import` over existing rows, `channels whatsapp enable`, `channels wa groups enable`, `channels whatsapp link|unlink|history`, `channels wa import`, `agents unshare`, `boards move-cards`, `spaces members rm`, `cards reply`, `cards pending --reply`, `factory runs rename`, `factory runs approve|changes|merge`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
252
|
+
- **Destructive commands need `--yes`** when you run them (no terminal): `agents rm`, `files rm`, `skills rm`, `credentials rm`, `board archive`, `dbs import` over existing rows, `channels whatsapp enable`, `channels messenger on`, `channels wa groups enable`, `channels whatsapp link|unlink|history`, `channels wa import`, `agents unshare`, `boards move-cards`, `spaces members rm`, `cards reply`, `cards pending --reply`, `factory runs rename`, `factory runs approve|changes|merge`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
251
253
|
|
|
252
254
|
## Verify
|
|
253
255
|
|