ghosty-acp 0.0.56 → 0.0.58

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.56",
3
+ "version": "0.0.58",
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.62"
8
+ version: "1.72"
9
9
  ---
10
10
 
11
11
  # Configure a Ghosty Studio agent
@@ -95,7 +95,9 @@ legacy and always `true`.)
95
95
  | "share it with / give access to <email>" | `ghosty agents share <id> <email> [--role editor\|admin]` (keeps ownership); `ghosty agents shares <id>` lists; `unshare` needs `--yes` |
96
96
  | "put it in my Teams workspace", "activate it in Teams as @x", "change its handle", "take it out of Teams", "make it @build / @plan / @check", "change who does the factory roles" | `ghosty agents teams ls <id>` (workspaces you administer: where it answers, with which @handle), `ghosty agents teams on <id> <workspace> [--handle x]` (on an active one it changes the handle; `@ghosty` is reserved), `ghosty agents teams on <id> <workspace> --factory plan,build,check` (makes it those Software Factory roles; `ls` shows the roles it holds), `ghosty agents teams off <id> <workspace>` (pauses it; keeps the @handle), `ghosty agents teams rm <id> <workspace> --yes` (removes it, frees the handle; the agent stays). In the UI: agent page → Channels → Ghosty Teams |
97
97
  | "turn off / on this skill" | `ghosty skills disable\|enable <id> <slug>` (its own or one of Ghosty's; `skills ls` shows `on`) |
98
- | "delete this agent" | confirm with the user first, then `ghosty agents rm <id>` (owner only; `409` names the workspace where it is active) |
98
+ | "something in Ghosty is broken and I can't fix it", "talk to Ghosty / support" | `ghosty support open --title "<short>" --body "<what, when, what was tried>"` — support answers BY EMAIL; replying to that email adds to the case. `ghosty support ls` / `show <id>` / `reply <id> --body …` to follow up. The case carries the account and agents' recent errors; never paste secrets |
99
+ | "archive / pause this agent for good", "I don't use this agent anymore" | prefer archiving over deleting: `ghosty agents archive <id>` (stops answering everywhere, hidden, nothing deleted; deleted automatically after 7 days). `ghosty agents restore <id>` brings it back as it was; `ghosty agents ls --archived` lists them |
100
+ | "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) |
99
101
  | "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) |
100
102
  | "change the model" | `ghosty agents get <id> --json` (lists `models`), then `ghosty agents set <id> --model <model-id>` (restarts by itself) |
101
103
  | "make it think more / less" | Ghosty · Lite: `ghosty agents set <id> --env GHOSTY_THINKING_EFFORT=off\|low\|medium\|high\|max`. Codex: `--env FLEET_EFFORT=none\|minimal\|low\|medium\|high\|xhigh\|max` |
@@ -108,19 +110,20 @@ legacy and always `true`.)
108
110
  | "test it as a WhatsApp customer / with a photo / with earlier context" | `ghosty try <id> "…" --waba --session <made-up phone> [--media FILE] [--history FILE --reset] --json` → `sent[]` (what it would send, tools included: `kind` text/voice/file/rich with `rich` ubicacion/cita/boton/contacto/reaccion; nothing leaves). A customer attachment exactly as Formmy delivers it: add `--as-formmy` → `media.copied` |
109
111
  | "show me this customer's chat on the board / did the attachment arrive?" | `ghosty cards ls <id> [--q name-or-phone] --json`, then `ghosty cards show <id> <folio\|phone> [--limit 50] --json` → `messages[]` with `role`, `content`, `mediaType`, `mediaCopied` |
110
112
  | "replay these real conversations" | `ghosty try <id> --replay sample.json --out ./replay [--max N]`; read `./replay/replay.json`; `--resume` if it was cut |
111
- | "is it configured right? / why does it answer badly?" | `ghosty agents doctor <id> --json` → `checks[]` with `level` (ok/warn/error) and a `fix` command each; exit 1 = something to fix |
113
+ | "is it configured right? / why does it answer badly?" | `ghosty agents doctor <id> --json` → `info` (model, effort, native subagents, answers /c, box for staff) and `checks[]` with `level` (ok/warn/error) and a `fix` command each; exit 1 = something to fix |
112
114
  | "did it forget the conversation? / did it start from scratch?" | `ghosty turns ls <id> --session <conversation> --json` → each turn's `sdk.resumed` (false + `freshReason` orphan/stale/replaced = it lost its memory; `new` = first turn). Claude agents only |
113
115
  | "try my public demo as a visitor / does it remember after a box change?" | `ghosty demos try <slug> "…"` (same thread across runs; `--new` for a new visitor); memory across boxes: second message with `--recycle-between --agent <id>`. It counts against the demo's caps |
114
116
  | "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
117
  | "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
118
  | "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) |
119
+ | "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
120
  | "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
121
  | "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
122
  | "which workspaces do I have / where is X's workspace" | `ghosty spaces ls [--user <email>] --json` (others: staff) |
121
123
  | "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
124
  | "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
125
  | "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` |
126
+ | "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
127
  | "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
128
  | "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
129
  | "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 |
@@ -135,10 +138,13 @@ legacy and always `true`.)
135
138
  | "remove these env variables" | `ghosty agents set <id> --unset-env K1,K2` |
136
139
  | "which models can it use? / is this model valid?" | `ghosty engines ls --models --json` → `engines[].models[]` (`id`, `multiplier`, `ownKeyOnly`); an invalid `--model` is rejected with the valid list |
137
140
  | "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) |
141
+ | "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` |
142
+ | "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) |
138
143
  | "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` |
139
144
  | "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
145
  | "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
146
  | "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 |
147
+ | "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
148
  | "who changed this workspace? / when was it transferred?" | `ghosty spaces log <workspace> --since 30d --json` (owner or staff) → `events[]` with `actor`, `action`, `detail` |
143
149
  | "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
150
  | "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,9 +152,10 @@ legacy and always `true`.)
146
152
  | "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
153
  | "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
154
  | "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`, then `ghosty agents set <id> --tool wa:<tool>=off` (no channel = everywhere) |
155
+ | "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
156
  | "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
157
  | "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) |
158
+ | "start its box now / warm it up before a demo" | `ghosty agents box <id> --start` (no turn spent; 503 = the space's boxes are full) |
152
159
  | "how many boxes / how much capacity does it have?" | `ghosty agents box <id> --json` → `capacity`; per workspace: `ghosty usage --boxes --workspace <slug> --json` |
153
160
  | "apply the new plan now" | `ghosty plan apply <workspace> --dry-run`, show the changes and monthly total, confirm, then without `--dry-run` (`--yes`) |
154
161
  | "copy its data from EasyBits" | `ghosty dbs import <id> <db> --from easybits:<db-id> --dry-run` first (needs `EASYBITS_API_KEY`), show the plan (and `gsOnly`: rows written in gs that replacing would delete — then use `--tables` or `--append`), then run without `--dry-run` (`--yes` if replacing rows) |
@@ -187,6 +194,7 @@ legacy and always `true`.)
187
194
  | "stop giving it this database" | `ghosty dbs revoke <id> <db>` (prints the `grant` that undoes it) |
188
195
  | "give an agent to each of MY customers (partner)" | not for a normal owner: see https://www.ghosty.studio/docs/cli/partners.md (`ghosty partner --help`). Issue a credential without printing it: `ghosty partner credentials create --label prod --out-env .env.partner`; debug tools: `ghosty partner try <org> "…" --verbose`; several agents per partner: `--agent <slug>` on `partner agent get|apply` and `partner try`; a business's WhatsApp number: `channels whatsapp link <partner-agent-id> … --partner-tenant <org> --partner-agent <slug>`; WhatsApp groups of a partner agent: `ghosty partner wa groups ls|link <jid> --tenant <org> --agent <slug>|create|unlink`; a business's WABA number registered by the partner in Formmy: `ghosty partner waba links create --tenant <org> --agent nik-public` (url + secret for Formmy) then `set <id> --integration <formmy-id> --on` |
189
196
  | "work in my client's account / workspace" | `ghosty login --device --profile <client>`: give the client the printed link and code to approve; then add `--profile <client>` to every command (`ghosty logout --profile <client>` revokes it) |
197
+ | "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 |
190
198
  | "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>` |
191
199
  | "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>` |
192
200
 
@@ -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.7"
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
- - **Parallel work: always pass `tabId`.** `tabs {action:"new", url, background:true}` returns a
106
- `tabId`; pass it to every call of that task. Two agents/subagents (say, YouTube and TikTok) then
107
- run at once without stepping on each other or stealing the visible tab. Answers start with `[tab N]`.
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