@myagentroam/node 0.10.51 → 0.10.53

package/dist/connector.js

@@ -890,8 +890,7 @@ export class NodeConnector {
                     sessionId: input.sessionId,
                     workspaceId: input.workspaceId,
                     ...(task === undefined ? {} : { taskId: task.id, revision: task.revision }),
-                    actorUserId: run.initiatedByUserId,
-                    readonly: run.source === 'SCHEDULED'
+                    actorUserId: run.initiatedByUserId
                 });
             },
             notificationMcp: async (input) => {

package/dist/runner/mar-agent/marctl-skill.js

@@ -29,7 +29,7 @@ const marctlInstructions = [
     'show --json fields: session.activity, session.model, session.effort, session.customTitle or session.runnerTitle, runs[] (id/status), queue.items[], and goal.status (goal may be null). Run status and Goal status are separate.',
     'Rename any authorized Workspace Session with sessions rename <session-id> --title <name> --json; parent relationships do not restrict renaming.',
     'show/config/history/graph/rename and schedule get/create/update may omit the Session ID to use the current Session. Without a current Session, specify an ID. send/goal/stop/wait always require explicit target IDs.',
-    'Use sessions schedule list/get/create/update for the same tasks as the built-in schedule MCP, which is hidden while this skill is available. list is Workspace-scoped. create requires --cron and text (-m/--message-file, up to 20,000 characters). update requires --expected-revision from get and at least cron or text. get returns task (null if absent), with id, revision, objective, cron, timezone and enabled; applied updates also return task. Reuse that task instead of probing its shape or refetching unchanged state. Schedule text is trimmed at both ends; compare after the same trimming; a conclusive update response needs no extra get. Other-owner edits return a PENDING proposal, not an applied change; scheduled execution is read-only. Follow existing approval rules and do not retry conflicts or uncertain writes blindly.',
+    'Use sessions schedule list/get/create/update for the same tasks as the built-in schedule MCP, which is hidden while this skill is available. list is Workspace-scoped. create requires --cron and text (-m/--message-file, up to 20,000 characters). update requires --expected-revision from get and at least cron or text. get returns task (null if absent), with id, revision, objective, cron, timezone and enabled; applied updates also return task. Reuse that task instead of probing its shape or refetching unchanged state. Schedule text is trimmed at both ends; compare after the same trimming; a conclusive update response needs no extra get. Other-owner edits return a PENDING proposal, not an applied change. Scheduled execution uses normal user permissions. Follow existing approval rules and do not retry conflicts or uncertain writes blindly.',
     'Read results with sessions history <session-id> --limit 10 --json (default: latest 10 SEGMENTs, not messages; --limit 1..100). In segments[].items[], select kind === "assistant_message" and read payload.text; keep segment runId and user_message.payload.clientMessageId for queued-input correlation. Reuse the returned page; follow --cursor <nextCursor> only for missing evidence.',
     'Use sessions send <session-id> --steer -m "Additional context: focus on the resume path." --json for decision-changing updates rather than routine reports: it may switch the current execution. Node decides delivery from actual state; an idle Session receives ordinary input. Choose exactly one of --steer or --queue, even when idle; missing, conflicting, repeated, or obsolete options are rejected locally before input is read or a request is sent. Use --queue to place input in a subsequent turn; with an active Goal, ordinary queued input waits until the Goal exits. start/send return clientMessageId and the accepted/queued result. A queued result may refer to the currently active Run: associate queueItemId/clientMessageId with history before deciding that input finished. There are no queue-item edit/delete/reorder commands; show includes queue state.',
     'Wait with sessions wait <session-id> --run <run-id> --timeout 5m --json through the existing Watch. Prefer --timeout 5m when blocked on task completion; use 30s for a short deadline. Continue useful independent work before waiting. If exec returns a running process or cell, reuse its process/cell handle rather than starting another wait or polling show/list. Timeout or cancelled waiting does not stop the task. Use sessions stop <session-id> --run <run-id> --json only to stop that active Run; ownership rules still apply.',

package/dist/service/schedule-mcp-bridge.js

@@ -39,8 +39,7 @@ export class ScheduleMcpBridge {
             args,
             environment: {
                 MAR_SCHEDULE_MCP_ENDPOINT: this.#endpoint,
-                MAR_SCHEDULE_MCP_TOKEN: token,
-                MAR_SCHEDULE_MCP_READ_ONLY: capability.readonly ? '1' : '0'
+                MAR_SCHEDULE_MCP_TOKEN: token
             },
             allowedToolCallers: {
                 [NODE_MCP.schedule.tools.get]: ['direct', 'programmatic'],
@@ -106,8 +105,6 @@ export class ScheduleMcpBridge {
                 return;
             }
             if (request.tool === NODE_MCP.schedule.tools.create) {
-                if (capability.readonly)
-                    throw new Error('SCHEDULE_READ_ONLY');
                 if (task !== undefined)
                     throw new Error('SCHEDULE_ALREADY_EXISTS');
                 const args = record(request.arguments);
@@ -134,8 +131,6 @@ export class ScheduleMcpBridge {
             }
             if (request.tool !== NODE_MCP.schedule.tools.update)
                 throw new Error('SCHEDULE_TOOL_INVALID');
-            if (capability.readonly)
-                throw new Error('SCHEDULE_READ_ONLY');
             if (task === undefined)
                 throw new Error('SCHEDULE_NOT_FOUND');
             const args = record(request.arguments);

package/dist/service/schedule-mcp-stdio.js

@@ -16,33 +16,31 @@ server.registerTool(NODE_MCP.schedule.tools.get, {
     description: 'Read the MAR scheduled task bound to this MAR-managed Workspace conversation, or null if none exists. ' +
         scopeNote
 }, async () => result(await request(NODE_MCP.schedule.tools.get, {})));
-if (process.env['MAR_SCHEDULE_MCP_READ_ONLY'] !== '1') {
-    server.registerTool(NODE_MCP.schedule.tools.create, {
-        description: 'Create the MAR scheduled task for this MAR-managed Workspace conversation. MAR runs it in this conversation for each admitted trigger using the connected Node time zone. ' +
-            scopeNote,
-        inputSchema: {
-            objective: z.string().min(1).max(20_000).describe(objectiveDescription),
-            cron: z
-                .string()
-                .min(9)
-                .max(64)
-                .describe('Five-field cron expression interpreted in the connected MAR Node time zone. It defines the schedule separately from the per-run task body.')
-        }
-    }, async (args) => result(await request(NODE_MCP.schedule.tools.create, args)));
-    server.registerTool(NODE_MCP.schedule.tools.update, {
-        description: 'Update the MAR scheduled task for this MAR-managed Workspace conversation. MAR runs the saved objective in this conversation for each admitted trigger using the connected Node time zone. ' +
-            scopeNote,
-        inputSchema: {
-            objective: z.string().min(1).max(20_000).describe(objectiveDescription).optional(),
-            cron: z
-                .string()
-                .min(9)
-                .max(64)
-                .describe('Replacement five-field cron expression in the connected MAR Node time zone.')
-                .optional()
-        }
-    }, async (args) => result(await request(NODE_MCP.schedule.tools.update, args)));
-}
+server.registerTool(NODE_MCP.schedule.tools.create, {
+    description: 'Create the MAR scheduled task for this MAR-managed Workspace conversation. MAR runs it in this conversation for each admitted trigger using the connected Node time zone. ' +
+        scopeNote,
+    inputSchema: {
+        objective: z.string().min(1).max(20_000).describe(objectiveDescription),
+        cron: z
+            .string()
+            .min(9)
+            .max(64)
+            .describe('Five-field cron expression interpreted in the connected MAR Node time zone. It defines the schedule separately from the per-run task body.')
+    }
+}, async (args) => result(await request(NODE_MCP.schedule.tools.create, args)));
+server.registerTool(NODE_MCP.schedule.tools.update, {
+    description: 'Update the MAR scheduled task for this MAR-managed Workspace conversation. MAR runs the saved objective in this conversation for each admitted trigger using the connected Node time zone. ' +
+        scopeNote,
+    inputSchema: {
+        objective: z.string().min(1).max(20_000).describe(objectiveDescription).optional(),
+        cron: z
+            .string()
+            .min(9)
+            .max(64)
+            .describe('Replacement five-field cron expression in the connected MAR Node time zone.')
+            .optional()
+    }
+}, async (args) => result(await request(NODE_MCP.schedule.tools.update, args)));
 await server.connect(new StdioServerTransport());
 function request(tool, args) {
     return new Promise((resolve, reject) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@myagentroam/node",
-  "version": "0.10.51",
+  "version": "0.10.53",
   "description": "MyAgentRoam Node runtime CLI.",
   "license": "Apache-2.0 AND GPL-2.0-or-later",
   "type": "module",
@@ -37,10 +37,10 @@
     "playwright": "1.62.1",
     "ws": "^8.21.3",
     "zod": "4.4.3",
-    "@myagentroam/agent": "0.10.51",
+    "@myagentroam/agent": "0.10.53",
     "@myagentroam/code-navigation": "0.10.1",
-    "@myagentroam/protocol": "0.10.51",
-    "@myagentroam/marctl": "0.10.10"
+    "@myagentroam/marctl": "0.10.11",
+    "@myagentroam/protocol": "0.10.53"
   },
   "devDependencies": {
     "@types/ws": "^8.18.1"