Skip to content

The Host Window ​

The JetWhale host is one window: a sidebar down the left side that picks what you are debugging and which tool you are looking at, and the selected plugin's own UI filling the rest.

The host window with its parts numbered: 1 the AI activity header, 2 the plugins that need no app, 3 the app picker, 4 the plugin list, 5 the sidebar footer, 6 the selected plugin's UIThe host window with its parts numbered: 1 the AI activity header, 2 the plugins that need no app, 3 the app picker, 4 the plugin list, 5 the sidebar footer, 6 the selected plugin's UI

The numbers follow the sidebar from top to bottom:

  1. The AI activity header
  2. The plugins that need no app
  3. The app picker
  4. The selected app's plugin list
  5. The sidebar footer
  6. The selected plugin's own UI

The plugins are documented on their own pages; this page covers the host around them.

AI activity ​

The sidebar header shows whether an AI agent is connected over MCP. With none connected it reads Connect an AI agent, and clicking it shows the endpoint and the setups to copy; while the MCP server is not running it reads MCP is off. While an agent is connected it reads AI agent connected. While a call runs, a rotating ring goes round the header and the tool's short name (mirror.tap) takes the text's place, with the full name on hover. Clicking it opens the details — the tool, the plugin it operates, the app — and the Follow the AI switch, the same setting as AI Activity.

The sidebar header showing network.listTransactions while an AI agent calls it, with its details open: the tool, the plugin, the app and the Follow the AI switchThe sidebar header showing network.listTransactions while an AI agent calls it, with its details open: the tool, the plugin, the app and the Follow the AI switch

Plugins that need no app ​

Plugins that need no app ("requiresAgent": false — the Device Mirror, for one) are listed at the top of the sidebar, above the app picker. They work as soon as the host starts, with nothing connected, and run once rather than once per app. Switching apps never moves one that is on screen, and a debug-server restart does not close it. Over MCP they live in a session of their own, host, which jetwhale.listSessions always lists first.

Choosing an app ​

One host commonly holds several apps from the same device, so sessions are picked with two dropdowns:

  1. Select Device — one entry per device, keyed by the deviceId the agent reported.
  2. Select App — the apps connected from that device. It appears once the device has more than one app; picking a device selects its first app, so a session is always active.

When nothing is connected the device row reads No app connected. When a session goes away the host says so (<device> · <app> disconnected, or N sessions disconnected when several drop at once, as after a debug-server restart).

Session security indicator ​

Each entry carries a lock icon for how its connection is secured:

LockMeaning
GreenConnected over TLS (wss); encrypted end to end.
NeutralPlain ws over a loopback peer — an app on this machine or an ADB-forwarded device. The traffic never leaves the machine.
NonePlain ws to a non-loopback peer; the traffic is unencrypted on the network.

The plugin list ​

Under the picker are the selected app's plugins, enabled ones first. The rest follow in two grayed groups, each under a fold row:

  • N disabled — installed but switched off; open to begin with unless there are more than two. Clicking one opens a screen with an Enable button.
  • N not in this app — installed in the host, but the app's agent never advertised the plugin; folded to begin with. Clicking one shows how to add it to the app: the Gradle dependency of its agent and its register(...) call to copy, with a link to an official plugin's guide.

The plugin list: three enabled plugins with MCP badges, Debug Actions under 1 disabled, and Storage Inspector under 1 not in this appThe plugin list: three enabled plugins with MCP badges, Debug Actions under 1 disabled, and Storage Inspector under 1 not in this app

With no app connected, the list says Connect an app to see its plugins. With no plugins installed at all, the sidebar says so, with a shortcut to the plugin settings when some jars failed to load; see Host Settings → Plugins.

Every row except a "not in this app" one has an overflow (⋯) menu:

  • Disable / Enable — host-wide, the same toggle as jetwhale.setPluginEnabled over MCP.
  • Pop out — moves the plugin into a window of its own, so you can watch two plugins, or one plugin on two sessions, side by side. The main window offers Bring back to main window, and the menu entry becomes Bring back. A plugin with no UI cannot pop out.

MCP badges ​

A plugin that contributes MCP tools carries an MCP badge on its row. Clicking the badge opens the MCP tools browser filtered to that plugin and the selected session. While an agent calls one of the plugin's tools, the badge fills with the accent color and the row takes a rotating ring, so the plugin being driven is visible even when its label has scrolled away.

EntryWhat it opens
Browse MCP tools (wrench icon)The MCP tools browser, unfiltered.
Settings (gear icon)Host Settings.
About JetWhale (info icon)The version, project links, and OSS Licenses: the open-source components the host ships.

Banners above the plugin area report on updates, which are never applied without a click; see Host Settings → Application.

Collapsing the sidebar ​

The collapse button in the sidebar header shrinks it to an icon rail, and the same button expands it again. The rail lists only the enabled plugins, with no groups and no overflow menu, and its session picker is one flat list of device · app. Every icon names itself in a tooltip.

The log viewer ​

Settings → General → Application → View Application Logs opens the host's own captured stdout/stderr in a separate window: filter by substring, toggle auto-scroll, and clear the buffer. This is the host's log, not the debugged app's: it is where a plugin jar that failed to load, or a server that failed to bind, reports itself. The same buffer backs the jetwhale.getLogs and jetwhale.clearLogs MCP tools.

Released under the Apache License 2.0.