ghosty-acp 0.0.73 → 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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ghosty-acp",
3
- "version": "0.0.73",
3
+ "version": "0.0.74",
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.105"
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's Meta's sign-in in the browser: `ghosty channels whatsapp connect <id>` (or `messenger connect`) opens the agent's Channels page; `--json` gives the URL to pass to the user |
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 |