ghosty-acp 0.0.69 → 0.0.71
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.102"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -219,7 +219,7 @@ legacy and always `true`.)
|
|
|
219
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 |
|
|
220
220
|
| "how is the factory doing?", "cost per merged PR", "merge rate" | `ghosty factory runs stats --since 30d [--repo owner/repo] --workspace <slug> --json` |
|
|
221
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` |
|
|
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 |
|
|
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. A run that stopped moving: ask, then `runs resume <n> --yes` (`runs stop|cancel <n>` too). More in the `ghosty-factory` skill |
|
|
223
223
|
| "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>]` |
|
|
224
224
|
| "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) |
|
|
225
225
|
| "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>` |
|
|
@@ -231,6 +231,7 @@ legacy and always `true`.)
|
|
|
231
231
|
| "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>` |
|
|
232
232
|
| "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>` |
|
|
233
233
|
| "watch this page / tell me when it changes / track the competitor's prices" | `ghosty watch add <id> <url> [--every 24h] [--focus "heading or line"] [--instruction "what matters"] [--title T]` — the platform fetches it without a model turn and only opens a turn when it changed (never a `schedule --every` that checks a page: each tick is a paid turn). `ghosty watch check <id> <watch-id> --dry-run` shows the diff now without saving; `watch ls\|rm\|resume <id> [watch-id]`. Inside a chat the agent has `watch_add`/`watch_list`/`watch_remove` |
|
|
234
|
+
| "my morning brief", "stop the morning summary", "send it at 8", "without the audio" | `ghosty brief` (on/off, voice, time, days, last sent); `ghosty brief on\|off`; `ghosty brief --at 8:15 --days 1-5 --voice off` (any subset; `--days all\|weekdays\|0,6`). `ghosty brief run --dry-run` builds today's with its voice note and prints it (sends nothing); `brief run` sends it now. It is the ONLY morning notice: lands in the latest personal chat with a voice note and a push, only when there's something. Inside a chat the agent has `daily_brief_set` |
|
|
234
235
|
| "how does the voice sound / say this in the voice notes' voice / does it have a Mexican accent" | `ghosty tts "text" [--voice em_santa\|em_alex\|ef_dora] [--out voz.wav]` then `afplay voz.wav` — the house voice (Kokoro, Mexican Spanish es-419, pronunciation lexicon: write brand names normally, never phonetically). Up to 400 characters |
|
|
235
236
|
|
|
236
237
|
Read `references/api.md` for exact request/response shapes before calling.
|
|
@@ -5,7 +5,7 @@ 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.3"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Get a repo ready for the Ghosty Software Factory
|
|
@@ -117,6 +117,10 @@ back-and-forth with the user, it's a few lines, or you're still figuring out wha
|
|
|
117
117
|
5. Show the PR and **ask before merging**: `ghosty factory runs merge <n> --yes`. If CI is still
|
|
118
118
|
running it queues and goes in when it passes.
|
|
119
119
|
|
|
120
|
+
If a run stopped moving (nobody working, the card says «Not moving»), ask the user and then
|
|
121
|
+
`ghosty factory runs resume <n> --yes`; `runs stop <n>` stops a running turn and `runs cancel <n>`
|
|
122
|
+
closes the run.
|
|
123
|
+
|
|
120
124
|
Exit code 1 from `--wait`/`watch` only means the timeout ran out; run `watch` again. The user can
|
|
121
125
|
always follow along in the room; `ghosty factory runs card <n>` brings the live card down.
|
|
122
126
|
|