@realtimex/sdk 1.7.10 → 1.7.11

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@realtimex/sdk",
-    "version": "1.7.10",
+    "version": "1.7.11",
     "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

@@ -2,12 +2,12 @@
 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.10
+sdk_version: 1.7.11
 ---
 
 # RealTimeX Moderator (SDK Source-Verified)
 
-Interact with the RealTimeX platform (`http://localhost:3001`) using `@realtimex/sdk` **v1.7.10**. Authentication is automatic when running inside RealtimeX.
+Interact with the RealTimeX platform (`http://localhost:3001`) using `@realtimex/sdk` **v1.7.11**. Authentication is automatic when running inside RealtimeX.
 
 `<SKILL_DIR>` below refers to the directory containing this SKILL.md.
 
@@ -20,6 +20,7 @@ SKILL=<SKILL_DIR>/scripts/rtx.js
 ENV=--env-dir=<cwd>
 
 node "$SKILL" ping                                     $ENV
+node "$SKILL" context                                 $ENV
 node "$SKILL" agents                                   $ENV
 node "$SKILL" workspaces                               $ENV
 node "$SKILL" threads <workspace-slug>                 $ENV
@@ -52,6 +53,21 @@ When the skill runs inside a spawned ACP or desktop terminal session, RealtimeX
 
 The bundled `sdk-init` and `rtx.js` helpers use those env vars as default context for terminal actions and thread listing. Explicit arguments still win.
 
+## Workspace And Thread Rule
+
+When the skill is used and a task needs workspace/thread context:
+
+1. Check current context first.
+   Use `const { sdk, context } = await initSDK()` or `node "$SKILL" context`.
+2. If `context.workspaceSlug` or `context.threadSlug` exists, use it as the default.
+3. If the user explicitly provided workspace/thread, those values override the default context.
+4. If no current context is available:
+   - list workspaces first
+   - list threads for the chosen workspace if a thread is needed
+   - ask the user only when still ambiguous
+
+Do not guess a workspace or thread if the current context is unknown.
+
 ---
 
 ## Desktop Terminal Sessions

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.10** · 2026-05-07
+> Auto-generated from `@realtimex/sdk` source · v**1.7.11** · 2026-05-07
 
 **Package:** `@realtimex/sdk` (CJS) · **Server:** `http://localhost:3001`
 **Developer Mode auth:** `Authorization: Bearer <apiKey>`
@@ -42,6 +42,7 @@ Use this module for visible Electron terminal sessions. This is the correct path
 
 Do not use ACP for these unless the user explicitly asks for ACP/headless mode.
 If the current process was spawned by RealtimeX, prefer `process.env.RTX_WORKSPACE_SLUG` and `process.env.RTX_THREAD_SLUG` as default context before guessing or asking the user.
+Always resolve current workspace/thread context first when a terminal action needs it: explicit user input > spawned-process env > list workspaces/threads > ask user if still ambiguous.
 
 ### `V1DesktopRuntimeSessionsModule`
 

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.10** · 2026-05-07
+> Auto-generated by `scripts/generate-skill.mjs` · SDK **1.7.11** · 2026-05-07
 
 Run `node scripts/generate-skill.mjs --force` after SDK source changes to refresh.
 

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

@@ -73,6 +73,15 @@ function resolveWorkspaceFlagOrContext(context = {}) {
 // ---------------------------------------------------------------------------
 const CMD = {};
 
+CMD.context = async () => {
+  const { context } = await getSDK();
+  print({
+    workspaceSlug: context?.workspaceSlug || null,
+    threadSlug: context?.threadSlug || null,
+    hasContext: Boolean(context?.workspaceSlug || context?.threadSlug),
+  });
+};
+
 // -- ping -------------------------------------------------------------------
 // Source: index.ts → sdk.ping() → { success, mode, appId, timestamp }
 CMD.ping = async () => { const { sdk } = await getSDK(); print(await sdk.ping()); };
@@ -892,6 +901,7 @@ Connection:
 
 sdk.api.*:
   agents / workspaces / threads <slug> / task <uuid>
+  context
 
 sdk.activities.*:
   activities [--status --limit --offset]