@slack/radar-mcp 1.3.0 → 1.5.0

package/README.md

@@ -28,24 +28,33 @@ Restart your Claude Code session for the tools to appear.
 The package also ships a browser-based dashboard that shows the same live device data without Claude Code in the loop.
 
 ```bash
-npx -p @slack/radar-mcp slack-radar-web
+npx @slack/radar-mcp web
 ```
 
 Or with a global install:
 
 ```bash
 npm install -g @slack/radar-mcp
-slack-radar-web
+slack-radar
 ```
 
-Opens `http://localhost:8100` automatically. Set `SLACK_RADAR_WEB_PORT` to use a different port. Features:
+Opens `http://localhost:8100` automatically. Set `SLACK_RADAR_WEB_PORT` to use a different port. (`slack-radar-web` still works as a direct alias.) Tabs:
 
-* Live Network / RTM / Clogs tabs with real-time SSE streaming
-* Filter bar for URL, channel, event name, payload text
-* Detail pane with Copy JSON, Copy Body, and Copy cURL buttons
-* Profile selector for personal vs work profile when both are running
-* Auto-extend keeps the device-side server alive while the browser tab is open
-* Enable Radar button handles ADB forwarding and device activation without Claude
+* **Live** — network, RTM, analytics clogs, and Slack-app logcat in one timeline
+* **Network** — calls per second vs response time, every call listed, slow ones flagged
+* **RTM** — real-time websocket events
+* **Clogs** — analytics events, click one to see its payload
+* **Logs** — device logcat, filtered to the Slack app (switch app or clear the filter)
+* **Custom** — a tab Claude builds on request. Ask a Claude Code session in your terminal for a view the pre-built tabs do not cover (e.g. "graph calls per second and flag the slow ones"); it authors the view via the `open_radar_dashboard` tool and it appears here. Persists until you refresh the page.
+
+Each tab has a counter, rate, sparkline, graph, a filter / sort / pause feed, and a payload inspector. Switching tabs replays what you have already seen this session (the browser caches it, bounded by count and age) so the view does not reset to empty. ADB forwarding and device activation are handled for you; a reconnect control re-arms after a device sleep.
+
+### Screen overlay
+
+A **▣ Screen** button opens a side panel that mirrors the live device screen, with a full-resolution screenshot and a screen recording. It is off by default and opens to a consent notice first, because it shows whatever is on the phone (open DMs, message content, notifications).
+
+* **Screenshot** works on any machine (pure `screencap`, no extra tools).
+* **Live mirror and recording** need `ffmpeg` on your machine. If it is missing, the panel shows the install command for your platform and the screenshot still works. ffmpeg is not bundled and is never installed for you.
 
 ## Prerequisites
 
@@ -70,7 +79,7 @@ Radar starts **disabled** each session. All tools except `ping` return an error
 
 | Tool | Description |
 |---|---|
-| `ping` | Health check. Returns uptime, buffer sizes, remaining session time, stream status. Use `timeout_minutes` to extend sessions. |
+| `ping` | Health check. Returns uptime, buffer sizes, remaining session time, stream status, and which app/profile is bound (`android_user_id`, `profile` personal/secondary, `package`). Use `timeout_minutes` to extend sessions. |
 | `get_recent_network_calls` | HTTP call summaries: method, URL, status code, duration. Filterable by URL substring and status code. |
 | `get_network_call_detail` | Full request/response headers and bodies for a specific call (gzip/brotli decompressed). |
 | `get_recent_rtm_events` | RTM event summaries: type, direction, channel, timestamp. Filterable by type, direction, channel. Uses subtypes (e.g. `message_changed`, not `message`). |
@@ -84,6 +93,7 @@ Radar starts **disabled** each session. All tools except `ping` return an error
 | `screenshot` | Capture device screen as PNG. 720px default, `full_res=true` for full resolution. |
 | `record_screen` | Record short screen video (MP4). Default 5s, max 30s. |
 | `clear_buffers` | Clear all captured network calls and RTM events from device and local buffers. |
+| `open_radar_dashboard` | Author or refine a custom live dashboard tab from a spec (source, filters, widgets, alerts). Suggested when a request is not covered by the pre-built tabs; not auto-invoked. Returns the dashboard URL; debug builds only, local only. |
 | `_radar_session_enable` | Enable radar for the session. Called by `/radar-enable` skill. |
 | `_radar_session_disable` | Disable radar for the session. Called by `/radar-disable` skill. |
 
@@ -121,8 +131,9 @@ What gets captured depends on the in-app server implementation. The MCP server i
 * **Network calls**: OkHttp interceptor. Ring buffer: 200 calls.
 * **RTM events**: WebSocket listener. Ring buffer: 500 events.
 * **Clogs**: Analytics interceptor. Ring buffer: 500 events. Persists across radar activation cycles.
+* **SQLite database** (Database tab, web dashboard only): when you open a database, a read-only **plaintext** copy of that on-device store (message text, request/response bodies, user/channel/team IDs) is pulled to a temp directory **on your own machine** (`os.tmpdir()/slack-radar-db-<port>`, files mode 0600). Auto-deleted when the dashboard process stops.
 
-All data is in-memory only. No disk writes.
+The network, RTM, and clog captures are in-memory ring buffers. The Database tab is the exception: it writes a plaintext copy of the selected on-device database to a temp file on your host for the duration of the session. Review before sharing anything from it.
 
 ### What gets captured, in detail
 
@@ -167,11 +178,11 @@ The device-side server may have auto-shut down. Use `/radar-enable` to restart i
 **"Session disabled"**
 Two consecutive connection failures disable the session. Use `/radar-enable` to reconnect.
 
-**Work profile devices**
-The MCP server auto-detects the Android user ID via `ps` and targets the broadcast accordingly. No manual `--user` flag needed. The web dashboard shows a profile selector when both personal and work profiles are running.
+**Devices with more than one user (e.g. a work profile)**
+The MCP server auto-detects the Android user ID via `ps` and targets the broadcast accordingly. No manual `--user` flag needed. In the dashboard's Logs tab, the package filter narrows logcat to the Slack app; clear the chip or pick another package to widen it.
 
 **Tools not appearing after setup**
 Restart your Claude Code session. MCP servers are registered at session start.
 
 **Port already in use (web dashboard)**
-Another instance may be running. Kill it with `lsof -ti :8100 | xargs kill` or set a different port with `SLACK_RADAR_WEB_PORT=8101 slack-radar-web`.
+Another instance may be running. Kill it with `lsof -ti :8100 | xargs kill` or set a different port with `SLACK_RADAR_WEB_PORT=8101 npx @slack/radar-mcp web`.