Skip to content
Development
Command

/loop-status

Inspect active loop state, progress, failure signals, and recommended intervention.

From plugin
ecc
239k109 skills72 agents109 commands7 hooks
+1
Install
> /plugin marketplace add affaan-m/ECC
> /plugin install ecc@ecc

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/loop-status

Context preview

What this command does when you run it.

Inspect active loop state, progress, failure signals, and recommended intervention.

Command definition

loop-status.md
description: Inspect active loop state, progress, failure signals, and recommended intervention.

Loop Status Command

Inspect active loop state, progress, and failure signals.

This slash command can only run after the current session dequeues it. If you need to inspect a wedged or sibling session, run the packaged CLI from another terminal:

npx --package ecc-universal ecc loop-status --json

The CLI scans local Claude transcript JSONL files under `~/.claude/projects/**` and reports stale `ScheduleWakeup` calls or `Bash` tool calls that have no matching `tool_result`.

Usage

`/loop-status [--watch]`

What to Report

  • active loop pattern
  • current phase and last successful checkpoint
  • failing checks (if any)
  • estimated time/cost drift
  • recommended intervention (continue/pause/stop)

Cross-Session CLI

  • `ecc loop-status --json` emits machine-readable status for recent local

Claude transcripts.

  • `ecc loop-status --home <dir>` scans a different home directory when

inspecting another local profile or mounted workspace.

  • `ecc loop-status --transcript <session.jsonl>` inspects one transcript

directly.

  • `ecc loop-status --bash-timeout-seconds 1800` adjusts the stale Bash

threshold.

  • `ecc loop-status --exit-code` exits `2` when stale loop or tool signals are

found, or `1` when transcripts cannot be scanned.

  • `--exit-code` with `--watch` requires `--watch-count` so watchdog scripts do

not wait forever for a process exit.

  • `ecc loop-status --watch` refreshes status until interrupted.
  • `ecc loop-status --watch --watch-count 3 --exit-code` refreshes a bounded

number of times, then exits with the highest status seen.

  • `ecc loop-status --watch --watch-count 3` emits a bounded watch stream for

scripts and handoffs.

  • `ecc loop-status --watch --write-dir ~/.claude/loops` maintains

`index.json` and per-session JSON snapshots for sibling terminals or watchdog scripts.

Watch Mode

When `--watch` is present, refresh status periodically. With `--json`, each refresh is emitted as one JSON object per line so another terminal or script can consume the stream.

Snapshot Files

Use `--write-dir <dir>` when a separate process needs to inspect loop state without waiting for the current Claude session to dequeue `/loop-status`. The CLI writes:

  • `index.json` with one row per inspected session.
  • `<session-id>.json` with the full status payload for that session.

These files are snapshots of local transcript analysis. They do not control or timeout Claude Code runtime tool calls.

Arguments

$ARGUMENTS:

  • `--watch` optional
Read more
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin