@swmansion/argent 0.30.2-next.13 → 0.30.2-next.14

package/dist/cli-cmds.mjs

@@ -35578,7 +35578,7 @@ var _CI_VENDOR_COUNT_FOR_TEST = vendors_default.length;
 var SESSION_ID2 = randomUUID5();
 function readCliVersion() {
   if (true) {
-    return "0.30.2-next.13";
+    return "0.30.2-next.14";
   }
   return "0.0.0";
 }

package/dist/installer.mjs

@@ -16899,7 +16899,7 @@ var _CI_VENDOR_COUNT_FOR_TEST = vendors_default.length;
 var SESSION_ID = randomUUID4();
 function readCliVersion() {
   if (true) {
-    return "0.30.2-next.13";
+    return "0.30.2-next.14";
   }
   return "0.0.0";
 }

package/dist/mcp-server.mjs

@@ -28595,6 +28595,7 @@ function toMcpTool(t) {
     name: t.name,
     description: t.description,
     inputSchema: { type: "object", ...withoutRetiredParams(t.inputSchema) },
+    ...t.readOnly ? { annotations: { readOnlyHint: true } } : {},
     ...Object.keys(meta2).length > 0 ? { _meta: meta2 } : {}
   };
 }

package/dist/tool-server.cjs

@@ -100944,7 +100944,7 @@ var _CI_VENDOR_COUNT_FOR_TEST = vendors_default.length;
 var SESSION_ID = (0, import_node_crypto3.randomUUID)();
 function readCliVersion() {
   if (true) {
-    return "0.30.2-next.13";
+    return "0.30.2-next.14";
   }
   return "0.0.0";
 }
@@ -125977,6 +125977,7 @@ Chromium apps are discovered by probing CDP debugging ports (default 9222; exten
 Booted/ready devices are listed first. Platforms whose CLI is unavailable are silently omitted; an empty result usually means xcode-select, Android platform-tools, <flag:harmonyos>DevEco Studio, </flag:harmonyos>or the Vega SDK is not installed.`,
   alwaysLoad: true,
   searchHint: "list devices simulators emulators avd serial udid ios android chromium vega <flag:harmonyos>harmony harmonyos </flag:harmonyos>app fire tv session start",
+  readOnly: true,
   zodSchema,
   services: () => ({}),
   async execute(_services, _params) {
@@ -130727,6 +130728,7 @@ function createHttpApp(registry2, options) {
       if (def.searchHint) entry.searchHint = renderFlagGated(def.searchHint, isFlagEnabled);
       if (def.longRunning) entry.longRunning = true;
       if (def.hideFromMcp) entry.hideFromMcp = true;
+      if (def.readOnly) entry.readOnly = true;
       const aliases = (def.aliases ?? []).map((alias) => ({
         ...entry,
         name: alias,
@@ -133830,6 +133832,7 @@ If state is connecting: do NOT restart the app. Launching it is what starts the
 If state is indeterminate: the process could not be inspected, so restart-app is worth one attempt. If this call still reports it after that restart, do NOT restart the app again: the service is stale rather than the app uninjected, so restart the tool-server (\`argent server stop && argent server start --detach\`) and retry. Remote simulators can never inspect the process, so this is the only unconnected state a running app reaches there.
 Returns { status: "init_failed", message, attempts } instead when the simulator's native-devtools environment failed to initialize.
 Fails if the simulator server is not running for the given UDID.`,
+  readOnly: true,
   zodSchema: zodSchema2,
   services: (params) => ({
     nativeDevtools: nativeDevtoolsRef(resolveDevice(params.udid))
@@ -133987,6 +133990,7 @@ Returns { status: "ok", matches } with matching views including their frames, pr
 At least one of className, identifier, label, tag, or nativeID must be provided.
 If status is restart_required: follow the message (usually restart-app), then retry. If status is service_stale: the app is already injected, so restarting it cannot help. Restart the tool-server (\`argent server stop && argent server start --detach\`) and retry. If the same status comes back after that restart, stop restarting: follow the message, which names the terminal fallback. If status is connect_pending: the app is injected and still connecting. Do not restart it, wait a few seconds and retry. If status is init_failed: the simulator's native-devtools environment could not be initialised. Follow the message (re-boot the simulator) rather than retrying this tool.
 A not-connected or not-running app comes back as one of those statuses rather than a failure. Failures are separate: an Apple system app is rejected outright (terminal: never retry it), and the hierarchy query itself can error or time out.`,
+  readOnly: true,
   zodSchema: zodSchema4,
   services: (params) => ({
     nativeDevtools: nativeDevtoolsRef(resolveDevice(params.udid))
@@ -134057,6 +134061,7 @@ Use when you need deep layout debugging, finding views with no accessibility lab
 Returns { status: "ok", windows, screen } with the full view hierarchy. screen gives the screen size in points on its portrait axes, and the interfaceOrientation of the UI (portrait, portraitUpsideDown, landscapeLeft, landscapeRight). Each screenFrame uses the portrait axes of the screen. Each windowFrame uses the axes of its window, which turn with the UI.
 If status is restart_required: follow the message (usually restart-app), then retry. If status is service_stale: the app is already injected, so restarting it cannot help. Restart the tool-server (\`argent server stop && argent server start --detach\`) and retry. If the same status comes back after that restart, stop restarting: follow the message, which names the terminal fallback. If status is connect_pending: the app is injected and still connecting. Do not restart it, wait a few seconds and retry. If status is init_failed: the simulator's native-devtools environment could not be initialised. Follow the message (re-boot the simulator) rather than retrying this tool.
 A not-connected or not-running app comes back as one of those statuses rather than a failure. Failures are separate: an Apple system app is rejected outright (terminal: never retry it), and the hierarchy query itself can error or time out.`,
+  readOnly: true,
   zodSchema: zodSchema5,
   services: (params) => ({
     nativeDevtools: nativeDevtoolsRef(resolveDevice(params.udid))
@@ -134126,6 +134131,7 @@ normalized contract.
 
 If status is restart_required: follow the message (usually restart-app), then retry. If status is service_stale: the app is already injected, so restarting it cannot help. Restart the tool-server (\`argent server stop && argent server start --detach\`) and retry. If the same status comes back after that restart, stop restarting: follow the message, which names the terminal fallback. If status is connect_pending: the app is injected and still connecting. Do not restart it, wait a few seconds and retry. If status is init_failed: the simulator's native-devtools environment could not be initialised. Follow the message (re-boot the simulator) rather than retrying this tool.
 A not-connected or not-running app comes back as one of those statuses rather than a failure. Failures are separate: an Apple system app is rejected outright (terminal: never retry it), and the screen query itself can error or time out.`,
+  readOnly: true,
   zodSchema: zodSchema6,
   services: (params) => ({
     nativeDevtools: nativeDevtoolsRef(resolveDevice(params.udid))
@@ -134208,6 +134214,7 @@ the UI is landscape.
 
 If status is restart_required: follow the message (usually restart-app), then retry. If status is service_stale: the app is already injected, so restarting it cannot help. Restart the tool-server (\`argent server stop && argent server start --detach\`) and retry. If the same status comes back after that restart, stop restarting: follow the message, which names the terminal fallback. If status is connect_pending: the app is injected and still connecting. Do not restart it, wait a few seconds and retry. If status is init_failed: the simulator's native-devtools environment could not be initialised. Follow the message (re-boot the simulator) rather than retrying this tool.
 A not-connected or not-running app comes back as one of those statuses rather than a failure. Failures are separate: an Apple system app is rejected outright (terminal: never retry it), and the point query itself can error or time out.`,
+  readOnly: true,
   zodSchema: zodSchema7,
   services: (params) => ({
     nativeDevtools: nativeDevtoolsRef(resolveDevice(params.udid))
@@ -134296,6 +134303,7 @@ the UI is landscape.
 
 If status is restart_required: follow the message (usually restart-app), then retry. If status is service_stale: the app is already injected, so restarting it cannot help. Restart the tool-server (\`argent server stop && argent server start --detach\`) and retry. If the same status comes back after that restart, stop restarting: follow the message, which names the terminal fallback. If status is connect_pending: the app is injected and still connecting. Do not restart it, wait a few seconds and retry. If status is init_failed: the simulator's native-devtools environment could not be initialised. Follow the message (re-boot the simulator) rather than retrying this tool.
 A not-connected or not-running app comes back as one of those statuses rather than a failure. Failures are separate: an Apple system app is rejected outright (terminal: never retry it), and the point query itself can error or time out.`,
+  readOnly: true,
   zodSchema: zodSchema8,
   services: (params) => ({
     nativeDevtools: nativeDevtoolsRef(resolveDevice(params.udid))
@@ -141514,6 +141522,7 @@ Use when you need a baseline image before an interaction or to inspect the curre
 Fails if the simulator-server / emulator backend / Chromium CDP <flag:harmonyos>/ \`hdc\` </flag:harmonyos>is not reachable for the given device.`,
     alwaysLoad: true,
     searchHint: "device simulator emulator chromium screen image capture baseline tvos apple tv",
+    readOnly: true,
     zodSchema: zodSchema16,
     outputHint: "image",
     capability: capability8,
@@ -150783,6 +150792,7 @@ after a tap/navigation to wait for the next screen, or before tapping an element
     alwaysLoad: true,
     searchHint: "wait await poll until visible hidden exists text appears disappears timeout element condition settle",
     longRunning: true,
+    readOnly: true,
     zodSchema: zodSchema29,
     capability: capability23,
     services: (params) => {
@@ -151214,6 +151224,7 @@ function createDebuggerStatusTool(registry2) {
 Use when you need to verify connectivity before using other debugger tools. Never fails when the runtime is simply unreachable: it returns a discriminated result instead:
 - { status: "connected", ... } with port, projectRoot (empty on Chromium and on legacy Metro, e.g. Vega), deviceName, appName, logicalDeviceId (absent on Vega), isNewDebugger (false on the legacy inspector), connected flag, loadedScripts count, and sourceMapReady (always true: waits for pending source maps before returning; no-op on Chromium).
 - { status: "not_connected", connected: false, reason, detail, guidance } (port omitted on Chromium) when Metro is not running (reason "metro_not_running"), no app is attached ("no_app_connected"), the device_id matches no target ("device_mismatch"), the CDP endpoint is unreachable or answered malformed ("cdp_unreachable"), the runtime accepted the connection but never answered ("runtime_unresponsive"), the cached connection went stale ("stale_connection"), or a reconnect is in flight ("reconnecting"). Follow the guidance field; do not retry in a loop.`,
+    readOnly: true,
     zodSchema: zodSchema32,
     capability: DEBUGGER_TOOL_CAPABILITY,
     // Resolved manually in execute so a not-connected precondition becomes a
@@ -152325,6 +152336,7 @@ Set includeSkipped=true to see a summary of all filtered components.
 Use when you need tap coordinates for a React Native UI element. Returns a compact text tree with (tap: x,y) coords. Fails if Metro debugger is not connected.`,
     alwaysLoad: true,
     searchHint: "react native component tree discovery tap coordinates",
+    readOnly: true,
     zodSchema: zodSchema35,
     // RN-only: needs the React DevTools backend from the dev JS bundle. Chromium has
     // no equivalent — use `describe` there.
@@ -152841,6 +152853,7 @@ Uses getInspectorDataForViewAtPoint + _debugStack + Metro /symbolicate.
 Set resolveSourceMaps to false to skip symbolication and get raw bundled locations instead.
 Set includeSkipped=true to see filtered items annotated with skip reasons.
 Use when you need the source file and line for a component at a tap coordinate. Fails if the app is not connected or the coordinate is outside the screen.`,
+  readOnly: true,
   zodSchema: zodSchema36,
   // RN-only: needs React Native's internal getInspectorDataForViewAtPoint and
   // Metro's /symbolicate; the Chromium session has no source resolver.
@@ -152958,6 +152971,7 @@ function createDebuggerLogRegistryTool(registry2) {
 Returns the log file path, entry counts by level, and message clusters (grouped by similarity). Works against Hermes (iOS / Android / Vega) and V8 (Chromium).
 Use when investigating warnings, errors, or unexpected output. Call this first for an overview, then read the returned file for details. Returns empty stats if no log data has been captured yet, but check { note }, which is present only when the stats are empty BECAUSE the previous debugger session ended: torn down (e.g. by stop-all-simulator-servers) with its log file deleted, or cut off by the app crashing with its log file kept at the path the note names. Absent that note, empty really does mean the app has logged nothing.
 When the debugger cannot be reached, this tool does not fail: it returns { status: "not_connected", reason, detail, guidance } with NO log file. Follow the guidance (do not retry in a loop). Read a log file in this state only when a { note } names one kept from before the app crashed. A "connected" result's stats may come from a session whose socket has since died. Use debugger-status, not this tool, to judge debugger health.`,
+    readOnly: true,
     zodSchema: zodSchema37,
     capability: DEBUGGER_TOOL_CAPABILITY,
     // Resolved manually in execute so a not-connected precondition becomes a
@@ -153137,6 +153151,7 @@ Each entry includes a requestId that can be passed to view-network-request-detai
 On React Native (iOS / Android / Vega) interception is injected into the JS runtime: it records each request once: XMLHttpRequest (axios included), React Native's fetch, Expo's fetch, and a fetch library that sends through React Native's network module itself, such as react-native-fetch-api (found in a Metro development build). Capture starts at the first network-tool call; a reload clears it. On Chromium it reads the browser's native CDP Network domain (the active tab; all request types).
 Use when inspecting outbound HTTP traffic or debugging API calls in the running app.
 Fails if the app is not connected (RN) or the device is not reachable (Chromium).`,
+  readOnly: true,
   zodSchema: zodSchema38,
   capability: DEBUGGER_TOOL_CAPABILITY,
   services: (params) => {
@@ -153254,6 +153269,7 @@ var networkRequestTool = {
 Returns request/response headers (sensitive headers redacted), status, timing, the request body, and optionally the response body.
 Request and response bodies over 1000 chars are cut to 1000 under a "[TRUNCATED: ...]" line that gives the full size; a binary response body is replaced by "[body omitted: binary <mime>, N bytes]". Use when you need headers, body, or timing for a specific request after listing logs.
 Returns an error message string if the requestId is not found: use view-network-logs to get valid requestId values.`,
+  readOnly: true,
   zodSchema: zodSchema39,
   capability: DEBUGGER_TOOL_CAPABILITY,
   services: (params) => {
@@ -153700,6 +153716,7 @@ since a TV UI has no tap coordinates. Move the highlight with \`tv-remote\` (up/
 back/menu/home), then call describe again to confirm where focus landed.`,
     alwaysLoad: true,
     searchHint: "accessibility element tree ui hierarchy tap coordinates ios android chromium vega <flag:harmonyos>harmony harmonyos </flag:harmonyos>dom tv tvos apple tv android tv fire tv focus focusable remote dpad",
+    readOnly: true,
     zodSchema: zodSchema40,
     capability: capability25,
     services: (params) => {
@@ -154200,6 +154217,7 @@ Use when a program needs element ancestry, such as an e2e engine's scoped select
 Returns { schemaVersion, roots, truncated, alertVisible, keyboardVisible, foregroundApp, unsupportedFields }.
 Fails if the iOS ax-service predates the tree command; update argent.`,
     hideFromMcp: true,
+    readOnly: true,
     zodSchema: zodSchema41,
     capability: capability26,
     services: () => ({}),
@@ -154270,6 +154288,7 @@ function createForegroundAppTool(registry2) {
 Returns { bundleId, name, alertVisible }; under a system alert, bundleId is the app it covers.
 A field is unset when it is unknown.`,
     hideFromMcp: true,
+    readOnly: true,
     zodSchema: zodSchema42,
     capability: capability27,
     services: () => ({}),
@@ -154756,6 +154775,7 @@ panel settles instantly on its last frame, and taps land nowhere until it is wok
 </flag:harmonyos>Use after a launch/navigation to wait for the UI to render before screenshotting or tapping.`,
     searchHint: "wait until screen settles idle stable stops changing animation transition rendered ready before screenshot",
     longRunning: true,
+    readOnly: true,
     zodSchema: zodSchema44,
     capability: capability29,
     services: (params) => {
@@ -155493,6 +155513,7 @@ function createReactProfilerStatusTool(registry2) {
       failedMsg: ({ failureSignal: failureSignal2 }) => `Failed to check React profiler: ${failureSignal2.error_code}`
     },
     description: `Check the state of the React profiler session without side effects. Use after an interruption (debugger disconnect, unexpected error, agent pause) to decide whether to continue with react-profiler-stop, start a new session, or reconnect the debugger. Ownership is verified server-side against this tool-server's in-memory session, so no token-threading is required. Returns { session_status, is_running, current_owner, \u2026 }. If this tool-server process restarted after react-profiler-start, status will report 'taken_over'; use react-profiler-start { force: true } to reclaim.`,
+    readOnly: true,
     zodSchema: zodSchema47,
     // RN-only: companion to react-profiler-start.
     capability: RN_ONLY_TOOL_CAPABILITY,
@@ -157295,6 +157316,7 @@ var reactProfilerComponentSourceTool = {
 Call this per-finding after react-profiler-analyze to inspect source before proposing a fix.
 Returns found: false if the component is not found in user-owned code (e.g. lives in node_modules).
 When several files define a component with the same name (e.g. platform variants like List.tsx and List.web.tsx), returns the primary match and lists the rest under otherMatches[] (file/line/col). Check it before assuming the returned file is the one you meant.`,
+  readOnly: true,
   zodSchema: zodSchema49,
   // Declared so the tool catalogue groups this with the other react-profiler-*
   // tools; the HTTP gate itself is a no-op here, as there is no device arg to
@@ -157433,6 +157455,7 @@ Use when you specifically need to investigate JS CPU hotspots that are NOT tied
 Call react-profiler-stop first. Reads directly from the stored cpuProfile.
 Returns a markdown table of the top hotspot functions with self-time, total-time, and location.
 Fails if react-profiler-stop has not been called or no CPU profile is stored.`,
+  readOnly: true,
   zodSchema: zodSchema50,
   // RN-only: reads a Hermes CPU profile; Chromium's V8 sample format differs.
   capability: RN_ONLY_TOOL_CAPABILITY,
@@ -157547,6 +157570,7 @@ var reactProfilerRendersTool = {
 Returns a markdown table of the top re-rendering components. No profiling session required; works on a live connected app.
 Use when you want a quick snapshot of render counts without a full profiling session.
 Fails if the React DevTools hook is not present in the runtime or the app is not connected.`,
+  readOnly: true,
   zodSchema: zodSchema51,
   // RN-only: queries the React DevTools backend hook on the live runtime.
   capability: RN_ONLY_TOOL_CAPABILITY,
@@ -157723,6 +157747,7 @@ var reactProfilerFiberTreeTool = {
 Use when tracing ancestry of a library component or checking for useMemoCache hook (confirms React Compiler is active on a component).
 Returns a nested JSON tree of fiber nodes with name, tag, actualDuration, selfBaseDuration, and children.
 Fails if the React DevTools hook is not present or no fiber roots have been committed yet.`,
+  readOnly: true,
   zodSchema: zodSchema52,
   // RN-only: walks the fiber tree via the React DevTools backend hook.
   capability: RN_ONLY_TOOL_CAPABILITY,
@@ -163239,6 +163264,7 @@ Every table states how many samples it covers and how much of that was idle.
 Use when investigating JS CPU hotspots or correlating CPU cost with specific components.
 Returns a markdown table of CPU hotspots, call tree, or per-component CPU breakdown.
 Fails if no CPU profile is stored; run react-profiler-stop first.`,
+  readOnly: true,
   zodSchema: zodSchema58,
   // RN-only: reads Hermes-format CPU profiles; Chromium's V8 sample format differs.
   capability: RN_ONLY_TOOL_CAPABILITY,
@@ -163598,6 +163624,7 @@ Modes:
 Use when drilling into specific components or time windows after react-profiler-analyze.
 Returns a markdown table or tree of commit data matching the requested mode.
 Fails if react-profiler-stop has not been called or no commit data is stored.`,
+  readOnly: true,
   zodSchema: zodSchema59,
   // Reads React commit data captured via the React DevTools backend.
   capability: RN_ONLY_TOOL_CAPABILITY,
@@ -163987,6 +164014,7 @@ Modes:
 Use when drilling into native hang stacks, thread CPU breakdown, or memory leaks after native-profiler-analyze.
 Returns a markdown report with native call stacks, thread weights, or leak details for the selected mode.
 Fails if native-profiler-analyze has not been run or no parsed trace data is in memory.`,
+  readOnly: true,
   zodSchema: zodSchema60,
   // No chromium entry: it has no native trace capture.
   capability: {
@@ -164074,6 +164102,7 @@ Requires both react-profiler-analyze and native-profiler-analyze to have been ca
 Call this tool when both profilers were run in parallel on the same session.
 Returns a markdown report correlating hangs with React commits, memory leaks, and investigation hints.
 Fails if either react-profiler-analyze or native-profiler-analyze has not been called first.`,
+  readOnly: true,
   zodSchema: zodSchema61,
   // iOS reads xctrace output; Android re-queries the Perfetto .pftrace via
   // loadAndroidCombinedData. Chromium has no native trace capture.
@@ -176328,6 +176357,7 @@ Touches no device: nothing is launched, tapped, dispatched or torn down, and no
 needs booting, so calling this costs nothing but a file read.
 Fails if the e2e test file does not exist.
 Address the e2e test exactly as you will address it in e2e-execute: name or flow_path, one and only one; supplying both or neither is rejected. The name goes in \`name\`, which resolves <project_root>/.argent/e2e/<name>.yaml, else .argent/flows/<name>.yaml.`,
+  readOnly: true,
   zodSchema: zodSchema72,
   fileInputs: fileInputs5,
   services: () => ({}),
@@ -176676,6 +176706,7 @@ exploration of anything the snapshot surfaces.
 Use when you need to inspect project configuration without manually reading multiple files.
 Returns partial data if workspacePath does not exist or is not readable; missing items are represented as null or empty collections.
 Fails if the workspacePath is not an absolute path or the directory cannot be accessed.`,
+  readOnly: true,
   zodSchema: zodSchema73,
   fileInputs: fileInputs6,
   services: () => ({}),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@swmansion/argent",
-  "version": "0.30.2-next.13",
+  "version": "0.30.2-next.14",
   "mcpName": "io.github.software-mansion/argent",
   "description": "MCP server for iOS Simulator and Android Emulator control",
   "license": "Apache-2.0",