@misterhuydo/sentinel 1.4.52 → 1.4.53

package/.cairn/.hint-lock

@@ -1 +1 @@
-2026-03-25T11:19:33.099Z
+2026-03-25T11:51:07.142Z

package/.cairn/session.json

@@ -1,6 +1,6 @@
 {
-  "message": "Auto-checkpoint at 2026-03-25T11:44:18.256Z",
-  "checkpoint_at": "2026-03-25T11:44:18.257Z",
+  "message": "Auto-checkpoint at 2026-03-25T11:57:04.683Z",
+  "checkpoint_at": "2026-03-25T11:57:04.684Z",
   "active_files": [],
   "notes": [],
   "mtime_snapshot": {}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@misterhuydo/sentinel",
-  "version": "1.4.52",
+  "version": "1.4.53",
   "description": "Sentinel — Autonomous DevOps Agent installer and manager",
   "bin": {
     "sentinel": "./bin/sentinel.js"

package/python/sentinel/sentinel_boss.py

@@ -240,9 +240,16 @@ Don't pad responses. Don't say "Great question!" or "Certainly!".
 If you don't know something, use a tool to find out before saying you don't know.
 
 When to act vs. when to ask:
-- Clear command ("check status", "fetch logs", "pause sentinel") → call the tool immediately, reply with results.
-- 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?"
-- Unclear intent (could be either) → use judgment: brief explanation + "Want me to run this now?"
+- Any read/investigate tool (ask_codebase, filter_logs, search_logs, get_status, tail_log, ask_logs,
+  get_fix_details, list_pending_prs, check_auth_status, list_projects, my_stats, get_repo_status,
+  list_recent_commits) → call immediately without asking permission. Never say "Want me to check?" —
+  just check and report results. If you think it's worth doing, do it.
+- Write/action tools (create_issue, trigger_poll, pull_repo, pause_sentinel, install_tool, merge_pr,
+  retry_issue, post_file) → act immediately for clear commands; confirm only when intent is ambiguous
+  (e.g. unclear which project or repo to target).
+- Explaining a tool ("what does X do?") → explain naturally, then offer to run it if relevant.
+- NEVER gate investigation on user approval. If diagnosing a problem, run all relevant read tools
+  first, then present findings. Asking "Want me to look?" wastes a round trip.
 - Prefer filter_logs over search_logs when synced logs are available — it's instant and never causes session timeout.
   Use search_logs only when the user explicitly wants live/real-time data or synced logs are not yet available.
 - 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.