agent-blocked 0.1.3 → 0.1.5

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
@@ -16,9 +16,9 @@ Report a blocker manually:
16
16
  npx agent-blocked@latest report --event=needs_direction --severity=medium --reason="Need human direction"
17
17
  ```
18
18
 
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.
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 during goal mode, autonomous mode, background execution, hook-driven automation, CI-style runs, or another CLI-specific automated mode. They also provide a local reporter command that sends blocker events to your Agent Blocked alert profile.
20
20
 
21
- Agents should notify when continuing would waste time, create risk, or require a decision only the human can make:
21
+ Agents should not notify during normal interactive paired work when the human is already present and responding in the current conversation. In automated modes, agents should notify when continuing would waste time, create risk, or require a decision only the human can make:
22
22
 
23
23
  - `needs_credentials` for missing API keys, OAuth, permissions, roles, or secrets.
24
24
  - `needs_direction` for ambiguous goals, tradeoffs, architecture, product behavior, or priorities.
@@ -27,12 +27,10 @@ Agents should notify when continuing would waste time, create risk, or require a
27
27
  - `low_confidence` when the agent can continue but the chance of being wrong is high.
28
28
  - `hard_blocked` when no productive path remains without human input.
29
29
 
30
- Set these environment variables in the shell where the agent runs:
30
+ Set the scoped token in the shell or secret store where the agent runs:
31
31
 
32
32
  ```bash
33
- export AGENT_BLOCKED_WEBHOOK_URL="https://agentblocked.com/api/agent-blocked"
34
33
  export AGENT_BLOCKED_AGENT_TOKEN="your-scoped-token"
35
- export AGENT_NAME="prod-agent"
36
34
  ```
37
35
 
38
36
  Agents can report through the installed local reporter:
@@ -156,7 +156,11 @@ try {
156
156
 
157
157
  const instructions = `# Agent Blocked instructions for coding agents
158
158
 
159
- When you are blocked by missing credentials, unclear direction, approval requirements, repeated tool failures, low confidence, or external context, stop burning tokens and report the blockage.
159
+ Use Agent Blocked only when this agent is running without an actively engaged human in the loop, such as goal mode, autonomous mode, background execution, hook-driven automation, CI-style runs, or another CLI-specific automated mode.
160
+
161
+ Do not report during normal interactive paired work when the human is already present and responding in the current conversation. In that case, ask the human directly in chat instead of sending an Agent Blocked alert.
162
+
163
+ When operating in an automated mode and blocked by missing credentials, unclear direction, approval requirements, repeated tool failures, low confidence, or external context, stop burning tokens and report the blockage.
160
164
 
161
165
  Notify the human when continuing would waste time, create risk, or require a decision only the human can make. Do not notify for routine recoverable errors that you can fix yourself in one or two attempts.
162
166
 
@@ -169,9 +173,7 @@ node .agent-blocked/report.mjs --event=needs_direction --severity=medium --reaso
169
173
  Environment expected by the report command:
170
174
 
171
175
  \`\`\`bash
172
- export AGENT_BLOCKED_WEBHOOK_URL="https://agentblocked.com/api/agent-blocked"
173
176
  export AGENT_BLOCKED_AGENT_TOKEN="your-scoped-token"
174
- export AGENT_NAME="your-agent-name"
175
177
  \`\`\`
176
178
 
177
179
  Event types:
@@ -325,7 +327,7 @@ function install() {
325
327
  installers[name]();
326
328
  }
327
329
 
328
- console.log("\nNext: set AGENT_BLOCKED_WEBHOOK_URL, AGENT_BLOCKED_AGENT_TOKEN, and AGENT_NAME in the shell where your agent runs.");
330
+ console.log("\nNext: set AGENT_BLOCKED_AGENT_TOKEN in the shell or secret store where your agent runs.");
329
331
  console.log("Manual report command: node .agent-blocked/report.mjs --event=needs_direction --severity=medium --reason=\"Need human direction\"");
330
332
  }
331
333
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agent-blocked",
3
- "version": "0.1.3",
3
+ "version": "0.1.5",
4
4
  "description": "CLI installer and reporter for Agent Blocked AI agent escalation alerts.",
5
5
  "type": "module",
6
6
  "bin": {