Connect your AI assistant. Let it set up the monitoring.

1. Open LastPing in the Claude Connectors Directory (https://claude.ai/directory/lastping), or search for LastPing under Settings, Connectors, Discover.
2. Press Connect, sign in to LastPing and allow the connection.
3. Connect it once: the mobile apps use the same connector, and Cowork uses the connectors added to Claude, so it follows this entry.

On a Team or Enterprise plan only an Owner can add it, under Organization settings, Connectors. Members then press Connect beside it under Settings, Connectors.

Settings, Connectors then shows LastPing connected.

In Cowork, paste the reporting block from the monitor's Connect page into the Project's instructions and check that a run arrives; tracing is not available there.

In a terminal, not inside a Claude Code chat:

claude mcp add --transport http --scope user lastping https://mcp.lastping.dev/mcp

Then start Claude Code, type /mcp, choose lastping and sign in to LastPing in the browser that opens. Added lastping with a key before? Remove that entry first:

claude mcp remove lastping --scope user

claude mcp get lastping | grep Status then shows Status: Connected.

Or paste this prompt into Claude Code and it connects LastPing itself, after you approve:

# Paste into Claude Code:
"Connect yourself to LastPing over MCP. First ask me to approve
changing my MCP configuration. Once I approve: if
claude mcp get lastping | grep -q Authorization && echo "added with a key"
prints added with a key, ask me, then run
claude mcp remove lastping --scope user. Then run in a shell:
claude mcp add --transport http --scope user lastping https://mcp.lastping.dev/mcp
Then tell me to type /mcp, choose lastping and sign in to LastPing
in the browser that opens; if /mcp does not list lastping yet, tell
me to restart with claude --continue first. When I say I have signed
in, confirm it: claude mcp get lastping | grep Status shows Status: Connected, and
list_monitors answers."

The sign-in is yours: Claude Code cannot do it for you.

1. On chatgpt.com, open Settings, Security and login, and turn on Developer mode. It is on Plus, Pro, Business, Enterprise and Education plans, on the web.
2. Open Plugins, press + and create an app: name it LastPing, paste https://mcp.lastping.dev/mcp and choose OAuth.
3. Sign in to LastPing and allow the connection.
4. In a chat, choose Developer mode from the + menu and select LastPing.

Install the LastPing plugin from cursor.directory, or add the server yourself to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project). This block has no key:

{
  "mcpServers": {
    "lastping": {
      "url": "https://mcp.lastping.dev/mcp"
    }
  }
}

Open Cursor's MCP settings, click Authenticate next to lastping and sign in to LastPing in the browser that opens. The settings then list lastping with its tools.

Run MCP: Open User Configuration from the Command Palette and merge this block into the file:

{
  "servers": {
    "lastping": {
      "type": "http",
      "url": "https://mcp.lastping.dev/mcp"
    }
  }
}

Start lastping from the file or from MCP: List Servers, then sign in to LastPing in the browser VS Code opens. MCP: List Servers then shows lastping running.

In a terminal, add the server: Codex opens the browser to sign in to LastPing. Added lastping with a key before? Delete its block from ~/.codex/config.toml first.

codex mcp add lastping --url https://mcp.lastping.dev/mcp

If no browser opened:

codex mcp login lastping

codex mcp get lastping | grep enabled then shows enabled: true.

Antigravity CLI (agy) replaced Gemini CLI. In a terminal:

agy mcp add lastping https://mcp.lastping.dev/mcp

Start agy, type /mcp, choose lastping, choose Authenticate and sign in to LastPing in the browser that opens.

In agy, /mcp then shows lastping. If the LastPing tools do not appear, restart with agy -c.

Every app you signed in lists under Settings, Profile, Connected apps in LastPing, where you can disconnect it any time. Resetting your password disconnects every app.

A claude.ai Project in the browser has no shell, so it cannot report runs of its own; it can use LastPing's tools through the connector.

An agent launched as a command (a cron job, a CI step, a script) is wrapped with lastping run (run_wrapper), so a separate process reports:

lastping run --monitor <id> -- ./nightly-summary.sh

Sends each turn's session id, its project (the name of the folder that holds the git repository, or the folder's name when it is not in a repository; a name, never a path) and the hook's version. A turn that ends on an Anthropic server_error, overloaded or rate_limit is an upstream error and pages no one until max(3, the monitor's failure threshold) runs in a row end that way. A permission prompt, an MCP form or a question to you reports the run blocked, and your answer clears it. Installed it before this version? Re-run the Claude Code set-up once.

The agent calls get_ping_instructions with tool set to codex, writes ~/.codex/lastping-report.sh and merges three hooks (SessionStart, UserPromptSubmit and Stop) into ~/.codex/hooks.json, which you trust in /hooks. Written from Codex's documentation and source; not yet run in Codex end to end. Pings from inside a task need network_access = true under [sandbox_workspace_write] in ~/.codex/config.toml, or your approval each time. None of the three hooks reports blocked on its own.

Pair the manual path with expect_every_s and an agent that quietly stops reporting opens a silence incident. Monitors created through the agent wizard get a 24-hour floor already set. The hooks and set-up scripts are POSIX sh: on Windows, run them in WSL or Git Bash; they are untested on Windows.

An on_demand monitor does no absence detection between runs; max_runtime_s bounds a started run; the onboarding wizard pre-fills four hours.