ghosty-acp 0.0.52 → 0.0.53
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.59"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -164,6 +164,7 @@ legacy and always `true`.)
|
|
|
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
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
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
|
+
| "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») |
|
|
167
168
|
| "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) |
|
|
168
169
|
| "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id>` |
|
|
169
170
|
| "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>` |
|
|
@@ -175,7 +176,9 @@ legacy and always `true`.)
|
|
|
175
176
|
| "who was answering this number?", "which numbers/pages were left without an agent?" | `ghosty channels whatsapp integrations <id> --json` → `lastAnswer {agentName, at}` per number; `--orphans` lists only numbers nobody answers today that had turns (`channels messenger ls <id> --orphans` for pages). Give it back with `ghosty channels whatsapp enable <that-agent> <number> --dry-run`, then `--yes` after the user confirms |
|
|
176
177
|
| "change this paragraph / section of the prompt", "patch the prompt", "add this to the prompt" | write `{"edits":[{"what":"hours","find":"9 to 6","replace":"9 to 7"}]}` to a file and run `ghosty agents set <id> --prompt-patch edits.json --dry-run` (prints the diff), then without `--dry-run`. Append: `--prompt-append extra.md`. Applies on the server's CURRENT prompt (never `get --prompt-out` + `set --prompt-file` for a small change: it overwrites concurrent edits). An edit that doesn't find its place → 409, nothing changes |
|
|
177
178
|
| "who changed this?", "audit log", "what happened to this agent's channels?", "who logged in as whom" | `ghosty audit ls [--workspace slug] [--agent id] [--actor email] [--action agent\|channel\|card\|factory\|workspace] [--since 24h] --json` (staff see all; others only their workspaces/agents) |
|
|
178
|
-
| "
|
|
179
|
+
| "why did this run take so long?", "what did run N cost?", "where did @build spend its time?" | `ghosty factory runs show <n> --timing --workspace <slug> --json` (each role's turns with minutes, model, USD; clock split working / waiting for a person / other; commands ≥ 60 s). Long commands without output usually mean a hung test or a missing service in the work box |
|
|
180
|
+
| "how is the factory doing?", "cost per merged PR", "merge rate" | `ghosty factory runs stats --since 30d [--repo owner/repo] --workspace <slug> --json` |
|
|
181
|
+
| "list / show / rename a factory run", "who is @build?" | `ghosty factory runs ls --workspace <slug> [--room R]` (with time and cost), `ghosty factory runs show <n> --workspace <slug> [--full]`, `ghosty factory runs rename <n> "Title" --workspace <slug> --dry-run` then `--yes`; `ghosty agents ls --handle build [--workspace <slug>]` |
|
|
179
182
|
| "clean up the board / archive test cards" | `ghosty cards archive <id> --integration X \| --column X \| --before 30d --dry-run` first, then with `--yes` after the user confirms (reversible) |
|
|
180
183
|
| "which conversations does it have?" | `ghosty conversations ls <id> --json`; read one with `ghosty conversations show <id> <conv-id> --json` (`messages[]` with `role`, `text`); continue one with `ghosty chat <id> "…" --conversation <conv-id>` |
|
|
181
184
|
| "what's in its database? / fix this row" | `ghosty dbs query <id> <db> "SELECT …" [--arg V]… --json` (read only); `--write` only for a change the user asked for |
|