@realtimex/sdk 2.0.33 → 2.0.34

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -74,5 +74,8 @@ server-error retries reuse the serialized body, timestamp, and delivery ID so
74
74
  the receiving endpoint can deduplicate delivery safely. A successful receipt
75
75
  confirms acceptance and routing, not agent-task completion.
76
76
 
77
- The package also publishes generated skill assets under
78
- `skills/realtimex-moderator-sdk`.
77
+ The package publishes a concise router at `skills/realtimex-moderator-sdk` and
78
+ focused generated skills for workspaces, terminal agents, browser sessions,
79
+ Local Apps, heartbeat, automation flows, artifacts, channels, webhooks, and
80
+ plugin/skill administration. All skills use the same pinned
81
+ `realtimex-pp-cli` binary.
package/index.js CHANGED
@@ -2150,5 +2150,5 @@ module.exports = {
2150
2150
  createRealtimeXClient,
2151
2151
  createRealtimeXWebhookClient,
2152
2152
  operations,
2153
- version: "2.0.33",
2153
+ version: "2.0.34",
2154
2154
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@realtimex/sdk",
3
- "version": "2.0.33",
3
+ "version": "2.0.34",
4
4
  "description": "RealtimeX runtime SDK package and moderator agent skill assets.",
5
5
  "private": false,
6
6
  "main": "./index.js",
@@ -0,0 +1,73 @@
1
+ ---
2
+ name: realtimex-artifacts
3
+ description: "List, publish, inspect, pause, resume, and revoke RealTimeX workspace artifacts. Use for browser-viewable artifact publication and lifecycle management."
4
+ allowed-tools: "Read Bash"
5
+ metadata:
6
+ openclaw:
7
+ requires:
8
+ bins:
9
+ - realtimex-pp-cli
10
+ ---
11
+
12
+ # RealTimeX Artifacts
13
+
14
+ List, publish, inspect, pause, resume, and revoke RealTimeX workspace artifacts. Use for browser-viewable artifact publication and lifecycle management.
15
+
16
+ ## CLI setup
17
+
18
+ This skill uses `realtimex-pp-cli` version 2.0.34. Before using its commands:
19
+
20
+ ```bash
21
+ realtimex-pp-cli --version
22
+ ```
23
+
24
+ If it is missing or does not report `realtimex-pp-cli 2.0.34`, install the pinned version:
25
+
26
+ ```bash
27
+ npm install -g @realtimex/pp-cli@2.0.34
28
+ ```
29
+
30
+ For requests about the current workspace or thread, resolve context first:
31
+
32
+ ```bash
33
+ realtimex-pp-cli prepare --agent
34
+ ```
35
+
36
+ ## Command reference
37
+
38
+ **get-artifact** — Manage get artifact
39
+
40
+ - `realtimex-pp-cli get-artifact <artifactId>` — Get one public artifact by artifact id.
41
+
42
+ **list-artifacts** — Manage list artifacts
43
+
44
+ - `realtimex-pp-cli list-artifacts <workspaceSlug>` — List public artifacts for one exact workspace slug. Revoked artifacts are hidden unless includeRevoked=true is passed.
45
+
46
+ **pause-artifact** — Manage pause artifact
47
+
48
+ - `realtimex-pp-cli pause-artifact <artifactId>` — Pause one published artifact by artifact id. Paused artifacts remain listed but stop serving publicly.
49
+
50
+ **publish-artifact** — Manage publish artifact
51
+
52
+ - `realtimex-pp-cli publish-artifact <workspaceSlug>` — Publish a browser-viewable file or folder under a workspace artifacts directory.
53
+
54
+ **resume-artifact** — Manage resume artifact
55
+
56
+ - `realtimex-pp-cli resume-artifact <artifactId>` — Resume one paused artifact by artifact id.
57
+
58
+ **revoke-artifact** — Manage revoke artifact
59
+
60
+ - `realtimex-pp-cli revoke-artifact <artifactId>` — Revoke one artifact by artifact id.
61
+
62
+ ## Domain rules
63
+
64
+ - Place publishable files or folders under the workspace `artifacts/` directory before publishing.
65
+ - Use the exact artifact identifier returned by list or publish operations for lifecycle changes.
66
+ - Treat revoke as the permanent serving-state action and require an explicit target.
67
+
68
+ ## Shared constraints
69
+
70
+ - Run documented commands with `--agent`.
71
+ - Use exact identifiers returned by `prepare` or the relevant list/get command; do not guess values.
72
+ - Do not bypass the CLI with raw HTTP calls. If a required operation is absent, report that limitation.
73
+ - Ask one concise clarification when required target context is missing or ambiguous.
@@ -0,0 +1,73 @@
1
+ ---
2
+ name: realtimex-automation-flows
3
+ description: "Run RealTimeX automation workflows and guided automation-flow commands, including working-directory setup and workspace layout. Use for explicit multi-step automation execution."
4
+ allowed-tools: "Read Bash"
5
+ metadata:
6
+ openclaw:
7
+ requires:
8
+ bins:
9
+ - realtimex-pp-cli
10
+ ---
11
+
12
+ # RealTimeX Automation Flows
13
+
14
+ Run RealTimeX automation workflows and guided automation-flow commands, including working-directory setup and workspace layout. Use for explicit multi-step automation execution.
15
+
16
+ ## CLI setup
17
+
18
+ This skill uses `realtimex-pp-cli` version 2.0.34. Before using its commands:
19
+
20
+ ```bash
21
+ realtimex-pp-cli --version
22
+ ```
23
+
24
+ If it is missing or does not report `realtimex-pp-cli 2.0.34`, install the pinned version:
25
+
26
+ ```bash
27
+ npm install -g @realtimex/pp-cli@2.0.34
28
+ ```
29
+
30
+ For requests about the current workspace or thread, resolve context first:
31
+
32
+ ```bash
33
+ realtimex-pp-cli prepare --agent
34
+ ```
35
+
36
+ ## Command reference
37
+
38
+ **chat-with-terminal-agent** — Manage chat with terminal agent
39
+
40
+ - `realtimex-pp-cli chat-with-terminal-agent` — Guide a user through sending a chat message to the terminal agent.
41
+
42
+ **goal-kickoff-composer** — Manage goal kickoff composer
43
+
44
+ - `realtimex-pp-cli goal-kickoff-composer` — Verify the shared Project/global Goal kickoff composer, routing, attachment authorization, retry, preview
45
+
46
+ **run-automation-workflow** — Manage run automation workflow
47
+
48
+ - `realtimex-pp-cli run-automation-workflow` — Run any app automation flow or scenario exposed via flowMetadata.cli.enabled=true by passing workflowName.
49
+
50
+ **set-default-workspace-agent** — Manage set default workspace agent
51
+
52
+ - `realtimex-pp-cli set-default-workspace-agent` — Set a workspace default agent from the desktop workspace chat settings UI.
53
+
54
+ **setup-working-dir** — Manage setup working dir
55
+
56
+ - `realtimex-pp-cli setup-working-dir` — Add or edit an agent working directory from the desktop settings UI.
57
+
58
+ **workspace-shell-layout** — Manage workspace shell layout
59
+
60
+ - `realtimex-pp-cli workspace-shell-layout` — Verify workspace navigation, title-bar containment, Files dock behavior
61
+
62
+ ## Domain rules
63
+
64
+ - Do not automatically retry workflow timeouts or server errors; report the failure so the user can decide.
65
+ - Resolve current workspace and thread context before running a flow that depends on them.
66
+ - Use the explicit generated flow command when one exists; use the generic workflow command only for supported workflow input.
67
+
68
+ ## Shared constraints
69
+
70
+ - Run documented commands with `--agent`.
71
+ - Use exact identifiers returned by `prepare` or the relevant list/get command; do not guess values.
72
+ - Do not bypass the CLI with raw HTTP calls. If a required operation is absent, report that limitation.
73
+ - Ask one concise clarification when required target context is missing or ambiguous.
@@ -0,0 +1,69 @@
1
+ ---
2
+ name: realtimex-browser-sessions
3
+ description: "List, create, start, stop, and delete isolated RealTimeX browser sessions. Use for named browser runtime and profile lifecycle work."
4
+ allowed-tools: "Read Bash"
5
+ metadata:
6
+ openclaw:
7
+ requires:
8
+ bins:
9
+ - realtimex-pp-cli
10
+ ---
11
+
12
+ # RealTimeX Browser Sessions
13
+
14
+ List, create, start, stop, and delete isolated RealTimeX browser sessions. Use for named browser runtime and profile lifecycle work.
15
+
16
+ ## CLI setup
17
+
18
+ This skill uses `realtimex-pp-cli` version 2.0.34. Before using its commands:
19
+
20
+ ```bash
21
+ realtimex-pp-cli --version
22
+ ```
23
+
24
+ If it is missing or does not report `realtimex-pp-cli 2.0.34`, install the pinned version:
25
+
26
+ ```bash
27
+ npm install -g @realtimex/pp-cli@2.0.34
28
+ ```
29
+
30
+ For requests about the current workspace or thread, resolve context first:
31
+
32
+ ```bash
33
+ realtimex-pp-cli prepare --agent
34
+ ```
35
+
36
+ ## Command reference
37
+
38
+ **create-browser-session** — Manage create browser session
39
+
40
+ - `realtimex-pp-cli create-browser-session` — Create an isolated named RealTimeX Browser session. When url is supplied, start the session and open that URL.
41
+
42
+ **delete-browser-session** — Manage delete browser session
43
+
44
+ - `realtimex-pp-cli delete-browser-session <sessionName>` — Delete a stopped named RealTimeX Browser session and its isolated profile.
45
+
46
+ **list-browser-sessions** — Manage list browser sessions
47
+
48
+ - `realtimex-pp-cli list-browser-sessions` — List registered RealTimeX Browser sessions and their live runtime state.
49
+
50
+ **start-browser-session** — Manage start browser session
51
+
52
+ - `realtimex-pp-cli start-browser-session <sessionName>` — Start an existing named RealTimeX Browser session, optionally opening an absolute HTTP or HTTPS URL.
53
+
54
+ **stop-browser-session** — Manage stop browser session
55
+
56
+ - `realtimex-pp-cli stop-browser-session <sessionName>` — Gracefully stop an existing named RealTimeX Browser session.
57
+
58
+ ## Domain rules
59
+
60
+ - List browser sessions before lifecycle changes and use the exact returned session name.
61
+ - Create a named session before starting it; stop it before permanent deletion.
62
+ - Treat each named browser session as an isolated profile and do not substitute terminal-session identifiers.
63
+
64
+ ## Shared constraints
65
+
66
+ - Run documented commands with `--agent`.
67
+ - Use exact identifiers returned by `prepare` or the relevant list/get command; do not guess values.
68
+ - Do not bypass the CLI with raw HTTP calls. If a required operation is absent, report that limitation.
69
+ - Ask one concise clarification when required target context is missing or ambiguous.
@@ -0,0 +1,81 @@
1
+ ---
2
+ name: realtimex-channels
3
+ description: "Create, configure, start, stop, and delete RealTimeX chat channels, approve pairing codes, and deliver channel files. Use for Telegram, Zalo, Discord, and other channel integrations."
4
+ allowed-tools: "Read Bash"
5
+ metadata:
6
+ openclaw:
7
+ requires:
8
+ bins:
9
+ - realtimex-pp-cli
10
+ ---
11
+
12
+ # RealTimeX Channels
13
+
14
+ Create, configure, start, stop, and delete RealTimeX chat channels, approve pairing codes, and deliver channel files. Use for Telegram, Zalo, Discord, and other channel integrations.
15
+
16
+ ## CLI setup
17
+
18
+ This skill uses `realtimex-pp-cli` version 2.0.34. Before using its commands:
19
+
20
+ ```bash
21
+ realtimex-pp-cli --version
22
+ ```
23
+
24
+ If it is missing or does not report `realtimex-pp-cli 2.0.34`, install the pinned version:
25
+
26
+ ```bash
27
+ npm install -g @realtimex/pp-cli@2.0.34
28
+ ```
29
+
30
+ For requests about the current workspace or thread, resolve context first:
31
+
32
+ ```bash
33
+ realtimex-pp-cli prepare --agent
34
+ ```
35
+
36
+ ## Command reference
37
+
38
+ **approve-channel-pairing-code** — Manage approve channel pairing code
39
+
40
+ - `realtimex-pp-cli approve-channel-pairing-code <code>` — Approve one pending channel pairing code by visible 6-digit code or database id.
41
+
42
+ **create-channel** — Manage create channel
43
+
44
+ - `realtimex-pp-cli create-channel <workspaceSlug>` — Create a chat channel in one exact workspace. Defaults to Telegram when plugin_type, channelType, and type are omitted.
45
+
46
+ **delete-channel** — Manage delete channel
47
+
48
+ - `realtimex-pp-cli delete-channel <channelId>` — Delete one chat channel by exact channel id.
49
+
50
+ **list-channels** — Manage list channels
51
+
52
+ - `realtimex-pp-cli list-channels` — List configured chat channels. Use returned channel ids with update-channel.
53
+
54
+ **send-channel-file** — Manage send channel file
55
+
56
+ - `realtimex-pp-cli send-channel-file` — Send one local CLI file back to an external channel using an explicit channel delivery context id.
57
+
58
+ **start-channel** — Manage start channel
59
+
60
+ - `realtimex-pp-cli start-channel <channelId>` — Start one chat channel by exact channel id.
61
+
62
+ **stop-channel** — Manage stop channel
63
+
64
+ - `realtimex-pp-cli stop-channel <channelId>` — Stop one chat channel by exact channel id.
65
+
66
+ **update-channel** — Manage update channel
67
+
68
+ - `realtimex-pp-cli update-channel <channelId>` — Update one chat channel by exact channel id. Only channel writable fields are changed.
69
+
70
+ ## Domain rules
71
+
72
+ - List channels before changing them and use the exact channel identifier returned by the server.
73
+ - Use an explicit channel delivery context when sending a file, and send one file per command.
74
+ - Approve only the pairing code explicitly presented by the user or current channel flow.
75
+
76
+ ## Shared constraints
77
+
78
+ - Run documented commands with `--agent`.
79
+ - Use exact identifiers returned by `prepare` or the relevant list/get command; do not guess values.
80
+ - Do not bypass the CLI with raw HTTP calls. If a required operation is absent, report that limitation.
81
+ - Ask one concise clarification when required target context is missing or ambiguous.
@@ -0,0 +1,85 @@
1
+ ---
2
+ name: realtimex-heartbeat
3
+ description: "Configure RealTimeX heartbeat scheduling, agents, active hours, timezone, autopilot, and immediate workspace heartbeat runs. Use for recurring HEARTBEAT.md task execution."
4
+ allowed-tools: "Read Bash"
5
+ metadata:
6
+ openclaw:
7
+ requires:
8
+ bins:
9
+ - realtimex-pp-cli
10
+ ---
11
+
12
+ # RealTimeX Heartbeat
13
+
14
+ Configure RealTimeX heartbeat scheduling, agents, active hours, timezone, autopilot, and immediate workspace heartbeat runs. Use for recurring HEARTBEAT.md task execution.
15
+
16
+ ## CLI setup
17
+
18
+ This skill uses `realtimex-pp-cli` version 2.0.34. Before using its commands:
19
+
20
+ ```bash
21
+ realtimex-pp-cli --version
22
+ ```
23
+
24
+ If it is missing or does not report `realtimex-pp-cli 2.0.34`, install the pinned version:
25
+
26
+ ```bash
27
+ npm install -g @realtimex/pp-cli@2.0.34
28
+ ```
29
+
30
+ For requests about the current workspace or thread, resolve context first:
31
+
32
+ ```bash
33
+ realtimex-pp-cli prepare --agent
34
+ ```
35
+
36
+ ## Command reference
37
+
38
+ **set-heartbeat-active-hours** — Manage set heartbeat active hours
39
+
40
+ - `realtimex-pp-cli set-heartbeat-active-hours` — Set workspace or global ambient-agent active hours using HH:mm start and end values.
41
+
42
+ **set-heartbeat-auto-pilot** — Manage set heartbeat auto pilot
43
+
44
+ - `realtimex-pp-cli set-heartbeat-auto-pilot` — Turn workspace or global ambient-agent heartbeat auto pilot on or off.
45
+
46
+ **set-heartbeat-default-agent** — Manage set heartbeat default agent
47
+
48
+ - `realtimex-pp-cli set-heartbeat-default-agent` — Set workspace or global ambient-agent default terminal agent and optional model for heartbeat defaults and legacy
49
+
50
+ **set-heartbeat-enabled** — Manage set heartbeat enabled
51
+
52
+ - `realtimex-pp-cli set-heartbeat-enabled` — Turn workspace or global ambient-agent heartbeat on or off.
53
+
54
+ **set-heartbeat-interval** — Manage set heartbeat interval
55
+
56
+ - `realtimex-pp-cli set-heartbeat-interval` — Set workspace or global ambient-agent scheduler check interval.
57
+
58
+ **set-heartbeat-timezone** — Manage set heartbeat timezone
59
+
60
+ - `realtimex-pp-cli set-heartbeat-timezone` — Set workspace or global ambient-agent heartbeat timezone, for example Asia/Saigon or UTC.
61
+
62
+ **setup-heartbeat-tasks** — Manage setup heartbeat tasks
63
+
64
+ - `realtimex-pp-cli setup-heartbeat-tasks` — Set up HEARTBEAT.md task instructions for a workspace or global ambient agent.
65
+
66
+ **trigger-workspace-heartbeat** — Manage trigger workspace heartbeat
67
+
68
+ - `realtimex-pp-cli trigger-workspace-heartbeat <workspaceSlug>` — Trigger the default HEARTBEAT.md task for a workspace immediately.
69
+
70
+ **trigger-workspace-heartbeat-tasks** — Manage trigger workspace heartbeat tasks
71
+
72
+ - `realtimex-pp-cli trigger-workspace-heartbeat-tasks <workspaceSlug>` — Trigger specified HEARTBEAT.md task names for a workspace immediately.
73
+
74
+ ## Domain rules
75
+
76
+ - Keep heartbeat instructions in `HEARTBEAT.md`; use the bundled template when creating it.
77
+ - Inspect the current workspace context before changing heartbeat configuration or triggering tasks.
78
+ - Use exact task names from `HEARTBEAT.md` when triggering selected heartbeat tasks.
79
+
80
+ ## Shared constraints
81
+
82
+ - Run documented commands with `--agent`.
83
+ - Use exact identifiers returned by `prepare` or the relevant list/get command; do not guess values.
84
+ - Do not bypass the CLI with raw HTTP calls. If a required operation is absent, report that limitation.
85
+ - Ask one concise clarification when required target context is missing or ambiguous.
@@ -0,0 +1,99 @@
1
+ # Heartbeat Instructions
2
+
3
+ ## Mission
4
+
5
+ Describe the ambient agent's standing responsibility.
6
+
7
+ ## Tasks
8
+
9
+ The scheduler evaluates this `tasks:` block on every heartbeat tick and runs only tasks that are due.
10
+ The first task is treated as the default task unless another task has `default: true`.
11
+ Use `default: true` on exactly one task to make it the default manual heartbeat target.
12
+ Use `default: false` on the first task if you do not want any task to be auto-selected as default.
13
+ Use `interval` for simple timing. Supported units are `m`, `h`, and `d`, for example `3m`, `1h`, or `1d`.
14
+ Omit `interval` and `cron` to run on every scheduler check interval.
15
+ Use `interval: disabled` to keep a task in the file but skip it during scheduled heartbeat checks. Manual triggers can still run the task.
16
+ Use `cron` for complex schedules, for example `0 9 * * *`.
17
+ Agent tasks require `agent`, for example `@codex`.
18
+ Use `model` to run an agent task with a specific model, for example `gpt-5.5-medium`.
19
+ Use `skills` to prefer skills for an agent task, for example `agent-browser, realtimex-moderator-sdk`.
20
+ Use `executor: shell` and `command` to run a shell command instead of an agent. Shell tasks do not use `prompt`.
21
+ When a shell command prints valid JSON, it can trigger additional tasks. Use one of these forms:
22
+
23
+ ```json
24
+ ["task-name-1", "task-name-2"]
25
+ ```
26
+
27
+ ```json
28
+ {
29
+ "tasks": ["task-name-1", "task-name-2"],
30
+ "reason": "metrics changed"
31
+ }
32
+ ```
33
+
34
+ To trigger tasks in another workspace, include `workspace`:
35
+
36
+ ```json
37
+ {
38
+ "workspace": "other-workspace-slug",
39
+ "tasks": ["task-name-1"],
40
+ "reason": "shared dependency changed"
41
+ }
42
+ ```
43
+
44
+ Only valid JSON triggers task dispatch. If the shell output is not valid JSON, no extra tasks are run.
45
+
46
+ tasks:
47
+
48
+ - name: default-review
49
+ default: true
50
+ interval: 30m
51
+ agent: @codex
52
+ model: gpt-5.5-medium
53
+ skills: agent-browser, realtimex-moderator-sdk
54
+ prompt: Review the workspace context and respond HEARTBEAT_OK when no action is needed
55
+ - name: weekday-morning-task
56
+ cron: 0 9 * * 1-5
57
+ agent: @codex
58
+ prompt: Describe what should run on a cron schedule
59
+ - name: sync-metrics
60
+ interval: 30m
61
+ executor: shell
62
+ command: bash ./scripts/sync-metrics.sh
63
+ - name: paused-task
64
+ interval: disabled
65
+ agent: @codex
66
+ prompt: This task is skipped by scheduled heartbeat checks until re-enabled
67
+ - name: another-task
68
+ agent: @codex
69
+ prompt: Tasks without interval or cron run on every scheduler check interval
70
+
71
+ ## Check for
72
+
73
+ - Pending tasks that require follow-up
74
+ - New events that need awareness
75
+
76
+ ## When action is needed
77
+
78
+ - State what should trigger action
79
+ - Describe the preferred next step
80
+ - If calendar routine context is provided, use it only when a concise update would help
81
+
82
+ ## When nothing is needed
83
+
84
+ - Reply exactly HEARTBEAT_OK
85
+
86
+ ## Allowed actions
87
+
88
+ - Review the current workspace context
89
+ - Create or update relevant artifacts when necessary
90
+
91
+ ## Never do
92
+
93
+ - Do not repeat old work without a clear reason
94
+ - Do not take destructive actions without explicit approval
95
+
96
+ ## Style
97
+
98
+ - Be concise
99
+ - Prefer concrete updates over speculation
@@ -0,0 +1,93 @@
1
+ ---
2
+ name: realtimex-local-apps
3
+ description: "Create, inspect, configure, start, stop, restart, and delete RealTimeX Local Apps. Use for local source, npx, uvx, webhook-trigger, status, log, and lifecycle operations."
4
+ allowed-tools: "Read Bash"
5
+ metadata:
6
+ openclaw:
7
+ requires:
8
+ bins:
9
+ - realtimex-pp-cli
10
+ ---
11
+
12
+ # RealTimeX Local Apps
13
+
14
+ Create, inspect, configure, start, stop, restart, and delete RealTimeX Local Apps. Use for local source, npx, uvx, webhook-trigger, status, log, and lifecycle operations.
15
+
16
+ ## CLI setup
17
+
18
+ This skill uses `realtimex-pp-cli` version 2.0.34. Before using its commands:
19
+
20
+ ```bash
21
+ realtimex-pp-cli --version
22
+ ```
23
+
24
+ If it is missing or does not report `realtimex-pp-cli 2.0.34`, install the pinned version:
25
+
26
+ ```bash
27
+ npm install -g @realtimex/pp-cli@2.0.34
28
+ ```
29
+
30
+ For requests about the current workspace or thread, resolve context first:
31
+
32
+ ```bash
33
+ realtimex-pp-cli prepare --agent
34
+ ```
35
+
36
+ ## Command reference
37
+
38
+ **create-local-app** — Manage create local app
39
+
40
+ - `realtimex-pp-cli create-local-app` — Create local app
41
+
42
+ **delete-local-app** — Manage delete local app
43
+
44
+ - `realtimex-pp-cli delete-local-app <appId>` — Delete local app
45
+
46
+ **get-local-app** — Manage get local app
47
+
48
+ - `realtimex-pp-cli get-local-app <appId>` — Get local app
49
+
50
+ **get-local-app-logs** — Manage get local app logs
51
+
52
+ - `realtimex-pp-cli get-local-app-logs <appId>` — Read bounded recent desktop logs. Each entry is capped at 4 KiB and secret-bearing configuration is omitted.
53
+
54
+ **get-local-app-status** — Manage get local app status
55
+
56
+ - `realtimex-pp-cli get-local-app-status <appId>` — Get local app status
57
+
58
+ **list-local-apps** — Manage list local apps
59
+
60
+ - `realtimex-pp-cli list-local-apps` — List local apps
61
+
62
+ **restart-local-app** — Manage restart local app
63
+
64
+ - `realtimex-pp-cli restart-local-app <appId>` — Restart local app
65
+
66
+ **set-local-app-enabled** — Manage set local app enabled
67
+
68
+ - `realtimex-pp-cli set-local-app-enabled <appId>` — Set local app enabled
69
+
70
+ **start-local-app** — Manage start local app
71
+
72
+ - `realtimex-pp-cli start-local-app <appId>` — Start local app
73
+
74
+ **stop-local-app** — Manage stop local app
75
+
76
+ - `realtimex-pp-cli stop-local-app <appId>` — Stop local app
77
+
78
+ **update-local-app** — Manage update local app
79
+
80
+ - `realtimex-pp-cli update-local-app <appId>` — Update local app
81
+
82
+ ## Domain rules
83
+
84
+ - List or inspect an app before changing lifecycle or configuration state, and use the exact app identifier returned by the server.
85
+ - Treat endpoint association and runtime state as server-owned values; confirm status after start, stop, or restart.
86
+ - Use bounded log reads for diagnosis and require explicit user intent before permanent app deletion.
87
+
88
+ ## Shared constraints
89
+
90
+ - Run documented commands with `--agent`.
91
+ - Use exact identifiers returned by `prepare` or the relevant list/get command; do not guess values.
92
+ - Do not bypass the CLI with raw HTTP calls. If a required operation is absent, report that limitation.
93
+ - Ask one concise clarification when required target context is missing or ambiguous.