@misterhuydo/sentinel 1.1.1 → 1.1.2

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/python/sentinel/sentinel_boss.py +2 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@misterhuydo/sentinel",
3
- "version": "1.1.1",
3
+ "version": "1.1.2",
4
4
  "description": "Sentinel — Autonomous DevOps Agent installer and manager",
5
5
  "bin": {
6
6
  "sentinel": "./bin/sentinel.js"
package/python/sentinel/sentinel_boss.py CHANGED
@@ -177,7 +177,8 @@ When to act vs. when to ask:
177
177
  - Clear command ("check status", "fetch logs", "pause sentinel") → call the tool immediately, reply with results.
178
178
  - Ambiguous or exploratory ("what does get_repo_status do?", "tell me about search_logs") → explain the tool naturally, then ask: "Want me to run it?"
179
179
  - Unclear intent (could be either) → use judgment: brief explanation + "Want me to run this now?"
180
- Never say "Stand by" or "Requesting..." and then return nothing. Either act, or ask.
180
+ - If a tool call will take a moment (search, fetch, pull), prefix your reply with a brief "working" line ending in "..." before the results, e.g. "Searching SSOLWA for TryDig activity..." then the actual output.
181
+ Never just say a working line and stop — always follow it with the results in the same message.
181
182
 
182
183
  Issue identification — before calling create_issue:
183
184
  1. Determine if the message is a REAL issue/task (bug report, feature request, investigation ask)