ghosty-acp 0.0.47 → 0.0.49

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.47",
3
+ "version": "0.0.49",
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.53"
8
+ version: "1.55"
9
9
  ---
10
10
 
11
11
  # Configure a Ghosty Studio agent
@@ -163,8 +163,16 @@ legacy and always `true`.)
163
163
  | "how much have I used? / am I out of usage?" | `ghosty usage --json` → `plan.name`, `week.pct` / `month.pct` (0–1), `exhausted` |
164
164
  | "let people try it without an account / share a demo" | `ghosty agents demo <id> --slug <name> [--expires "YYYY-MM-DDTHH:MM"] [--welcome T] [--starter T] [--chips "a\|b"] --json` then `ghosty agents demo enable <id>` → `url`; no flags = status; `--rotate` if the link leaked, `--off` to stop |
165
165
  | "what files are in my account?" | `ghosty me files ls [--kind document] --json`; `me files upload <path>`, `me files rm <file-id>` |
166
+ | "download / export / back up my files", "I want my files like in EasyBits" | `ghosty me files export --dry-run` (how many files and MB per folder), then `ghosty me files export --out <folder>` → `documents/`, `conversations/`, `library/`; rerunning only brings what's new. One file: `ghosty me files get <file-id> --out <path>` |
167
+ | "download / export / back up this database", "give me the table in Excel" | `ghosty dbs export <id> <db>` → `<db>.sqlite` (whole database); one table as CSV: `ghosty dbs export <id> <db> --table <t>` (`--out` to choose the path). On the web: /app/datos?tab=dbs → the database → **.sqlite** / **table.csv** |
166
168
  | "use my browser / do it in my Chrome" | install Ghosty for Chrome (https://www.ghosty.studio/chrome), stay signed in to ghosty.studio and open /c: it pairs alone. In personal chats and scheduled tasks the agent gets `browser_*` tools (never in customer channels); never types passwords. Guide: https://www.ghosty.studio/docs/navegador |
167
169
  | "what do my agents remember about me?" / "make it remember X" | `ghosty me memories ls --json`; `me memories add "X"` (app-wide, all agents), `edit <id> "…"`, `rm <id>` (only travels in personal chats) |
170
+ | "pause / resume this conversation", "stop the bot with this customer", "take it out of operator-only" | `ghosty cards pause <id> <folio\|phone> --mode 30min\|2h\|24h\|until_tomorrow\|permanent` (permanent = escalated, operator only) / `ghosty cards resume <id> <card>` (also lifts operator-only; it does NOT answer by itself). Both are logged |
171
+ | "answer the ones left pending", "detonate pending replies", "ask the bot to reply to this customer" | list first: `ghosty cards pending <id> [--since 2026-10-06T02:13Z\|12h] --json` → `cards[].flags` (paused, escalated, window_closed, reaction, not_whatsapp, no_agent: those are NEVER answered). Show the user how many would be answered (`--reply --dry-run`), and only after they confirm: `ghosty cards pending <id> --since … --reply --yes` (real customers get messages). One card: `ghosty cards reply <id> <card> [--directive "…"] --yes`. Never on a production conversation without the user's explicit OK |
172
+ | "who was answering this number?", "which numbers/pages were left without an agent?" | `ghosty channels whatsapp integrations <id> --json` → `lastAnswer {agentName, at}` per number; `--orphans` lists only numbers nobody answers today that had turns (`channels messenger ls <id> --orphans` for pages). Give it back with `ghosty channels whatsapp enable <that-agent> <number> --dry-run`, then `--yes` after the user confirms |
173
+ | "change this paragraph / section of the prompt", "patch the prompt", "add this to the prompt" | write `{"edits":[{"what":"hours","find":"9 to 6","replace":"9 to 7"}]}` to a file and run `ghosty agents set <id> --prompt-patch edits.json --dry-run` (prints the diff), then without `--dry-run`. Append: `--prompt-append extra.md`. Applies on the server's CURRENT prompt (never `get --prompt-out` + `set --prompt-file` for a small change: it overwrites concurrent edits). An edit that doesn't find its place → 409, nothing changes |
174
+ | "who changed this?", "audit log", "what happened to this agent's channels?", "who logged in as whom" | `ghosty audit ls [--workspace slug] [--agent id] [--actor email] [--action agent\|channel\|card\|factory\|workspace] [--since 24h] --json` (staff see all; others only their workspaces/agents) |
175
+ | "list / show / rename a factory run", "who is @build?" | `ghosty factory runs ls --workspace <slug> [--room R]`, `ghosty factory runs show <n> --workspace <slug> [--full]`, `ghosty factory runs rename <n> "Title" --workspace <slug> --dry-run` then `--yes`; `ghosty agents ls --handle build [--workspace <slug>]` |
168
176
  | "clean up the board / archive test cards" | `ghosty cards archive <id> --integration X \| --column X \| --before 30d --dry-run` first, then with `--yes` after the user confirms (reversible) |
169
177
  | "which conversations does it have?" | `ghosty conversations ls <id> --json`; read one with `ghosty conversations show <id> <conv-id> --json` (`messages[]` with `role`, `text`); continue one with `ghosty chat <id> "…" --conversation <conv-id>` |
170
178
  | "what's in its database? / fix this row" | `ghosty dbs query <id> <db> "SELECT …" [--arg V]… --json` (read only); `--write` only for a change the user asked for |
@@ -192,7 +200,7 @@ Read `references/api.md` for exact request/response shapes before calling.
192
200
  - **Restart is not free**: it cuts a turn in progress. Batch changes, restart once at the end.
193
201
  - Files go to the agent's working directory; tell the user the agent can `ls` them. Max 10 MB each.
194
202
  - Never print the token back to the user or into logs.
195
- - **Destructive commands need `--yes`** when you run them (no terminal): `agents rm`, `files rm`, `skills rm`, `credentials rm`, `board archive`, `dbs import` over existing rows, `channels whatsapp enable`, `channels wa groups enable`, `channels whatsapp link|unlink|history`, `channels wa import`, `agents unshare`, `boards move-cards`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
203
+ - **Destructive commands need `--yes`** when you run them (no terminal): `agents rm`, `files rm`, `skills rm`, `credentials rm`, `board archive`, `dbs import` over existing rows, `channels whatsapp enable`, `channels wa groups enable`, `channels whatsapp link|unlink|history`, `channels wa import`, `agents unshare`, `boards move-cards`, `cards reply`, `cards pending --reply`, `factory runs rename`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
196
204
 
197
205
  ## Verify
198
206