You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
'The app exposes a React Native CDP target through Metro',
1658
+
'Symptom: JavaScript heap grows after opening and closing the Cart screen',
1659
+
'Need proof that retained JS objects survive cleanup, plus shortest useful retaining paths',
1660
+
'This is not a native/process memory investigation',
1661
+
],
1662
+
task: 'Plan a bounded React Native JS heap leak workflow using agent-cdp: select the Metro CDP target, sample heap usage, capture baseline/action/cleanup snapshots, diff them, run leak-triplet, and inspect retainers for a leaked node.',
'The app exposes a React Native CDP target through Metro',
1692
+
'Symptom: JavaScript heap may grow after filtering the product list',
1693
+
'Need only a compact first-pass JS heap growth signal before deciding whether to capture heap snapshots',
1694
+
'This is not a native/process memory investigation',
1695
+
],
1696
+
task: 'Plan the CDP commands to select the Metro target and collect compact before/after JavaScript heap usage samples with GC, then diff the usage samples.',
Copy file name to clipboardExpand all lines: website/docs/docs/agent-setup.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ The bundled [agent-device skill](https://github.com/callstack/agent-device/blob/
47
47
Add this as a project rule, custom instruction, or skill equivalent when your agent client supports it:
48
48
49
49
```text
50
-
Use agent-device only for app/device automation tasks. Before planning commands, run `agent-device --version` and read `agent-device help workflow`. For exploratory QA, read `agent-device help dogfood`. For logs, network, traces, or runtime failures, read `agent-device help debugging`. For React Native component trees, props/state/hooks, slow renders, or rerenders, read `agent-device help react-devtools`. For React Native apps, overlays, Metro/Fast Refresh blockers, and routing to React DevTools or debugging evidence, read `agent-device help react-native`.
50
+
Use agent-device only for app/device automation tasks. Before planning commands, run `agent-device --version` and read `agent-device help workflow`. For exploratory QA, read `agent-device help dogfood`. For logs, network, traces, or runtime failures, read `agent-device help debugging`. For React Native component trees, props/state/hooks, slow renders, or rerenders, read `agent-device help react-devtools`. For React Native JavaScript heap growth, heap snapshots, or retained-object leaks, read `agent-device help agent-cdp`. For React Native apps, overlays, Metro/Fast Refresh blockers, and routing to React DevTools or debugging evidence, read `agent-device help react-native`.
51
51
52
52
Use MCP tools or the CLI in the integrated terminal. If `agent-device` is not on PATH but the user installed it globally in another shell, resolve the command the same way the user would from a normal terminal session and run that absolute path instead. This may require inspecting shell startup behavior or package-manager/global bin locations; do not assume the agent process `PATH` is the user's `PATH`. Do not silently fall back to `npx -y agent-device@latest`; ask or use an exact version. MCP exposes structured tools backed by the agent-device client; it does not expose generic shell execution. Prefer `open -> snapshot -i -> act -> re-snapshot -> verify -> close`. Use current refs such as `@e3` for exploration and selectors for durable replay. Keep mutating commands against one session serial. Capture screenshots, logs, network, perf, traces, recordings, and `.ad` replay scripts only when they add evidence.
53
53
```
@@ -111,6 +111,7 @@ Before planning device work, run `agent-device --version` and read `agent-device
111
111
For exploratory QA, read `agent-device help dogfood`.
112
112
For logs, network, traces, or runtime failures, read `agent-device help debugging`.
113
113
For React Native component trees, props/state/hooks, slow renders, or rerenders, read `agent-device help react-devtools`.
114
+
For React Native JavaScript heap growth, heap snapshots, or retained-object leaks, read `agent-device help agent-cdp`.
114
115
For React Native apps, overlays, Metro/Fast Refresh blockers, and routing to React DevTools or debugging evidence, read `agent-device help react-native`.
115
116
116
117
Use the CLI in Cursor's integrated terminal.
@@ -199,6 +200,7 @@ Before planning device work, run `agent-device --version` and read `agent-device
199
200
For exploratory QA, read `agent-device help dogfood`.
200
201
For logs, network, traces, or runtime failures, read `agent-device help debugging`.
201
202
For React Native component trees, props/state/hooks, slow renders, or rerenders, read `agent-device help react-devtools`.
203
+
For React Native JavaScript heap growth, heap snapshots, or retained-object leaks, read `agent-device help agent-cdp`.
202
204
For React Native apps, overlays, Metro/Fast Refresh blockers, and routing to React DevTools or debugging evidence, read `agent-device help react-native`.
Copy file name to clipboardExpand all lines: website/docs/docs/installation.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ Use global install for normal agent workflows. It gives agents a stable `agent-d
21
21
agent-device help workflow
22
22
agent-device help debugging
23
23
agent-device help react-devtools
24
+
agent-device help agent-cdp
24
25
```
25
26
26
27
Some agent clients run commands in an environment that differs from the user's normal install shell. If `agent-device` is missing in the agent terminal but was installed globally elsewhere, resolve the command the same way the user would from a normal terminal session, then use the absolute binary path for agent commands. This may require inspecting shell startup behavior or package-manager/global bin locations; do not assume the agent process `PATH` is the user's `PATH`.
0 commit comments