acbridge 1.1.2 → 1.2.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/dist/acbridge.mjs +125 -113
- package/hub/dist/hub.cjs +53 -52
- package/package.json +1 -1
- package/plugin/README.md +6 -0
- package/plugin/plugins/alexa/dist/channel.mjs +33 -31
- package/plugin/plugins/alexa/scripts/codex-signal.mjs +128 -49
- package/plugin/plugins/alexa/scripts/signal.mjs +90 -20
- package/plugin/plugins/alexa/scripts/statusline-guard.mjs +6 -2
package/package.json
CHANGED
package/plugin/README.md
CHANGED
|
@@ -7,6 +7,12 @@ Profiles (see [`../docs/CLAUDE-SIGNALS.md`](../docs/CLAUDE-SIGNALS.md)). Install
|
|
|
7
7
|
then loaded on every session with `claude --channels plugin:alexa@bridge` — **no `--dangerously-*`
|
|
8
8
|
flag**. This directory is the *packaging* of the `channel/` workspace for that installed-plugin path.
|
|
9
9
|
|
|
10
|
+
`signal.mjs` also CARRIES the agent device-brief (2026-08): at SessionStart it asks the hub
|
|
11
|
+
(`GET /local/agent/brief`) whether the cwd's bound profile ticks "Make agent aware of devices in
|
|
12
|
+
chat" and, if so, prints the brief as `hookSpecificOutput.additionalContext` — its only stdout,
|
|
13
|
+
on that one event. For Codex the same brief rides the channel's MCP `instructions` instead
|
|
14
|
+
(`acbridge setup` registers `[mcp_servers.acbridge]` in `~/.codex/config.toml`, env `ACB_AGENT=codex`).
|
|
15
|
+
|
|
10
16
|
This same `plugins/alexa/scripts/` directory also carries `codex-signal.mjs` — the Codex CLI sibling
|
|
11
17
|
of `signal.mjs` (below). It is **not** registered in this plugin's own `hooks/hooks.json`; Codex CLI
|
|
12
18
|
has its own hooks engine entirely, and `acbridge setup` installs `codex-signal.mjs` directly into
|