xcodebug 1.2.2 → 1.2.3

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.
@@ -1,15 +1,27 @@
1
1
  ---
2
2
  name: xcodebug
3
- description: "Builds, launches, and captures console logs from physical iOS devices through the xcodebug MCP server. Use when the user invokes xcodebug, requests its doctor/devices/status/logs/wait/stop/restart actions, or wants to verify an iOS app on a real device using its console."
3
+ description: "Builds, launches, and captures console logs from physical iOS devices using the registered native xcodebug tool or an explicitly configured xcodebug MCP connection. Use when the user invokes xcodebug, requests its doctor/devices/status/logs/wait/stop/restart actions, or wants to verify an iOS app on a real device using its console."
4
4
  ---
5
5
 
6
6
  # xcodebug
7
7
 
8
- Use the **existing xcodebug MCP connection**. Its tool is named `xcodebug`
9
- (Claude Code: `mcp__xcodebug__xcodebug`; Codex may display `xcodebug.xcodebug`).
10
- Do not run an `xcodebug` shell command or start another MCP server: captures and
11
- restart settings belong to the connected server process. If the tool is absent,
12
- report that the xcodebug MCP connection must be configured first.
8
+ Select the execution tool by exposed capability, not by client name:
9
+
10
+ - If the session exposes the registered native extension tool `xcodebug`,
11
+ execute the action through that tool. A native transport exposed as
12
+ `xd://xcodebug` is the same backend: read its live schema, then write the action
13
+ JSON to that URI. Reading a schema or this skill does not execute an action.
14
+ - If the user explicitly requests the native extension but it is not exposed,
15
+ report that it must be loaded. Do not substitute MCP or a shell command.
16
+ - Otherwise, use only an existing configured xcodebug MCP tool, commonly named
17
+ `mcp__xcodebug__xcodebug` or `xcodebug.xcodebug`. If it is absent, report the
18
+ missing connection; do not start another server.
19
+ - Captures and restart settings belong to the selected tool's process. Do not
20
+ switch backends or substitute another operation.
21
+
22
+ Native command dispatch is enforced by the host's registered command handler,
23
+ not by these instructions. A shared skill may still be discovered through a
24
+ user-level skills directory; these instructions do not disable that discovery.
13
25
 
14
26
  ## Dispatch the request
15
27
 
@@ -17,10 +29,10 @@ Read the request following `/xcodebug` in Claude Code or `$xcodebug` in Codex.
17
29
  Both explicit invocation and a matching natural-language request can use this skill.
18
30
 
19
31
  - With no arguments, call `{"action":"launch"}` once to build as needed, install,
20
- launch and start capturing with the server's defaults. Keep the capture running;
32
+ launch and start capturing with the selected tool's defaults. Keep the capture running;
21
33
  report a launch error without substituting a status query or another action.
22
34
  - For `status`, call `{"action":"status"}` to inspect captures without launching.
23
- - For an explicit action, call the MCP tool with that action and the supplied
35
+ - For an explicit action, call the selected tool with that action and the supplied
24
36
  parameters immediately. Do not replace execution with instructions for the user.
25
37
  - Accept `action [key=value ...]`, `action=... [key=value ...]`, or a JSON parameter
26
38
  object. Actions: `doctor`, `devices`, `changes`, `build`, `install`, `launch`,
@@ -28,10 +40,11 @@ Both explicit invocation and a matching natural-language request can use this sk
28
40
  - Use the live tool schema for parameter names and types. Preserve quoted strings,
29
41
  numeric `since`/`limit`/`timeoutSeconds`, booleans, JSON `args` arrays and
30
42
  `environment` objects. Keep a supplied `command` shell line intact.
31
- - Omit unspecified parameters so the server can apply its project configuration.
32
- MCP supports pull reads: omit `push` or use `push="off"`; `context` and `wake`
33
- are unsupported. Explain an unsupported explicit value instead of changing it silently.
34
- - For an explicit action, make exactly one xcodebug MCP call, report its result,
43
+ - Omit unspecified parameters so the selected tool can apply its project configuration.
44
+ - Only on MCP, use pull reads: omit `push` or use `push="off"`; `context` and
45
+ `wake` are unsupported. Explain an unsupported explicit value instead of changing it silently.
46
+ Native tools retain their live schema's push modes.
47
+ - For an explicit action, make exactly one selected-tool call, report its result,
35
48
  and stop, including on error. Do not add diagnostic `status` calls or retry
36
49
  with another action unless the user asks. `logs` never authorizes launching
37
50
  an app, and `launch` does not imply an immediate `stop`.
@@ -42,7 +55,7 @@ Both explicit invocation and a matching natural-language request can use this sk
42
55
 
43
56
  ## Examples
44
57
 
45
- | Request after the skill name | MCP arguments |
58
+ | Request after the skill name | Selected tool arguments |
46
59
  |---|---|
47
60
  | *(no arguments)* | `{"action":"launch"}` |
48
61
  | `status` | `{"action":"status"}` |
@@ -77,13 +90,16 @@ Both explicit invocation and a matching natural-language request can use this sk
77
90
  that would break the console bridge. Use the returned exit code and logs as evidence.
78
91
  - A capture that ended on its own says why in `status`, under `logs`, and in the
79
92
  reply of the `wait` or `command` it interrupted: the app exited, or was
80
- restarted outside the capture. It gives a crash report path when the device
81
- wrote one. A reply can also warn that a console reattach relaunched the app.
93
+ restarted outside the capture. Interrupted actions wait for the existing
94
+ crash-report search and include its system termination cause and report path
95
+ when available; missing evidence is reported explicitly, not guessed. Caller
96
+ cancellation still applies. A reply can also warn that a console reattach
97
+ relaunched the app.
82
98
  Report these with the result; the log then does not describe one
83
99
  uninterrupted run.
84
100
  - When a verification goal is answered, stop the capture started for that goal.
85
101
  Include its `captureId` so other captures are not stopped. An explicit `stop`
86
- without an ID intentionally stops all running captures in this server.
102
+ without an ID intentionally stops all running captures in the selected tool.
87
103
  - Report the operation's result, relevant log evidence, capture ID/cursor or log
88
104
  path when returned, and whether capture remains active. Do not invent device
89
105
  activity, successful builds, or test outcomes.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xcodebug",
3
- "version": "1.2.2",
3
+ "version": "1.2.3",
4
4
  "type": "module",
5
5
  "description": "Build, install and launch an iOS app on a physical device and read its console inside the agent session (pi / omp extension)",
6
6
  "keywords": [
@@ -25,10 +25,13 @@
25
25
  "bugs": {
26
26
  "url": "https://github.com/sublimter/xcodebug/issues"
27
27
  },
28
+ "bin": {
29
+ "xcodebug-setup-codex": "./bin/xcodebug-setup-codex.mjs"
30
+ },
28
31
  "files": [
29
32
  "*.ts",
33
+ "bin/",
30
34
  "mcp/",
31
- "skills/",
32
35
  "claude/",
33
36
  "README.md",
34
37
  "GUIDE.md",
@@ -48,7 +51,8 @@
48
51
  "pi": {
49
52
  "extensions": [
50
53
  "./index.ts"
51
- ]
54
+ ],
55
+ "skills": []
52
56
  },
53
57
  "peerDependencies": {
54
58
  "@earendil-works/pi-coding-agent": "*",