@thehammer/danx-dashboard-mcp 0.1.298 → 0.1.300

package/dist/handlers.js

@@ -131,6 +131,7 @@ export async function danxbotApi(client, args) {
         query: args.query,
         body: args.body,
         board: args.board,
+        background: args.background,
     });
 }
 // ---------------- danxbot_api_list (DX-3465 A5, PLN-11 R-25) ----------------

package/dist/http-client.js

@@ -50,6 +50,9 @@ export class DashboardHttpClient {
         if (this.config.session) {
             headers["x-danx-session-id"] = this.config.session.id;
         }
+        if (args.background === true) {
+            headers["x-danx-plugin-background"] = "1";
+        }
         let bodyString;
         if (args.body !== undefined) {
             headers["Content-Type"] = "application/json";

package/dist/index.js

@@ -568,6 +568,8 @@ strictTool("danxbot_api",
     // instead of reaching the dashboard malformed.
     body: bodyValueSchema.optional(),
     ...boardField,
+    // DX-5033 - sends x-danx-plugin-background (see DanxbotApiArgs.background); an agent setting it would hide its own calls from the pause and idle logic.
+    background: z.boolean().optional().describe("Set only by plugin hooks; an agent never sets it."),
 }, 
 // DX-3997 — the result rides back verbatim, plus the dashboard's own `reminders[]` entries
 // for this plan-connected session (the server decides; `listener-reminder.ts` only relays).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-dashboard-mcp",
-  "version": "0.1.298",
+  "version": "0.1.300",
   "description": "Stdio MCP server fronting danxbot's dashboard API for agents (operator sessions and dispatched workers alike): the generic danxbot_api/danxbot_api_list/danxbot_api_spec tools reach any route the caller's credential may call, plus dedicated agent-specific tools (plan_connect, request_permission, attach_file, and danxbot_slack_reply) (DX-3465, PLN-11 R-25).",
   "license": "MIT",
   "type": "module",