ghosty-acp 0.0.55 → 0.0.57
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.66"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -114,13 +114,14 @@ legacy and always `true`.)
|
|
|
114
114
|
| "stop it / it keeps working in the background" | `ghosty turns cancel <id> <conversation-id> --json` → `detenido` + `background` (video jobs, subagents, wake-ups canceled: nothing more is delivered) |
|
|
115
115
|
| "test it with this photo / PDF" | `ghosty try <id> "…" --media FILE` (repeatable) or `ghosty chat <id> "…" --media FILE`; as a WhatsApp customer add `--waba --session <phone>` |
|
|
116
116
|
| "do X to all agents that…" (staff) | `ghosty agents ls --sponsor <email> \| --owner <email> [--engine E] --ids`, then `xargs -I{} ghosty agents set {} … --dry-run` first |
|
|
117
|
-
| "clean up its history / delete the test chats" | `ghosty conversations rm <id> --kind test --before 7d --dry-run`, confirm, then without `--dry-run` (`--yes`); customer threads: `conversations archive <id> --kind channel` (never rm) |
|
|
117
|
+
| "clean up its history / delete the test chats" | `ghosty conversations rm <id> --kind test --before 7d --dry-run`, confirm, then without `--dry-run` (`--yes`); customer threads: `conversations archive <id> --kind channel` (never rm); only the user's own chats with it: `conversations rm <id> --kind personal --dry-run` (also gone from their apps) |
|
|
118
118
|
| "merge my duplicated documents" | `ghosty agents docs dedupe --dry-run`, show the merges, then `--yes`; two specific ones: `ghosty agents docs dedupe <keep-id> <drop-id>` |
|
|
119
119
|
| "use this file from my files in the chat" | `ghosty me files ls --q <name> --json` → id, then `ghosty chat <id> "…" --file <file-id>` |
|
|
120
120
|
| "which workspaces do I have / where is X's workspace" | `ghosty spaces ls [--user <email>] --json` (others: staff) |
|
|
121
121
|
| "no claude model fits / raise the model cap" (422 «caps at 0.25×») | staff: `ghosty spaces set <workspace> --model-cap 4 --dry-run`, then `--yes` (1 = up to Sonnet, none = its plan's) |
|
|
122
122
|
| "create a workspace" | `ghosty spaces create <slug> --dry-run`, then without `--dry-run` (yours, trial; same rules as the web: confirmed email, plan cap). `--combo` other than teams: staff |
|
|
123
123
|
| "bring only the ad leads from this number" | `ghosty channels whatsapp history <id> --integration <formmy-id> --dry-run --list --only-ads` → show which, then without `--dry-run` (`--yes`); new numbers: `channels whatsapp link … --ads-only on` |
|
|
124
|
+
| "this agent answers two numbers, keep their boards separate" | `ghosty channels whatsapp link <id> --integration <formmy-id> --board "<board>" --dry-run` per number (`--board agent` = back to the agent's); `channels whatsapp ls <id>` shows each number's board |
|
|
124
125
|
| "why did it fail? / it didn't answer" | `ghosty turns ls <id> --errors --since 24h --json` → failed turns with their `error`; a WhatsApp customer got NO turn at all: `ghosty turns ls <id> --skipped --since 24h --json` → `reason` (manual_mode, records_only, paused, reaction, channel_off, no_quota) |
|
|
125
126
|
| "what did it answer to that? / audit a reply" | `ghosty turns show <id> [turn-id] --json` → `input` (what came in) and `output` (what it answered), any engine or channel |
|
|
126
127
|
| "where did it say X? / find the turn where it quoted…" | `ghosty turns grep <id> "text" --since 7d [--role user\|agent] --json` → `matches[]` with `turnId` and `snippet`; then `turns show <id> <turnId>`. Text only, not tools |
|
|
@@ -139,6 +140,7 @@ legacy and always `true`.)
|
|
|
139
140
|
| "renew / extend this workspace" or "rename its slug" | staff only: `ghosty spaces renew <workspace> --until YYYY-MM-DD --dry-run`, confirm, then `--yes`; `ghosty spaces rename <old> <new> --dry-run` first |
|
|
140
141
|
| "make X the owner of this workspace / hand it over to the client" | staff only: `ghosty spaces transfer <workspace> --to <email> --keep-as admin --copy-keys --dry-run --json` → `keys.missing` (agents without a key stop answering) and `warnings`; confirm with the user, then without `--dry-run` plus `--yes`. Only the owner changes: agents, skills and history stay; documents, databases, boards and numbers its agents use move (`resources`); anything also used outside stays and shows in `warnings`. `--copy-keys` also copies the connectors (MercadoPago, Skydropx…) it lacks |
|
|
141
142
|
| "assign X (Ghosty staff) to this client" | staff only: `ghosty staff assign <staff-email> <client-email> --reason "…"` (`unassign` to remove, `staff ls`); the assigned person operates the client's agents, documents, databases and boards as themselves, without keys, billing or transfers |
|
|
143
|
+
| "archive / remove a workspace", "bring back an archived workspace" | owner or staff: `ghosty spaces archive <workspace> --dry-run` (shows status and agent count), confirm with the user, then `--yes`. Nothing is deleted: it leaves `/app` and `spaces ls`, agents and data stay. `ghosty spaces restore <workspace> --yes` undoes it |
|
|
142
144
|
| "who changed this workspace? / when was it transferred?" | `ghosty spaces log <workspace> --since 30d --json` (owner or staff) → `events[]` with `actor`, `action`, `detail` |
|
|
143
145
|
| "check X's health / X's app is stuck" (support) | staff only: `ghosty agents doctor --user <email> [agent]` — doctor, latest turns with «fetched» (`never` = their app didn't pick up a finished answer), plan/bag and boxes (duplicates flagged); `ghosty agents ls --user <email> --app android` shows their list and phones with the app build (old build = ask them to update) |
|
|
144
146
|
| "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>` |
|
|
@@ -146,7 +148,7 @@ legacy and always `true`.)
|
|
|
146
148
|
| "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
149
|
| "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]` |
|
|
148
150
|
| "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 |
|
|
149
|
-
| "turn this tool off for customers / in WhatsApp" | `ghosty agents get <id> --fields tools --json` → `tools.canales
|
|
151
|
+
| "turn this tool off for customers / in WhatsApp" | `ghosty agents get <id> --fields tools --json` → `tools.canales` (what really runs per channel), then `ghosty agents set <id> --tool wa:<tool>=off` (no channel = everywhere). Team tools (identity, notes, full board, the owner's personal accounts) never run for customers and `=on` can't open them; a whole connector per channel: agent page → Connectors |
|
|
150
152
|
| "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 |
|
|
151
153
|
| "remove this agent from the workspace" | irreversible (memory and files go too): confirm with the user, then `ghosty agents rm <id> --from-workspace --yes` (turns it off in every Teams, then deletes it) |
|
|
152
154
|
| "how many boxes / how much capacity does it have?" | `ghosty agents box <id> --json` → `capacity`; per workspace: `ghosty usage --boxes --workspace <slug> --json` |
|
|
@@ -164,7 +166,7 @@ legacy and always `true`.)
|
|
|
164
166
|
| "how much have I used? / am I out of usage?" | `ghosty usage --json` → `plan.name`, `week.pct` / `month.pct` (0–1), `exhausted` |
|
|
165
167
|
| "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 |
|
|
166
168
|
| "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` |
|
|
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; 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 |
|
|
169
|
+
| "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 |
|
|
168
170
|
| "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») |
|
|
169
171
|
| "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) |
|
|
170
172
|
| "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id>` |
|
|
@@ -5,7 +5,7 @@ license: MIT
|
|
|
5
5
|
compatibility: Needs curl or Node 18+, network access to https://www.ghosty.studio, and Chrome with the Ghosty extension signed in to ghosty.studio
|
|
6
6
|
metadata:
|
|
7
7
|
author: ghosty-studio
|
|
8
|
-
version: "1.
|
|
8
|
+
version: "1.8"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Use the person's Chrome through Ghosty
|
|
@@ -75,11 +75,11 @@ machine, set `GS_BROWSER_TOKEN` to the `btr_…` token from the panel (remote pa
|
|
|
75
75
|
```bash
|
|
76
76
|
curl -s https://www.ghosty.studio/api/browser/call \
|
|
77
77
|
-H "Authorization: Bearer $BT" -H "content-type: application/json" \
|
|
78
|
-
-d '{"tool":"navigate","input":{"url":"https://example.com"},"client":"Claude Code"}'
|
|
78
|
+
-d '{"tool":"navigate","input":{"url":"https://example.com"},"client":"Claude Code","session":"task-42"}'
|
|
79
79
|
```
|
|
80
80
|
|
|
81
81
|
`tool` accepts `navigate` or `browser_navigate`. `client` is the name the user sees in the
|
|
82
|
-
panel. `timeoutMs` defaults to 60000 (max 180000). `200` = result, `401` = token expired or
|
|
82
|
+
panel. `session` (optional, ≤ 80 chars) identifies your agent: each session gets its own tab. `timeoutMs` defaults to 60000 (max 180000). `200` = result, `401` = token expired or
|
|
83
83
|
revoked (renew it), `409` = browser not connected or extension too old (the `error` says which),
|
|
84
84
|
`504` = the tool failed or timed out (`error`).
|
|
85
85
|
|
|
@@ -102,9 +102,13 @@ OpenAPI: https://www.ghosty.studio/openapi.yaml (tag *Navegador*).
|
|
|
102
102
|
| Debug the user's site | `console_messages`, `network_requests` |
|
|
103
103
|
| Record what you did | `gif_creator` (`start_recording` → … → `stop_recording` → `export`) |
|
|
104
104
|
|
|
105
|
-
- **
|
|
106
|
-
`
|
|
107
|
-
|
|
105
|
+
- **Each agent has its own tab.** Every Ghosty conversation, every `browser-mcp` process and every
|
|
106
|
+
HTTP `session` gets its own tab in the "Ghosty" group: several agents drive the same Chrome at once
|
|
107
|
+
without stepping on each other, with no `tabId` needed. The first one uses the usual tab; the rest
|
|
108
|
+
open theirs in the background without stealing the visible one.
|
|
109
|
+
- **Parallel tasks of the same agent: pass `tabId`.** `tabs {action:"new", url, background:true}`
|
|
110
|
+
returns a `tabId`; pass it to every call of that task (say, YouTube and TikTok, or two subagents
|
|
111
|
+
sharing one MCP process). Answers start with `[tab N]`.
|
|
108
112
|
- **Uploads**: `read_page` ends with "Subir archivos" listing every `<input type=file>` (also the
|
|
109
113
|
HIDDEN ones behind a button) with a `ref`; pass it as `target` to `file_upload` with absolute paths.
|
|
110
114
|
- **Accounts/channels**: switch with the page's own account picker (avatar → "Switch account"; on
|
|
@@ -120,7 +124,7 @@ OpenAPI: https://www.ghosty.studio/openapi.yaml (tag *Navegador*).
|
|
|
120
124
|
hanging. A click that opens another tab says `↗ … [tabId N]`. For screen recordings, arm with
|
|
121
125
|
`showMs` (≤ 3000) so the dialog stays visible a moment before it is answered.
|
|
122
126
|
- `status` returns `build` (hash of the running code) and `capabilities`: check them after the user
|
|
123
|
-
reloads the extension.
|
|
127
|
+
reloads the extension. `sessions` in `capabilities` = one tab per agent (older builds share one tab).
|
|
124
128
|
- **`type` clears the field first** (rich editors too); `clear: false` appends. If the field ended
|
|
125
129
|
up different, the answer warns with ⚠️ — check it.
|
|
126
130
|
- **Tag/chip fields** (YouTube, TikTok): `type` with `slowly: true` and comma-separated text; the
|