@realtimex/sdk 2.0.26 → 2.0.27

package/index.d.ts

@@ -1550,7 +1550,7 @@ export declare class RealtimeXClient {
   /** Pause one published artifact by artifact id. Paused artifacts remain listed but stop serving publicly. */
   pauseArtifact(options?: PauseArtifactOptions): Promise<PauseArtifactResponse>;
   pauseArtifact(artifactId: string, options?: Omit<PauseArtifactOptions, 'params'>): Promise<PauseArtifactResponse>;
-  /** Return compact workspace, thread, current workspace/thread from explicit workspaceSlug and threadSlug query parameters, LLM provider, model, and CLI agent context for agents before choosing arguments. Agents should pass --workspace-slug "$RTX_WORKSPACE_SLUG" and --thread-slug "$RTX_THREAD_SLUG" when those environment variables exist. */
+  /** Return compact workspace, thread, current workspace/thread, LLM provider, model, and CLI agent context before choosing arguments. Managed RealtimeX terminal authentication supplies the current route automatically; workspaceSlug and threadSlug remain optional compatibility inputs for other callers. */
   prepare(options?: PrepareOptions): Promise<PrepareResponse>;
   prepare(query?: PrepareQuery, options?: Omit<PrepareOptions, 'query'>): Promise<PrepareResponse>;
   /** Promote one workspace-owned agent skill to a global managed skill by copying its files into a new global skill row. */

package/index.js

@@ -1576,5 +1576,5 @@ module.exports = {
   createClient: createRealtimeXClient,
   createRealtimeXClient,
   operations,
-  version: "2.0.26",
+  version: "2.0.27",
 };

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@realtimex/sdk",
-    "version": "2.0.26",
+    "version": "2.0.27",
     "description": "RealtimeX runtime SDK package and moderator agent skill assets.",
     "private": false,
     "main": "./index.js",

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

@@ -20,20 +20,20 @@ This skill drives the `realtimex-pp-cli` binary. Verify the CLI is installed and
 
 1. Install or reinstall the pinned version via npm:
    ```bash
-   npm install -g @realtimex/pp-cli@2.0.26
+   npm install -g @realtimex/pp-cli@2.0.27
    ```
 2. Verify the exact version:
    ```bash
    realtimex-pp-cli --version
    ```
-   The output must be `realtimex-pp-cli 2.0.26`.
+   The output must be `realtimex-pp-cli 2.0.27`.
 
-If `--version` reports "command not found" after install, the npm global bin directory is not on `$PATH`. If it reports any version other than `2.0.26`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
+If `--version` reports "command not found" after install, the npm global bin directory is not on `$PATH`. If it reports any version other than `2.0.27`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
 
 * Always run first:
 
   ```bash
-  realtimex-pp-cli prepare --workspace-slug "$RTX_WORKSPACE_SLUG" --thread-slug "$RTX_THREAD_SLUG" --agent
+  realtimex-pp-cli prepare --agent
   ```
 
 ## Command Reference
@@ -188,7 +188,7 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 **prepare** — Manage prepare
 
-- `realtimex-pp-cli prepare` — Return compact workspace, thread, current workspace/thread from explicit workspaceSlug and threadSlug query parameters
+- `realtimex-pp-cli prepare` — Return compact workspace, thread, current workspace/thread, LLM provider, model
 
 **promote-workspace-agent-skill** — Manage promote workspace agent skill
 
@@ -456,9 +456,9 @@ Verify: `claude mcp list`
    ```bash
    realtimex-pp-cli --version
    ```
-   If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.26`, reinstall the pinned version:
+   If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.27`, reinstall the pinned version:
    ```bash
-   npm install -g @realtimex/pp-cli@2.0.26
+   npm install -g @realtimex/pp-cli@2.0.27
    ```
    Then run `realtimex-pp-cli --version` again and proceed only after exact-version verification succeeds.
 2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
@@ -476,19 +476,21 @@ This skill intentionally exposes a small action-first command set. Prefer these
 * Never call the RealTimeX API directly with `curl`, `fetch`, raw HTTP clients, or custom scripts.
 * If the current CLI cannot do the requested task, say the feature is not available and will be added soon.
 * Use `--agent` on every command.
-* Treat `$RTX_WORKSPACE_SLUG` as the current workspace slug when it is set, and `$RTX_THREAD_SLUG` as the current thread slug when it is set.
-* For requests that refer to "current workspace", "this workspace", "current thread", or "this thread", use those environment values directly when they are available.
-* When you need the resolved current workspace/thread objects or related context, call:
+* In a managed RealtimeX terminal, let `prepare` resolve the current workspace and thread from authenticated terminal-session context. Do not require or forward workspace/thread environment variables to `prepare`.
+* Treat `prepare` as the resolved source of truth for requests that refer to "current workspace", "this workspace", "current thread", or "this thread".
+* `RTX_AGENT_CONTEXT_JSON` and the legacy `$RTX_WORKSPACE_SLUG` and `$RTX_THREAD_SLUG` aliases may be present for runtime compatibility, but do not block on inspecting them or manually pass them to `prepare`.
+* Call the following whenever you need the resolved current workspace/thread objects or related context:
 
   ```bash
-  realtimex-pp-cli prepare --workspace-slug "$RTX_WORKSPACE_SLUG" --thread-slug "$RTX_THREAD_SLUG" --agent
+  realtimex-pp-cli prepare --agent
   ```
 
-* If `$RTX_WORKSPACE_SLUG` or `$RTX_THREAD_SLUG` is missing for a current-context request that requires it, ask for the missing workspace or thread before running the command.
+* For callers outside a managed RealtimeX terminal, `prepare` still accepts explicit `--workspace-slug` and `--thread-slug` compatibility inputs.
+* Ask for a missing workspace or thread only when `prepare` cannot resolve the required current context or when the user intends to target a different context.
 * Always run first:
 
   ```bash
-  realtimex-pp-cli prepare --workspace-slug "$RTX_WORKSPACE_SLUG" --thread-slug "$RTX_THREAD_SLUG" --agent
+  realtimex-pp-cli prepare --agent
   ```
 
 * Use exact workspace slugs, thread slugs, provider ids, model ids, agent `canonical`, and agent `modelId` values from `prepare`.
@@ -530,7 +532,7 @@ For terminal agents and terminal sessions:
 * Use `list-terminal-agents` when you only need available terminal agents. Use `prepare` when you also need workspace/thread/provider/model context.
 * Use `open-terminal-session` to open a new desktop terminal session for a terminal agent. It auto-attaches the CLI controller through the desktop runtime launch request.
 * Use exact `agentName`, `providerId`, and `modelId` values from `list-terminal-agents` or `prepare.agents`.
-* When opening a terminal session for the current thread, pass both `--workspace-slug "$RTX_WORKSPACE_SLUG"` and `--thread-slug "$RTX_THREAD_SLUG"`.
+* When opening a terminal session for the current thread, pass the exact current workspace and thread slugs returned by `prepare`.
 * Use `list-terminal-sessions` to inspect grouped terminal sessions by `workspaceSlug` and `threadSlug`. Each session includes compact identity fields and `attached` status.
 * Use `resume-terminal-session` or `resume-latest-terminal-session` to resume + attach an existing session. Use `terminate-terminal-session` to close + detach a session.
 
@@ -538,7 +540,7 @@ For agent skills:
 
 * Use `list-workspace-agent-skills` before enabling, disabling, or reloading workspace skills.
 * For `reload-agent-skills`, always pass a workspace slug.
-* If the user asks to reload skills for the current workspace, pass `--workspace-slug "$RTX_WORKSPACE_SLUG"`.
+* If the user asks to reload skills for the current workspace, pass the exact current workspace slug returned by `prepare`.
 * After `reload-agent-skills` succeeds, reload your own skill context before relying on updated skill instructions.
 
 For personality and heartbeat setup: