ghosty-acp 0.0.46 → 0.0.48
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.54"
|
|
9
9
|
---
|
|
10
10
|
|
|
11
11
|
# Configure a Ghosty Studio agent
|
|
@@ -93,7 +93,7 @@ legacy and always `true`.)
|
|
|
93
93
|
| "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
94
|
| "give it the CRM / sales tools" | `ghosty agents set <id> --toolsets +crm` (a plain list replaces; `-x` removes) |
|
|
95
95
|
| "share it with / give access to <email>" | `ghosty agents share <id> <email> [--role editor\|admin]` (keeps ownership); `ghosty agents shares <id>` lists; `unshare` needs `--yes` |
|
|
96
|
-
| "put it in my Teams workspace", "activate it in Teams as @x", "change its handle", "take it out of Teams" | `ghosty agents teams ls <id>` (workspaces you administer: where it answers, with which @handle), `ghosty agents teams on <id> <workspace> [--handle x]` (on an active one it changes the handle; `@ghosty` is reserved), `ghosty agents teams off <id> <workspace>` (pauses it; keeps the @handle), `ghosty agents teams rm <id> <workspace> --yes` (removes it, frees the handle; the agent stays). In the UI: agent page → Channels → Ghosty Teams |
|
|
96
|
+
| "put it in my Teams workspace", "activate it in Teams as @x", "change its handle", "take it out of Teams", "make it @build / @plan / @check", "change who does the factory roles" | `ghosty agents teams ls <id>` (workspaces you administer: where it answers, with which @handle), `ghosty agents teams on <id> <workspace> [--handle x]` (on an active one it changes the handle; `@ghosty` is reserved), `ghosty agents teams on <id> <workspace> --factory plan,build,check` (makes it those Software Factory roles; `ls` shows the roles it holds), `ghosty agents teams off <id> <workspace>` (pauses it; keeps the @handle), `ghosty agents teams rm <id> <workspace> --yes` (removes it, frees the handle; the agent stays). In the UI: agent page → Channels → Ghosty Teams |
|
|
97
97
|
| "turn off / on this skill" | `ghosty skills disable\|enable <id> <slug>` (its own or one of Ghosty's; `skills ls` shows `on`) |
|
|
98
98
|
| "delete this agent" | confirm with the user first, then `ghosty agents rm <id>` (owner only; `409` names the workspace where it is active) |
|
|
99
99
|
| "switch it to another engine" | `ghosty agents set <id> --engine <engine> [--model <model-id>] --dry-run` first (says what is forgotten and which machine is replaced; `ok:false` if it is busy), then the same without `--dry-run`. The model belongs to the NEW engine; each conversation keeps its history (gs passes it on its first turn) |
|
|
@@ -163,6 +163,8 @@ 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) |
|
|
168
170
|
| "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) |
|