by adom

Drive your Claude Code sessions from your phone — every container's sessions in one board. Talk to any of them by voice or text, pick the model per session, and get a push when a session asks a question or is ready for you. Install this CLI to hook a container in and manage its keeper.

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Download

name: session-monitor-cli description: The Session Monitor CLI — the `session-monitor` command to install and manage a container's keeper (start/stop/status/logs) and check keeper-fleet health. Use when someone wants to hook a container into the Session Monitor, start/stop/check the keeper, see whether a keeper is reporting, or open their dashboard. Trigger words — session-monitor cli, session monitor command line, manage the keeper, keeper status, start the keeper, stop the keeper, keeper fleet health, is my keeper reporting, sm cli.

session-monitor-cli

The session-monitor command manages this container's keeper and queries the fleet. It's the doer paired with the natural-language adom-remote-control skill — a package deal.

Install

adom-wiki pkg install adom/session-monitor-cli   # puts `session-monitor` on your PATH

Commands

session-monitor keeper start --token <YOUR_TOKEN>   # install + supervise the keeper here
session-monitor keeper status                        # local daemon/keeper + is the service getting reports?
session-monitor keeper stop                          # stop this container's keeper
session-monitor keeper logs -n 60                    # tail the keeper log
session-monitor status                               # keeper-fleet health across your containers
session-monitor open                                 # dashboard URL (with your token) for your phone
session-monitor version

Add --json to any command for a {status, message, data, hints} envelope.

Notes

The token gates the service; it's a secret — not bundled. Ask whoever runs the monitor. (session-monitor token mint <email> works only on the service container.)
The keeper is a supervised daemon (singleton-locked nohup loop + cron watchdog). keeper start installs + keeps it alive; it survives laptop-off.

---
name: session-monitor-cli
description: The Session Monitor CLI — the `session-monitor` command to install and manage a container's keeper (start/stop/status/logs) and check keeper-fleet health. Use when someone wants to hook a container into the Session Monitor, start/stop/check the keeper, see whether a keeper is reporting, or open their dashboard. Trigger words — session-monitor cli, session monitor command line, manage the keeper, keeper status, start the keeper, stop the keeper, keeper fleet health, is my keeper reporting, sm cli.
---

# session-monitor-cli

The `session-monitor` command manages **this container's keeper** and queries the
fleet. It's the doer paired with the natural-language
[`adom-remote-control`](https://wiki.adom.inc/adom/adom-remote-control) skill —
**a package deal**.

## Install

```bash
adom-wiki pkg install adom/session-monitor-cli   # puts `session-monitor` on your PATH
```

## Commands

```bash
session-monitor keeper start --token <YOUR_TOKEN>   # install + supervise the keeper here
session-monitor keeper status                        # local daemon/keeper + is the service getting reports?
session-monitor keeper stop                          # stop this container's keeper
session-monitor keeper logs -n 60                    # tail the keeper log
session-monitor status                               # keeper-fleet health across your containers
session-monitor open                                 # dashboard URL (with your token) for your phone
session-monitor version
```

Add `--json` to any command for a `{status, message, data, hints}` envelope.

## Notes

- The **token** gates the service; it's a secret — not bundled. Ask whoever runs
  the monitor. (`session-monitor token mint <email>` works only on the service
  container.)
- The **keeper** is a supervised daemon (singleton-locked nohup loop + cron
  watchdog). `keeper start` installs + keeps it alive; it survives laptop-off.