ghosty-acp 0.0.72 → 0.0.74
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.107"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -112,7 +112,7 @@ legacy and always `true`.)
|
|
|
112
112
|
| "teach it a rule for everyone", "from now on don't offer X", "add / turn off a promo" | `ghosty agents memory ls <id> --json`; rule: `memory add <id> "…" [--scope wa]` (travels in every conversation, also with customers), `memory edit <id> <rule-id> "…"`, `memory rm <id> <id>`; promo: `memory add <id> --promo --title T --details D [--from YYYY-MM-DD] [--until YYYY-MM-DD]`, `memory enable|disable <id> <promo-id>`. Personal preferences of the user go in `me memories` instead |
|
|
113
113
|
| "give / hand over this agent to someone", "move it to another workspace" | `ghosty agents transfer <id> --to EMAIL [--workspace THEIR-SLUG] --dry-run`, show the plan and warnings (missing provider key), confirm with the user, then without `--dry-run` + `--yes`. Between the user's own workspaces: `--workspace SLUG|none` (none = personal; `--force` only if they accept cutting a running turn). Owner session, never the `gat_` token |
|
|
114
114
|
| "put my agent in Microsoft Teams" (MTeams; not Ghosty Teams) | the company creates a Single Tenant **Azure Bot** (F0) in its own Azure and adds the Teams channel; then `ghosty channels mteams connect <id> --app-id <guid> --tenant <guid> [--name N]` with the client secret in `GHOSTY_MTEAMS_SECRET` (Ghosty tests it with Microsoft); paste the returned messaging endpoint in the Azure Bot → Configuration; `ghosty channels mteams zip <id> <bot> --out F.zip` and the Teams admin uploads it in Manage apps. No app store. The admin can try it first with Azure's “Test in Web Chat”. If it stays silent, `ghosty channels mteams ls <id>` shows the last problem (`lastError`: e.g. "el token no es para este bot" = endpoint pasted into another Azure Bot). Docs: /docs/canales/microsoft-teams |
|
|
115
|
-
| "connect WhatsApp Business / Messenger" | it'
|
|
115
|
+
| "connect WhatsApp Business / Messenger" | `ghosty channels whatsapp connect <id> --json` starts or resumes the connection and gives `url`: pass it to the user, it works for 1 h on any screen (if the phone doesn't finish Meta's sign-in, open it on a computer). Run it again to see `state`: `pending` or `connected`. It needs no balance and doesn't turn the agent on. Messenger: `messenger connect` opens Channels |
|
|
116
116
|
| "pay / upgrade the plan / invoices / change the card" | `ghosty plan open [workspace]` opens the plan page (Stripe); without a workspace (or `personal`) the personal plan at /c/uso; `--json` gives the URL |
|
|
117
117
|
| "delete this agent" | offer `archive` first (reversible for 7 days); if they still want it gone, confirm, then `ghosty agents rm <id>` (owner only; `409` names the workspace where it is active) |
|
|
118
118
|
| "switch it to another engine" | `ghosty agents set <id> --engine <engine> [--model <model-id>] --dry-run` first (says what is forgotten and which machine is replaced; `ok:false` if it is busy), then the same without `--dry-run`. The model belongs to the NEW engine; each conversation keeps its history (gs passes it on its first turn) |
|
|
@@ -162,6 +162,7 @@ legacy and always `true`.)
|
|
|
162
162
|
| "how much did this workspace use / which agent spends most / messages left without balance" | `ghosty usage --workspace <slug> --by agent,day --days 14 --json` → `rows`, `agents` (turns, failed, billable, noQuota); the unanswered ones: `ghosty turns ls --workspace <slug> --quota-hits --json` (owner or staff) |
|
|
163
163
|
| "how much does this agent cost / API equivalent / spend of /c vs Messenger" | `ghosty usage --agent <id> --by model,day,canal --cost --json` → `rows` (day, model, canal, tokens, `usd` at provider list price) and `totalUsd`; its turns per channel: `ghosty turns ls <id> --canal anon --json` |
|
|
164
164
|
| "who answers /c without an account / turn native subagents on for X" or "give this agent a bigger box" | staff only: `ghosty settings ls`, `ghosty settings set ANON_NATIVE_AGENT_ID <agent-id>` (`unset` = back to the default), `ghosty settings set NATIVE_SUBAGENT_AGENTS +<agent-id>`; box: `ghosty agents set <id> --box 4096:10` (MB:conversations, recycles its boxes) |
|
|
165
|
+
| "the new app version is out, show the update notice" / "force people to update" | staff only: `ghosty app ls`, then `ghosty app suggest <build>` (iOS; `--platform android|notch`) once that build is live in the store; `ghosty app min <build> --yes` only if the old one breaks something (never above suggest) |
|
|
165
166
|
| "did a Meta campaign pause? / why are no ad leads coming in?" | staff only: `ghosty ads watch` (accounts, active campaigns, token expiry, last ad lead per ads-only number) and `ghosty ads watch run --dry-run` (what it would alert now). Alerts reach staff by themselves every hour |
|
|
166
167
|
| "give this agent its own token bag / make it one-time" | staff only: `ghosty bags ls <workspace>`, `ghosty bags create <workspace> "<bag>" --tokens 20M [--recurring off]`, `ghosty agents set <id> --bag "<bag>"`; change: `ghosty bags set <workspace> "<bag>" --tokens 30M` |
|
|
167
168
|
| "move this workspace to pro / give it a plan as a courtesy" | staff only: `ghosty spaces plan <workspace> trial|pro|empresarial [--courtesy] [--until YYYY-MM-DD] [--note "…"] --dry-run --json` → `before`/`after` (plan, modelCap, tokensUsed/tokensIncluded, hardCap, paidUntil) and `warnings`; confirm, then `--yes`. Never charges Stripe nor emails the customer |
|
|
@@ -175,7 +176,7 @@ legacy and always `true`.)
|
|
|
175
176
|
| "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 |
|
|
176
177
|
| "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 |
|
|
177
178
|
| "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]` |
|
|
178
|
-
| "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 person sees the same at `/c/sitios/<slug>` (tabs `?tab=datos` etc.) |
|
|
179
|
+
| "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.) |
|
|
179
180
|
| "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>` |
|
|
180
181
|
| "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` |
|
|
181
182
|
| "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 |
|
|
@@ -232,7 +233,7 @@ legacy and always `true`.)
|
|
|
232
233
|
| "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>` |
|
|
233
234
|
| "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>` |
|
|
234
235
|
| "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` |
|
|
235
|
-
| "my morning brief", "stop the morning summary", "send it at 8", "without the audio" | `ghosty brief` (on/off, voice, time, days, last sent); `ghosty brief on\|off`; `ghosty brief --at 8:15 --days 1-5 --voice off` (any subset; `--days all\|weekdays\|0,6`). `ghosty brief run --dry-run` builds today's with its voice note and prints it (sends nothing); `brief run` sends it now. It is the ONLY morning notice: lands in the latest personal chat with a voice note and a push, only when there's something. Inside a chat the agent has `daily_brief_set` |
|
|
236
|
+
| "my morning brief", "stop the morning summary", "send it at 8", "without the audio" | `ghosty brief` (on/off, voice, time, days, last sent); `ghosty brief on\|off`; `ghosty brief --at 8:15 --days 1-5 --voice off` (any subset; `--days all\|weekdays\|0,6`); `ghosty brief pause 7` or `pause 2026-11-20` skips it and it comes back on its own, `ghosty brief resume` removes the pause. `ghosty brief run --dry-run` builds today's with its voice note and prints it (sends nothing); `brief run` sends it now. It is the ONLY morning notice: lands in the latest personal chat with a voice note and a push, only when there's something. Inside a chat the agent has `daily_brief_set` |
|
|
236
237
|
| "how does the voice sound / say this in the voice notes' voice / does it have a Mexican accent" | `ghosty tts "text" [--voice em_santa\|em_alex\|ef_dora] [--out voz.wav]` then `afplay voz.wav` — the house voice (Kokoro, Mexican Spanish es-419, pronunciation lexicon: write brand names normally, never phonetically). Up to 400 characters |
|
|
237
238
|
|
|
238
239
|
Read `references/api.md` for exact request/response shapes before calling.
|