ghosty-acp 0.0.58 → 0.0.59
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.74"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -47,6 +47,16 @@ reaches only that agent (no `agents ls`, no `chat`).
|
|
|
47
47
|
Exit codes: `0` ok · `1` API error (read the message, don't retry blindly) · `2` usage error
|
|
48
48
|
(check `--help`) · `3` not signed in.
|
|
49
49
|
|
|
50
|
+
### From Claude or any MCP client: the account connector
|
|
51
|
+
|
|
52
|
+
To work with the user's agents from Claude, Claude Code or another MCP client (not to configure
|
|
53
|
+
them), the account exposes an OAuth MCP server at `https://www.ghosty.studio/mcp`:
|
|
54
|
+
`claude mcp add --transport http ghosty https://www.ghosty.studio/mcp` (or Claude → Settings →
|
|
55
|
+
Connectors → Add custom connector). The user approves the login once. Tools: `list_agents`,
|
|
56
|
+
`message_agent`, `get_agent_reply`, `list_conversations`, `read_conversation`, `crm_search_leads`,
|
|
57
|
+
`crm_read_lead`, `crm_reply_lead`, `crm_pause_lead`, `list_files`, `get_usage`, `whoami`. Docs:
|
|
58
|
+
https://www.ghosty.studio/docs/protocolos/conector-claude
|
|
59
|
+
|
|
50
60
|
### Fallback: raw HTTP
|
|
51
61
|
|
|
52
62
|
If Node is not available, use curl with the agent token. Base URL:
|
|
@@ -89,6 +99,7 @@ legacy and always `true`.)
|
|
|
89
99
|
| "which toolsets / connectors does it really have?" | `ghosty agents get <id> --fields toolsets,connectors --json` → effective `toolsets[]` and `connectors[]` with `connected`, `granted`, `effective` |
|
|
90
100
|
| "turn off most of Ghosty's skills" | `ghosty skills house <id> --only a,b --dry-run`, then without `--dry-run` (`--enable`/`--disable` for a few) |
|
|
91
101
|
| "one board per number / move these cards to another board" | `ghosty boards ls <workspace>`, `boards create <workspace> "<name>" --columns-from main`, `boards assign <agent-id> "<name>"`, `boards move-cards <workspace> --from main --to "<name>" --integration <formmy-id> --dry-run` then `--yes` after confirming; `boards rm <workspace> "<name>" --yes` deletes an empty one |
|
|
102
|
+
| "give X access to the workspace / board for a few days" (reviewer accounts) | `ghosty spaces members add <workspace> <email> --until 14d` (`--role admin` to let them invite), `ghosty boards access <workspace> <board> --add <email> --until 14d` (a whole-workspace board needs no list); `spaces members rm <workspace> <email> --yes` removes; `ghosty access why <email> <agent-id>` or `--workspace W --board B` explains why someone sees something |
|
|
92
103
|
| "edit its (long) prompt" | `ghosty agents get <id> --prompt-out PROMPT.md`, edit the file, `ghosty agents set <id> --prompt-file PROMPT.md` |
|
|
93
104
|
| "base its prompt on another agent's (a branch, a variant)" | write an overlay `{"edits":[{"what","find","replace","regex"?,"all"?}]}`, `ghosty agents set <id> --prompt-base <base-id> --prompt-overlay overlay.json --dry-run --out /tmp/p.md`, check, then without `--dry-run`. It regenerates when the base changes; its own prompt can't be edited while linked (`--prompt-base none` unlinks) |
|
|
94
105
|
| "give it the CRM / sales tools" | `ghosty agents set <id> --toolsets +crm` (a plain list replaces; `-x` removes) |
|
|
@@ -216,7 +227,7 @@ Read `references/api.md` for exact request/response shapes before calling.
|
|
|
216
227
|
- **Restart is not free**: it cuts a turn in progress. Batch changes, restart once at the end.
|
|
217
228
|
- Files go to the agent's working directory; tell the user the agent can `ls` them. Max 10 MB each.
|
|
218
229
|
- Never print the token back to the user or into logs.
|
|
219
|
-
- **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.
|
|
230
|
+
- **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`, `spaces members rm`, `cards reply`, `cards pending --reply`, `factory runs rename`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
220
231
|
|
|
221
232
|
## Verify
|
|
222
233
|
|
|
@@ -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.
|
|
8
|
+
version: "1.9"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Use the person's Chrome through Ghosty
|
|
@@ -106,6 +106,15 @@ OpenAPI: https://www.ghosty.studio/openapi.yaml (tag *Navegador*).
|
|
|
106
106
|
HTTP `session` gets its own tab in the "Ghosty" group: several agents drive the same Chrome at once
|
|
107
107
|
without stepping on each other, with no `tabId` needed. The first one uses the usual tab; the rest
|
|
108
108
|
open theirs in the background without stealing the visible one.
|
|
109
|
+
- **Tabs don't pile up.** When a `browser-mcp` process exits its tab is freed at once and closed
|
|
110
|
+
after 2 minutes; an agent that never says goodbye (a /c conversation, an HTTP script) frees its tab
|
|
111
|
+
after 5 idle minutes and it closes after 30. The tab the user is looking at is never closed.
|
|
112
|
+
- **Several steps in one call: `batch`.** When you can predict two or more steps, send them together:
|
|
113
|
+
`batch {actions:[{name:"navigate",input:{url}}, {name:"type",input:{target:"input[name=q]",text:"…",submit:true}}, {name:"wait_for",input:{text:"…"}}, {name:"get_page_text",input:{}}]}`.
|
|
114
|
+
One round trip instead of four; only the last step returns a snapshot. Steps run in order and the
|
|
115
|
+
batch stops at the first error, pending confirmation, captcha/2FA, dialog, or when the page changed
|
|
116
|
+
and the next step uses an old ref — after `navigate` (or a click that changes page) target with a
|
|
117
|
+
selector or `text`, not a ref. Use `wait_for` as the check that a step worked. Max 20 steps, no nesting.
|
|
109
118
|
- **Parallel tasks of the same agent: pass `tabId`.** `tabs {action:"new", url, background:true}`
|
|
110
119
|
returns a `tabId`; pass it to every call of that task (say, YouTube and TikTok, or two subagents
|
|
111
120
|
sharing one MCP process). Answers start with `[tab N]`.
|
|
@@ -124,7 +133,8 @@ OpenAPI: https://www.ghosty.studio/openapi.yaml (tag *Navegador*).
|
|
|
124
133
|
hanging. A click that opens another tab says `↗ … [tabId N]`. For screen recordings, arm with
|
|
125
134
|
`showMs` (≤ 3000) so the dialog stays visible a moment before it is answered.
|
|
126
135
|
- `status` returns `build` (hash of the running code) and `capabilities`: check them after the user
|
|
127
|
-
reloads the extension. `sessions` in `capabilities` = one tab per agent (older builds share one tab).
|
|
136
|
+
reloads the extension. `sessions` in `capabilities` = one tab per agent (older builds share one tab). `sessionEnd` = the tab
|
|
137
|
+
closes when the agent exits; `batch` = `batch` is available (older builds: call tools one by one).
|
|
128
138
|
- **`type` clears the field first** (rich editors too); `clear: false` appends. If the field ended
|
|
129
139
|
up different, the answer warns with ⚠️ — check it.
|
|
130
140
|
- **Tag/chip fields** (YouTube, TikTok): `type` with `slowly: true` and comma-separated text; the
|