@integrity-labs/agt-cli 0.27.16 → 0.27.18
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/bin/agt.js +3 -3
- package/dist/{chunk-6D55CCVZ.js → chunk-CDMAMIVX.js} +30 -4
- package/dist/chunk-CDMAMIVX.js.map +1 -0
- package/dist/lib/manager-worker.js +9 -5
- package/dist/lib/manager-worker.js.map +1 -1
- package/dist/mcp/direct-chat-channel.js +8 -0
- package/package.json +1 -1
- package/dist/chunk-6D55CCVZ.js.map +0 -1
|
@@ -14114,6 +14114,14 @@ var mcp = new Server(
|
|
|
14114
14114
|
tools: {}
|
|
14115
14115
|
},
|
|
14116
14116
|
instructions: [
|
|
14117
|
+
// ENG-5845: highest-priority guard first. Without this framing,
|
|
14118
|
+
// Opus 4.8 reads the softer "Reply using…" line as a suggestion and
|
|
14119
|
+
// emits plain text — the reply lives in the local Claude session
|
|
14120
|
+
// but never reaches the operator's session_id through the channel
|
|
14121
|
+
// API. Mirrors the slack-channel CRITICAL line shipped in
|
|
14122
|
+
// ENG-5830. Total instructions string is ~850 / 2048 chars so we
|
|
14123
|
+
// have room to be explicit.
|
|
14124
|
+
"CRITICAL: every response to a direct-chat <channel> tag MUST go through direct_chat.reply (passing the session_id verbatim). Text in your session WITHOUT a direct_chat.reply call never reaches the operator \u2014 the reply dies inside the agent process.",
|
|
14117
14125
|
'Messages from the webapp Direct Chat arrive as <channel source="direct-chat" session_id="..." user="...">.',
|
|
14118
14126
|
"Reply using the direct_chat.reply tool, passing the session_id from the tag.",
|
|
14119
14127
|
"Always reply to every direct chat message \u2014 the user is waiting in the webapp.",
|