agent-blocked 0.1.0 → 0.1.1
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 +19 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
CLI installer and reporter for Agent Blocked.
|
|
4
4
|
|
|
5
|
+
Published package: https://www.npmjs.com/package/agent-blocked
|
|
6
|
+
|
|
5
7
|
Install adapters in any agent project:
|
|
6
8
|
|
|
7
9
|
```bash
|
|
@@ -14,8 +16,24 @@ Report a blocker manually:
|
|
|
14
16
|
npx agent-blocked report --event=needs_direction --severity=medium --reason="Need human direction"
|
|
15
17
|
```
|
|
16
18
|
|
|
17
|
-
|
|
19
|
+
The installer adds a small `.agent-blocked/` directory plus tool-specific config or instruction files for the selected agent tools. Those files tell the agent when to escalate and provide a local reporter command that sends blocker events to your Agent Blocked alert profile.
|
|
20
|
+
|
|
21
|
+
Set these environment variables in the shell where the agent runs:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
export AGENT_BLOCKED_WEBHOOK_URL="https://agentblocked.com/api/agent-blocked"
|
|
25
|
+
export AGENT_BLOCKED_AGENT_TOKEN="your-scoped-token"
|
|
26
|
+
export AGENT_NAME="prod-agent"
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
Agents can report through the installed local reporter:
|
|
18
30
|
|
|
19
31
|
```bash
|
|
20
32
|
node .agent-blocked/report.mjs --event=needs_credentials --severity=critical --reason="Missing deploy credentials"
|
|
21
33
|
```
|
|
34
|
+
|
|
35
|
+
Codex can also be run through the wrapper so hard stops are reported automatically:
|
|
36
|
+
|
|
37
|
+
```bash
|
|
38
|
+
npx agent-blocked codex -- codex "implement the requested change"
|
|
39
|
+
```
|