@integrity-labs/agt-cli 0.28.396 → 0.28.398

package/dist/mcp/direct-chat-channel.js

@@ -29748,10 +29748,15 @@ function readDirectChatSessionState(agentDir, nowMs) {
 
 // src/direct-chat-channel-meta.ts
 function buildDirectChatChannelMeta(input) {
+  const identity = {};
+  if (input.userName) identity.user_name = input.userName;
+  if (input.userEmail) identity.user_email = input.userEmail;
+  if (input.userRole) identity.user_role = input.userRole;
   return {
     session_id: input.sessionId,
     user: "webapp",
     source: "direct-chat",
+    ...identity,
     // String flag the agent's channel instructions (and the renderer) read:
     // 'false' = notice (do not reply), 'true' = normal message (reply expected).
     requires_reply: input.isNotice ? "false" : "true",
@@ -35526,6 +35531,7 @@ var mcp = new Server(
       // have room to be explicit.
       "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.",
       'Messages from the webapp Direct Chat arrive as <channel source="direct-chat" session_id="..." user="...">.',
+      "When the tag carries user_name (and sometimes user_email / user_role), that is the verified human you are talking with; address them by name and tailor your reply to who they are. If those attributes are absent, the sender is unknown, so just reply helpfully without personalization.",
       "Reply using the direct_chat.reply tool, passing the session_id from the tag.",
       "Always reply to every direct chat message that expects a reply (its meta has requires_reply=true, or no requires_reply field) \u2014 the user is waiting in the webapp.",
       "NEVER call direct_chat.reply for a NOTICE \u2014 a notification whose meta has requires_reply=false (ENG-6381). It is an informational FYI (e.g. an integration-status update), not a question, and it has ALREADY been acknowledged for you. Replying would wrongly post into the operator\u2019s chat history and burn a turn. Just take it into account and carry on.",
@@ -35975,7 +35981,14 @@ async function pollForMessages(sinceMs) {
         params: {
           content: injectContent,
           meta: {
-            ...buildDirectChatChannelMeta({ sessionId: msg.session_id, isNotice }),
+            ...buildDirectChatChannelMeta({
+              sessionId: msg.session_id,
+              isNotice,
+              // ENG-8047: pure passthrough of the server-resolved human identity.
+              userName: msg.sender_name,
+              userEmail: msg.sender_email,
+              userRole: msg.sender_role
+            }),
             ...attachmentMeta
           }
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.396",
+  "version": "0.28.398",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {