astracode-agent 0.4.1 → 0.5.0

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/README.md CHANGED
@@ -98,6 +98,7 @@ Commands:
98
98
  | `/tasks` | background agents, commands and monitors: `/tasks <id>` shows one's output or report, `/tasks stop <id>`, `/tasks stop-all` |
99
99
  | `/agents` | the agents it can start: built-in, the project's, yours and `--agents`, with each file and what it shadows |
100
100
  | `/mcp` | MCP servers and their tools |
101
+ | `/plugin` | in the line session: list, install and manage plugins, as `astracode-agent plugin` does (below) |
101
102
  | `/export`, `/status`, `/help` | save the conversation, account and model details, all keys |
102
103
 
103
104
  ### Subagents and background tasks
@@ -182,6 +183,7 @@ astracode-agent -p "<prompt>" [options]
182
183
  | `--agents <json\|file>` | Agent definitions for this run. See [Subagents](#subagents-and-background-tasks). |
183
184
  | `--agent <name>` | Run as that agent: its prompt, tools and model. |
184
185
  | `--allow-agent-mcp` | Start the MCP servers the project's agent files declare. See [Subagents](#subagents-and-background-tasks). |
186
+ | `--trust` | Accepted and changes nothing: a `-p` run trusts the folder it runs in, as Claude Code's `-p` does. A conversation, `acp` and `review` take it too, and there it matters: without it (or `ASTRACODE_TRUST=1`, or a folder you trusted once, or `/trust` in a conversation) the agent changes no file and runs no command, and the project's rules, hooks, skills, commands and agents are not loaded. `review` stays untrusted unless told, because a fork's pull request reaches it. |
185
187
  | `--report-to <url>` | Post the run's progress to `<url>/events` as it goes. See [Reporting progress](#reporting-progress). |
186
188
  | `-v, --verbose` | Prints the agent's log on stderr. |
187
189
 
@@ -284,6 +286,47 @@ requests, and no secret: each run signs in with the identity token GitHub gives
284
286
  the job. A repository secret `ASTRACODE_TOKEN` (an API key with the "Run agents"
285
287
  scope), if set, is used instead. See [Remote agents](https://astracode.io/docs/agent/remote-agents/).
286
288
 
289
+ ## Plugins
290
+
291
+ Plugins written for Claude Code or Cursor, or in the open Agent Plugins
292
+ format, install from marketplaces you add: a GitHub repository, any git url,
293
+ or a folder on your machine. A plugin brings skills, commands, agents, rules,
294
+ hooks and MCP servers, and the CLI and the editor share what is installed.
295
+
296
+ ```bash
297
+ astracode-agent plugin marketplace add anthropics/claude-code
298
+ astracode-agent plugin list --available
299
+ astracode-agent plugin install hookify@claude-code-plugins
300
+ astracode-agent plugin list
301
+ ```
302
+
303
+ | command | |
304
+ |---|---|
305
+ | `plugin marketplace add <owner/repo[#ref] \| git url \| folder>` | add a marketplace; its name is the one its `marketplace.json` gives |
306
+ | `plugin marketplace remove\|update <name>`, `plugin marketplace list` | |
307
+ | `plugin list [--available] [--json]` | what is installed and what each one contributes, or what your marketplaces offer |
308
+ | `plugin install <name[@marketplace]> [--scope user\|project] [--yes]` | install; `project` applies only in this folder, once it is trusted |
309
+ | `plugin update <name@marketplace> [--yes]` | fetch its newest commit |
310
+ | `plugin uninstall\|enable\|disable <name@marketplace>` | |
311
+ | `plugin approve <name@marketplace> [--yes]` | allow the hooks and servers of a plugin installed for you, such as one your organisation requires |
312
+ | `plugin config <name@marketplace> [<key> [<value>]]` | the options a plugin asks for |
313
+
314
+ **What it runs is printed first.** Before a plugin is installed, every hook
315
+ command and MCP server it would run is printed, as it would run. It is
316
+ installed only with `--yes` or a `y` typed at the question; in a script or a
317
+ pipe with no `--yes`, the answer is no. An update that changes what it runs
318
+ asks again, and a no keeps the version you have.
319
+
320
+ A plugin's skills and commands are named `<plugin>:<name>` (`/hookify:list`),
321
+ and the bare name works while no other plugin has it. A sensitive option is
322
+ kept in the Keychain (or `secrets.json`, owner-only, in `~/.config/astracode`
323
+ elsewhere) and is never taken from the command line: run `plugin config`
324
+ without a value to type it, or pipe it in. Plugins are kept in
325
+ `~/.astracode/plugins`, each at the commit it was installed from.
326
+
327
+ A plugin's MCP servers start in the full-screen conversation, as your own
328
+ do. See [Plugins](https://astracode.io/docs/extending/plugins/).
329
+
287
330
  ## In Zed or a JetBrains IDE
288
331
 
289
332
  `astracode-agent acp` speaks the [Agent Client Protocol](https://agentclientprotocol.com),
@@ -359,5 +402,7 @@ runners already have it.
359
402
  | variable | |
360
403
  |---|---|
361
404
  | `ASTRACODE_API_KEY` | An `ac_live_` key. Takes precedence over a saved session. |
405
+ | `ASTRACODE_TRUST` | `1` trusts the folder for a conversation, `acp` or `review`, as `--trust` does. A `-p` run trusts it anyway. |
362
406
  | `ASTRACODE_GATEWAY_URL` | The gateway to use. The default is `https://api.astracode.io`. |
363
407
  | `ASTRACODE_CONFIG_DIR` | Keep the session in this folder instead of the Keychain or `~/.config/astracode`. |
408
+ | `ASTRACODE_PLUGINS_DIR` | Keep plugins and their state here instead of `~/.astracode/plugins`. |