ghosty-acp 0.0.75 → 0.0.77
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.110"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -142,13 +142,14 @@ legacy and always `true`.)
|
|
|
142
142
|
| "which workspaces do I have / where is X's workspace" | `ghosty spaces ls [--user <email>] --json` (others: staff) |
|
|
143
143
|
| "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) |
|
|
144
144
|
| "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 |
|
|
145
|
-
| "the agent should only answer new people on my number / don't let it answer my mom" | `ghosty channels whatsapp contacts <id> --integration <id>` (state: new-only, known contacts, muted) · `--new-only on` (skips people the owner already talks to: WhatsApp contacts + history + people the owner wrote first) · `--mute <phone>` (agent never answers that number) · `--allow <phone>` (agent always answers it, even if known) · `--unmute <phone>` (back to the general rule) · `--signature 👾|off` (prefix on the agent's messages so customers tell it from the owner; new numbers start with 👾) · `--seed` (bring known contacts again) · `--list [--q mom]` (the phone contacts with names and each rule; find a contact by name before muting it). Numbers connected from Channels start not answering, with new-only on: turn the number on once the known contacts show up |
|
|
145
|
+
| "the agent should only answer new people on my number / don't let it answer my mom" | `ghosty channels whatsapp contacts <id> --integration <id>` (state: new-only, known contacts, muted) · `--new-only on` (skips people the owner already talks to: WhatsApp contacts + history + people the owner wrote first) · `--mute <phone>` (agent never answers that number) · `--allow <phone>` (agent always answers it, even if known) · `--team <phone>` (that number is the owner's team, e.g. their other business line: the agent answers it in team mode, with no sales script, no lead card and no campaigns) · `--unmute <phone>` (back to the general rule) · `--signature 👾|off` (prefix on the agent's messages so customers tell it from the owner; new numbers start with 👾) · `--seed` (bring known contacts again) · `--list [--q mom]` (the phone contacts with names and each rule; find a contact by name before muting it). Numbers connected from Channels start not answering, with new-only on: turn the number on once the known contacts show up |
|
|
146
146
|
| "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` |
|
|
147
147
|
| "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 |
|
|
148
|
-
| "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, own_number) |
|
|
148
|
+
| "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, own_number, loop_brake = more than 30 messages from one contact in 10 min or 60 in 1 h, usually another bot; paused 2 h) |
|
|
149
149
|
| "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 |
|
|
150
150
|
| "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 |
|
|
151
151
|
| "set the quote issuer / VAT / folio prefix" (house `cotizar` tool) | `ghosty agents set <id> --quote iva=0,prefix=SFI,vigencia=15` (empty value clears: `rfc=`); `ghosty agents get <id> --fields cotizacion` to read it. An own skill named `cotizar` already turns the house tool off |
|
|
152
|
+
| "let the owner edit catalog prices themselves" (web, CSV or chatting with the agent) | Put the catalog in a database: `ghosty dbs create <id> catalogo` → `ghosty dbs import <id> catalogo --from csv:productos.csv --table productos` → `ghosty agents set <id> --quote catalogo_base=catalogo:productos`. Columns are detected by name (sku/clave/codigo, nombre, precio, unidad, categoria). If the database does not answer, the agent keeps quoting with the last good read or the `--catalog` list |
|
|
152
153
|
| "prices already include VAT except bulk / VAT only with invoice" | `ghosty agents set <id> --catalog productos.csv` (sku,nombre,precio,unidad,categoria) + `--quote iva-incluido=true,iva.GRANEL=16,solo-factura=true`; the category comes from the catalog, not the model; the agent passes `factura: true` when the customer asks for an invoice |
|
|
153
154
|
| "why was it slow? / where did the time go?" | `ghosty turns show <id> [turn-id] --json` → `byTool` (seconds per tool), `steps` (timeline), `totals.outputTokens`; pool engines only (`timeline: false` otherwise) |
|
|
154
155
|
| "is it running the new image? / it still behaves old" | `ghosty agents box <id> --check <path-the-new-image-brings> --json` → `stale`; if > 0, `ghosty agents box <id> --recycle`, one turn, check again (ACP: `agents restart`) |
|
|
@@ -175,6 +176,7 @@ legacy and always `true`.)
|
|
|
175
176
|
| "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>` |
|
|
176
177
|
| "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 |
|
|
177
178
|
| "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 |
|
|
179
|
+
| "what did my phone notify me / what is still waiting for me" | `ghosty notifications [--pending]` (= the app's «Avisos» bell; urgent sales ones stay pending until someone replies to that customer) |
|
|
178
180
|
| "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]`. "delete my site": confirm first, then `ghosty sites rm <slug> --yes` (can't be undone) |
|
|
179
181
|
| "how is my app", "is it awake", "what variables / tasks / files does it have" | `ghosty sites show <slug> --json` (status `site.wake.phase`: ready/starting/asleep/failed, never wakes it; variable NAMES only). Change: `ghosty sites env set <slug> NAME=value` · `env rm <slug> NAME`; tasks `ghosty sites cron ls|pause|resume|rm <slug> [id]`; files `ghosty sites files ls|rm <slug> [id]`. Errors (server + browser, grouped): `ghosty sites errors <slug> [--since 6h] [--req-id ID]`. The agent inside the app: `ghosty sites agent <slug>` (show) · `sites agent <slug> create` (Haiku 5.5) · `--agent <id>` / `--model m`. The person sees the same at `/c/sitios/<slug>` (tabs `?tab=datos` etc.) |
|
|
180
182
|
| "put my domain on my app", "use reservas.midominio.com", "custom domain" | `ghosty sites domain add <slug> <domain>` prints the DNS record (CNAME to `<slug>.ghosty.page` for a subdomain, A to the printed IP for the root); hand it over in one line. After they add it: `ghosty sites domain verify <slug> <domain>` (DNS can take minutes to a couple of hours; Cloudflare proxy off). Verified = the app answers at `https://<domain>`, HTTPS issued on the first visit. Apps with a backend only. `ghosty sites domain ls <slug>`, `rm <slug> <domain>` |
|
|
@@ -16,7 +16,7 @@ curl -s "$B" -H "Authorization: Bearer $GHOSTY_AGENT_TOKEN"
|
|
|
16
16
|
|
|
17
17
|
## PATCH /
|
|
18
18
|
Body: any of `{ "name", "model", "prompt", "webSearch": bool, "channels": { "teams": bool, "web": bool, "whatsapp": bool, "messenger": bool }, "starters": ["…up to 5, ≤80 chars"], "tools": { "gs": { "<name>": bool }, "extensions": { "<name>": bool } } }`.
|
|
19
|
-
Also `"channelRoles": { "teams": "equipo"|"cliente", "programado": … }` (who talks on that channel; the rest are fixed) and `"email": { "anyFromClients": bool }` (owner only: `enviar_correo` to any address from customer channels). CLI: `agents set --web-search --chat-starters --channel-roles --extensions --email-any`.
|
|
19
|
+
Also `"channelRoles": { "teams": "equipo"|"cliente", "programado": … }` (who talks on that channel; the rest are fixed) and `"email": { "anyFromClients": bool }` (owner only: `enviar_correo` to any address from customer channels). Also `"fallback": bool` (default true: if the owner's Claude key or subscription fails before answering, the turn is retried once with Haiku on Ghosty's key and billed to the plan). CLI: `agents set --web-search --fallback --chat-starters --channel-roles --extensions --email-any`.
|
|
20
20
|
`tools.gs` today: `programar_seguimiento` (schedule a future turn), `archivo_enviar` (send a file the agent produced — an https URL — to the person it is talking to: photo/audio/document on WhatsApp and Messenger, a link elsewhere) and `actualizar_identidad` (the agent rewrites or appends to its own prompt — it only works when the owner talks to it from Studio or the Mac app; from Messenger/WhatsApp/Teams the call is refused).
|
|
21
21
|
`tools.canales` decides per channel: `{ "canales": { "messenger": { "actualizar_identidad": false } } }` (channels: `chat` = Studio/Mac app, `teams`, `whatsapp`, `messenger`, `programado`, `prueba`; the GET returns the effective matrix). By default `actualizar_identidad` is only on in `chat`.
|
|
22
22
|
`tools` turns tools off (`false`) or back on (`true`) by name and merges with what is saved. `tools.gs` are the tools gs lends the agent (the GET lists them all with their state); `tools.extensions` are the machine's `config.yaml` extensions (`developer` = shell + files, `todo`, `analyze`, `easybits`…; `?full=1` returns the real list as `extensions`) and changing them restarts the machine. The veto is enforced: an off tool disappears from the list and is refused when called.
|