---
title: "ktm adb status"
description: "Check each Android phone's agent, ADB bridge status, and current connection holder using the ktm adb status command."
sidebarTitle: "status"
lastUpdated: "2026-09-23"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

{/* GENERATED FILE: do not edit by hand. Regenerate with: node scripts/generate.mjs */}

Show phones, their agent's ADB bridge state, and who is connected

## Usage

```bash
ktm adb status [flags]
```

## Examples

```bash
ktm adb status
ktm adb status --all
ktm adb status --output json
```

## Flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--all` | boolean |  | Include phones that are unconfigured or not attached to an agent |

## Details

One row per Android phone: the agent hosting it, whether that agent's ADB
bridge is on, and — when someone is connected through 'ktm adb connect' — who
holds the phone and since when.

BRIDGE column values: on, off (enable with 'ktm adb enable'), offline (agent
unreachable), unknown (the agent does not expose remote configuration).

BRIDGE and IN USE BY describe adb sessions, which is a different question from
the platform availability shown by 'ktm resources list': a phone can be
Available there while someone holds it here.

Phones that are not configured or not attached to an agent are left out, since
nothing can be connected to them; --all lists them too.

## Related

- [`ktm adb`](/cli/commands/adb)
- [`ktm resources`](/cli/commands/resources)

<Note>
  Global flags (`--output`, `--debug`, `--host`, …) apply to every command. See the [command reference overview](/cli/commands/overview).
</Note>

## What's next?

<Columns cols={2}>
  <Card title="All commands" icon="terminal" href="/cli/commands/overview">
    Browse the full CLI reference.
  </Card>
  <Card title="Get started" icon="rocket" href="/cli/getting-started">
    Install the CLI and authenticate.
  </Card>
</Columns>