ghosty-acp 0.0.60 → 0.0.62
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.85"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -111,6 +111,7 @@ legacy and always `true`.)
|
|
|
111
111
|
| "rotate / revoke the agent token", "the gat_ token leaked" | owner session only (a `gat_` token can't rotate itself): `ghosty agents token rotate <id> --yes` prints the new token ONCE on stdout — hand it to the user to store, never echo it into logs; `token revoke <id> --yes` closes the editor channel. On ACP engines it cuts the turn in flight |
|
|
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
|
+
| "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 |
|
|
114
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
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 |
|
|
116
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) |
|
|
@@ -159,6 +160,7 @@ legacy and always `true`.)
|
|
|
159
160
|
| "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) |
|
|
160
161
|
| "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` |
|
|
161
162
|
| "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) |
|
|
163
|
+
| "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 |
|
|
162
164
|
| "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` |
|
|
163
165
|
| "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 |
|
|
164
166
|
| "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 |
|
|
@@ -207,6 +209,8 @@ legacy and always `true`.)
|
|
|
207
209
|
| "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 |
|
|
208
210
|
| "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` |
|
|
209
211
|
| "how is the factory doing?", "cost per merged PR", "merge rate" | `ghosty factory runs stats --since 30d [--repo owner/repo] --workspace <slug> --json` |
|
|
212
|
+
| "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` |
|
|
213
|
+
| "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 |
|
|
210
214
|
| "list / show / rename a factory run", "who is @build?" | `ghosty factory runs ls --workspace <slug> [--room R]` (with time and cost), `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>]` |
|
|
211
215
|
| "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) |
|
|
212
216
|
| "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>` |
|
|
@@ -236,7 +240,7 @@ Read `references/api.md` for exact request/response shapes before calling.
|
|
|
236
240
|
- **Restart is not free**: it cuts a turn in progress. Batch changes, restart once at the end.
|
|
237
241
|
- Files go to the agent's working directory; tell the user the agent can `ls` them. Max 10 MB each.
|
|
238
242
|
- Never print the token back to the user or into logs.
|
|
239
|
-
- **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.
|
|
243
|
+
- **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`, `factory runs approve|changes|merge`. Confirm with the user BEFORE adding it; prefer `--dry-run` first where it exists.
|
|
240
244
|
|
|
241
245
|
## Verify
|
|
242
246
|
|
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ghosty-factory
|
|
3
|
-
description: Prepare and maintain a GitHub repo for the Ghosty Software Factory (@plan, @build, @check agents working from Ghosty Teams) — AGENTS.md, the docs/agents/ knowledge base, .ghosty/factory.md (which agent and model plays each role) and small, reviewable PRs. Use when the user mentions Ghosty Factory, Software Factory, @plan/@build/@check, .ghosty/factory.md, docs/agents or wants their repo "ready for agents".
|
|
3
|
+
description: Prepare and maintain a GitHub repo for the Ghosty Software Factory (@plan, @build, @check agents working from Ghosty Teams) — AGENTS.md, the docs/agents/ knowledge base, .ghosty/factory.md (which agent and model plays each role) and small, reviewable PRs. Use when the user mentions Ghosty Factory, Software Factory, @plan/@build/@check, .ghosty/factory.md, docs/agents or wants their repo "ready for agents". Also use it to DELEGATE work from your terminal to the factory with `ghosty factory run` ("hand this to the factory", "let @build do it", "open a factory run").
|
|
4
4
|
license: MIT
|
|
5
5
|
compatibility: Any git repository hosted on GitHub. Network access to https://www.ghosty.studio for the docs.
|
|
6
6
|
metadata:
|
|
7
7
|
author: ghosty-studio
|
|
8
|
-
version: "1.
|
|
8
|
+
version: "1.2"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Get a repo ready for the Ghosty Software Factory
|
|
@@ -92,6 +92,34 @@ Conventions of this repo that @plan, @build and @check must know:
|
|
|
92
92
|
migrations, dependencies, public API or `.github/`. Split big work.
|
|
93
93
|
- **`CODEOWNERS`** covering `.github/`, so a person reviews CI changes.
|
|
94
94
|
|
|
95
|
+
## 5. Delegate from your terminal
|
|
96
|
+
|
|
97
|
+
You (Claude Code, Codex…) can hand work to the factory and keep going with the user. It runs in
|
|
98
|
+
the repo's Teams room with the same plan, approvals and card as if the user typed it there.
|
|
99
|
+
|
|
100
|
+
**Delegate** long, self-contained work with a clear "done": a feature behind a flag, a refactor
|
|
101
|
+
with tests, a migration with a checklist, a bug with a reproduction. **Keep it** when it needs
|
|
102
|
+
back-and-forth with the user, it's a few lines, or you're still figuring out what to build.
|
|
103
|
+
|
|
104
|
+
0. If no room has the repo yet (`ghosty factory rooms ls --workspace <slug>`), connect it:
|
|
105
|
+
`ghosty factory rooms connect owner/repo --room <name> --create --workspace <slug>`. If it says
|
|
106
|
+
the GitHub App doesn't see the repo, give the user the link it prints. It also reports what the
|
|
107
|
+
repo is missing to be "ready for agents" (sections 1–4 above fix most of it).
|
|
108
|
+
1. Write the request like a ticket: the goal, why, how we'll know it's done (a check a person can
|
|
109
|
+
run), and the files or docs to read first. One request = one PR.
|
|
110
|
+
2. `ghosty factory run "<request>" --repo owner/repo --wait --workspace <slug> --json`. It returns
|
|
111
|
+
at `plan_review` with `next` (the exact commands). If the repo is in several rooms, add `--room`.
|
|
112
|
+
3. Show the user the plan (`ghosty factory runs show <n> --full`) and **ask before signing**:
|
|
113
|
+
`ghosty factory runs approve <n> --plan-version <N> --yes`. To send it back:
|
|
114
|
+
`ghosty factory runs changes <n> --note "…" --yes`.
|
|
115
|
+
4. `ghosty factory runs watch <n> --json` until `pr_review` (or `escalated`: show the points and
|
|
116
|
+
let the user choose `approve` = another loop, or `changes` = replan).
|
|
117
|
+
5. Show the PR and **ask before merging**: `ghosty factory runs merge <n> --yes`. If CI is still
|
|
118
|
+
running it queues and goes in when it passes.
|
|
119
|
+
|
|
120
|
+
Exit code 1 from `--wait`/`watch` only means the timeout ran out; run `watch` again. The user can
|
|
121
|
+
always follow along in the room; `ghosty factory runs card <n>` brings the live card down.
|
|
122
|
+
|
|
95
123
|
## Verify
|
|
96
124
|
|
|
97
125
|
- Every command in `AGENTS.md` runs.
|