@realtimex/sdk 1.7.11 → 1.7.13

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@realtimex/sdk",
-    "version": "1.7.11",
+    "version": "1.7.13",
     "description": "SDK for building Local Apps that integrate with RealtimeX",
     "main": "dist/index.js",
     "module": "dist/index.mjs",

package/skills/realtimex-moderator-sdk/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: realtimex-moderator-sdk
 description: Control and interact with the RealTimeX application through its Node.js SDK. This skill should be used when users want to manage workspaces, threads, agents, activities, LLM chat, vector store, MCP tools, ACP agent sessions, TTS/STT, or any other RealTimeX platform feature via the API. All method signatures are verified against the SDK source code.
-generated: 2026-05-07
-sdk_version: 1.7.11
+generated: 2026-05-08
+sdk_version: 1.7.13
 ---
 
 # RealTimeX Moderator (SDK Source-Verified)
 
-Interact with the RealTimeX platform (`http://localhost:3001`) using `@realtimex/sdk` **v1.7.11**. Authentication is automatic when running inside RealtimeX.
+Interact with the RealTimeX platform (`http://localhost:3001`) using `@realtimex/sdk` **v1.7.13**. Authentication is automatic when running inside RealtimeX.
 
 `<SKILL_DIR>` below refers to the directory containing this SKILL.md.
 
@@ -140,6 +140,10 @@ await sdk.desktopRuntimeSessions.launchTerminalShell({
 });
 ```
 
+Rule:
+- If you launch a shell with `initialCommand` and the user did not explicitly ask to prefill only, use `initialCommandMode: "direct"`.
+- Use `prefill` only when the user specifically wants the command staged without execution.
+
 Manage existing terminal sessions:
 
 ```js
@@ -349,6 +353,52 @@ It covers:
 - **Agent Skills** — types (`repo`/`zip`), scopes, status values
 - **Data Models** — all database models with fields and defaults
 
+### Heartbeat Task Blocks
+
+When working with `HEARTBEAT.md`, check whether it uses a top-level `tasks:` block.
+
+Example:
+
+```yaml
+tasks:
+  - name: audit-fetch
+    interval: 4h
+    prompt: Fetch origin/realtimex-dev and diff against tmp/frontend-audit-cursor.txt.
+
+  - name: audit-ui-design
+    interval: 4h
+    prompt: Review changed frontend files for UI design violations. If none, reply HEARTBEAT_OK.
+```
+
+Rules:
+- A top-level `tasks:` list means the heartbeat is split into separate scheduled tasks, not one monolithic prompt.
+- Each `- name:` item is its own task definition.
+- `name` is the stable task id. Keep it concise and stable when editing.
+- `interval` is the cadence for that specific task.
+- `prompt` is the full instruction body for that task.
+- `HEARTBEAT_OK` means the task ran successfully but had nothing actionable to do.
+- Preserve task order unless the user explicitly wants a reordering.
+- If one task refers to another task's output, that dependency is described in the prompt text. Do not invent hidden YAML dependency fields.
+
+When editing heartbeat files:
+- If the file already uses `tasks:`, add or edit individual task items instead of collapsing them into one large prompt.
+- If the file is a single long heartbeat prompt and the user wants separate scheduled jobs, rewrite it into a `tasks:` list with one item per independent workflow.
+- When splitting a single heartbeat into tasks, preserve the original intent, move each discrete workflow into its own `prompt`, and keep shared context text only where needed.
+- Keep YAML formatting simple: top-level `tasks:`, then `- name`, `interval`, `prompt`.
+
+When a user asks how to convert a heartbeat into task-block form, produce or edit it into this shape:
+
+```yaml
+tasks:
+  - name: task-one
+    interval: 4h
+    prompt: First workflow instructions.
+
+  - name: task-two
+    interval: 12h
+    prompt: Second workflow instructions.
+```
+
 ---
 
 ## References

package/skills/realtimex-moderator-sdk/references/api-reference.md

@@ -1,6 +1,6 @@
 # RealTimeX SDK — API Reference
 
-> Auto-generated from `@realtimex/sdk` source · v**1.7.11** · 2026-05-07
+> Auto-generated from `@realtimex/sdk` source · v**1.7.13** · 2026-05-08
 
 **Package:** `@realtimex/sdk` (CJS) · **Server:** `http://localhost:3001`
 **Developer Mode auth:** `Authorization: Bearer <apiKey>`
@@ -84,6 +84,8 @@ await sdk.desktopRuntimeSessions.launchTerminalShell({
 });
 ```
 
+Default rule: when launching a shell with an initial command, prefer `initialCommandMode: 'direct'` unless the user explicitly wants prefill-only behavior.
+
 Common mistake:
 
 ```js

package/skills/realtimex-moderator-sdk/references/known-issues.md

@@ -1,6 +1,6 @@
 # Known Issues — Source-Detected
 
-> Auto-generated by `scripts/generate-skill.mjs` · SDK **1.7.11** · 2026-05-07
+> Auto-generated by `scripts/generate-skill.mjs` · SDK **1.7.13** · 2026-05-08
 
 Run `node scripts/generate-skill.mjs --force` after SDK source changes to refresh.
 

package/skills/realtimex-moderator-sdk/scripts/rtx.js

@@ -365,7 +365,11 @@ CMD['terminal-launch-shell'] = async () => {
   if (flags.thread) body.threadSlug = flags.thread;
   if (flags.presentation) body.presentationMode = flags.presentation;
   if (flags.command) body.initialCommand = flags.command;
-  if (flags['command-mode']) body.initialCommandMode = flags['command-mode'];
+  if (flags['command-mode']) {
+    body.initialCommandMode = flags['command-mode'];
+  } else if (flags.command) {
+    body.initialCommandMode = 'direct';
+  }
   if (flags.title) body.title = flags.title;
   if (flags.subtitle) body.subtitle = flags.subtitle;
   print(await terminal.launchTerminalShell(body));
@@ -953,6 +957,7 @@ sdk.desktopRuntimeSessions.* — Desktop terminal sessions:
     [--workspace=<slug>] [--thread=<slug>] [--presentation=panel|tab]
     [--command="pwd"] [--command-mode=direct|prefill|shell]
     Launch a visible shell terminal.
+    Default: when --command is provided, it runs in direct mode unless --command-mode is explicitly set.
 
   terminal-launch-cli-agent <agent-name> [<provider-id>] [<message>]
     [--workspace=<slug>] [--thread=<slug>] [--presentation=panel|tab] [--model=<id>]