ghosty-acp 0.0.63 → 0.0.65

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ghosty-acp",
3
- "version": "0.0.63",
3
+ "version": "0.0.65",
4
4
  "description": "Conecta tu editor a un agente ACP remoto. Puente entre entrada/salida estándar y WebSocket, sin dependencias.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -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.89"
8
+ version: "1.91"
9
9
  ---
10
10
 
11
11
  # Configure a Ghosty Studio agent
@@ -175,7 +175,7 @@ legacy and always `true`.)
175
175
  | "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 |
176
176
  | "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]` |
177
177
  | "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>` |
178
- | "I have a coupon", "redeem HACK2026", "create a coupon for the event" (staff) | `ghosty coupons redeem <CODE>` (one per account; adds balance and may lend a plan until a date). Or the link `https://www.ghosty.studio/canjear?codigo=<CODE>`. Staff: `ghosty coupons create <CODE> --credit 50 [--plan pro --until ISO] [--max N]` is born a draft; `ghosty coupons set <CODE> --on` turns it on; `ghosty coupons ls` |
178
+ | "I have a coupon", "redeem HACK2026", "create a coupon for the event" (staff) | `ghosty coupons redeem <CODE>` (one per account; adds balance and may lend a plan until a date). Or the link `https://www.ghosty.studio/canjear?codigo=<CODE>`. Staff: `ghosty coupons create <CODE> --credit 50 [--plan pro --until ISO] [--max N]` is born a draft; `ghosty coupons set <CODE> --on` turns it on; `ghosty coupons ls`; a lent plan that starts later: `--from ISO --redeem-by ISO --convert-promo STRIPE_CODE`; who redeemed and converted: `ghosty coupons show <CODE> --json` |
179
179
  | "sign in with Google in my app", "login with Google" | No Google console: the app copies `https://www.ghosty.studio/apps/auth/ghosty-login.mjs` (no deps), sends the button to `loginUrl({ returnTo, state })` and on the callback calls `verifyLogin(id_token)` → `{ sub, email, name, picture }`. `returnTo` must be `<slug>.ghosty.page` or a verified custom domain. Docs: /docs/apps |
180
180
  | "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 |
181
181
  | "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 |
@@ -226,6 +226,7 @@ legacy and always `true`.)
226
226
  | "tell @plan / an agent in Teams to…", "post this in the room / thread" | `ghosty teams post <workspace>#<room>[/<thread-message-id>] "@plan …" [--wait]` → posted as the user (no thread = new thread, like «Pedir»), the mentioned agent answers; `--wait` prints its answer. Only for something the user asked to send |
227
227
  | "have it speak in this Teams room / thread at 9" | `ghosty schedule add <id> "…" --teams <workspace>#<room>[/<thread-message-id>] --at ISO \| --in 30m` → it answers there as if mentioned; `ghosty schedule ls\|rm <id> [sched-id] --teams <workspace>` |
228
228
  | "have it do X every day / at 9 / remind me" | `ghosty schedule add <id> "…" --at ISO \| --in 30m [--every 12h --until ISO] [--title T]`; each run notifies the user's phone, an answer of exactly `OK` stays silent. `ghosty schedule ls|rm <id>` |
229
+ | "watch this page / tell me when it changes / track the competitor's prices" | `ghosty watch add <id> <url> [--every 24h] [--focus "heading or line"] [--instruction "what matters"] [--title T]` — the platform fetches it without a model turn and only opens a turn when it changed (never a `schedule --every` that checks a page: each tick is a paid turn). `ghosty watch check <id> <watch-id> --dry-run` shows the diff now without saving; `watch ls\|rm\|resume <id> [watch-id]`. Inside a chat the agent has `watch_add`/`watch_list`/`watch_remove` |
229
230
 
230
231
  Read `references/api.md` for exact request/response shapes before calling.
231
232