ghosty-acp 0.0.67 → 0.0.69
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.100"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -142,6 +142,7 @@ legacy and always `true`.)
|
|
|
142
142
|
| "which workspaces do I have / where is X's workspace" | `ghosty spaces ls [--user <email>] --json` (others: staff) |
|
|
143
143
|
| "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) |
|
|
144
144
|
| "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 |
|
|
145
|
+
| "the agent should only answer new people on my number / don't let it answer my mom" | `ghosty channels whatsapp contacts <id> --integration <id>` (state: new-only, known contacts, muted) · `--new-only on` (skips people the owner already talks to: WhatsApp contacts + history + people the owner wrote first) · `--mute <phone>` (agent never answers that number) · `--allow <phone>` (agent always answers it, even if known) · `--unmute <phone>` (back to the general rule) · `--signature 👾|off` (prefix on the agent's messages so customers tell it from the owner; new numbers start with 👾) · `--seed` (bring known contacts again) · `--list [--q mom]` (the phone contacts with names and each rule; find a contact by name before muting it). Numbers connected from Channels start not answering, with new-only on: turn the number on once the known contacts show up |
|
|
145
146
|
| "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` |
|
|
146
147
|
| "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 |
|
|
147
148
|
| "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, own_number) |
|
|
@@ -215,6 +216,7 @@ legacy and always `true`.)
|
|
|
215
216
|
| "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) |
|
|
216
217
|
| "why did this run take so long?", "what did run N cost?", "where did @build spend its time?" | `ghosty factory runs show <n> --timing --workspace <slug> --json` (each role's turns with minutes, model, USD; clock split working / waiting for a person / other; commands ≥ 60 s). Long commands without output usually mean a hung test or a missing service in the work box |
|
|
217
218
|
| "why did run N fail / get stuck?", "what should we change so it doesn't happen again?" | `ghosty factory runs why <n> --workspace <slug> --json` (category — `approved_unmet_criterion` first when a plan criterion like "in the preview" was approved without evidence, see `acceptance[]` —, impact, critical step with evidence, typed actions: role_rules → `.ghosty/factory.md`, repo_setup, skill, prompt; `--refresh` redoes it). Stuck patterns per step are in `runs show <n> --timing` |
|
|
219
|
+
| "the run is escalated, what do I pick?", "a or b", "merge it as it is" | `ghosty factory runs choose <n> --workspace <slug>` lists the 2–3 paths @check left (a/b/c with their action); `ghosty factory runs choose <n> <letter> --yes` applies one and the choice reaches the next role word for word. `merge_as_is` merges with red CI that the PR did not cause (logged as `merge_override`): confirm with the user first. `fix_main` opens a separate run that fixes the main branch (it waits for the owner's signature); the escalated run then shows «Waiting for the main fix (#N)» and resumes on its own when that fix merges |
|
|
218
220
|
| "how is the factory doing?", "cost per merged PR", "merge rate" | `ghosty factory runs stats --since 30d [--repo owner/repo] --workspace <slug> --json` |
|
|
219
221
|
| "connect this repo to the factory", "create a factory room", "set up the factory for <repo>" | `ghosty factory rooms connect owner/repo --room <name> --create --workspace <slug> --json` (checks the GitHub App sees it; returns `readiness` = what's missing); `ghosty factory rooms ls --workspace <slug>`; `rooms disconnect … --yes` |
|
|
220
222
|
| "hand this to the factory", "let the factory build it", "delegate this PR", "send it to @plan" | `ghosty factory run "<goal, why, how we know it's done>" --repo owner/repo --wait --workspace <slug> --json` → it returns at `plan_review` with `next` (the commands). Show the user the plan (`runs show <n> --full`) and ask before `runs approve <n> --plan-version N --yes`; then `runs watch <n>` until `pr_review` and ask before `runs merge <n> --yes`. `runs changes <n> --note "…"` sends it back; `runs card <n>` brings the live card down. More in the `ghosty-factory` skill |
|
|
@@ -249,7 +251,7 @@ Read `references/api.md` for exact request/response shapes before calling.
|
|
|
249
251
|
- **Restart is not free**: it cuts a turn in progress. Batch changes, restart once at the end.
|
|
250
252
|
- Files go to the agent's working directory; tell the user the agent can `ls` them. Max 10 MB each.
|
|
251
253
|
- Never print the token back to the user or into logs.
|
|
252
|
-
- **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 messenger on`, `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`, `factory runs approve|changes|merge`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
254
|
+
- **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 messenger on`, `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`, `factory runs approve|changes|merge|choose`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
253
255
|
|
|
254
256
|
## Verify
|
|
255
257
|
|