[FEATURE] Show active loops (`/loop`) in the status bar and task list

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When using /loop to schedule recurring tasks (e.g., /loop 5m /clear), the created loops are completely invisible in the UI. There is no indication anywhere that scheduled tasks are running in the background.

Note: the fact that loops survive /clear is actually a great feature! It enables useful patterns like /loop 5m /clear for automatic context management. The problem is purely about visibility, not behavior.

The issues:

1. No visibility — after /clear, the user has no way to know that previously scheduled loops are still active and will continue executing
2. No discoverability — with 2+ active loops, it's hard to remember what's scheduled without checking via CronList tool or asking Claude directly
3. No management UI — there's no quick way to see, stop, or inspect active loops from the interface

Proposed Solution

Reuse the existing background tasks UX (Ctrl+T task list, status bar indicator) for loops:

Status bar indicator

Show active loop count in the status bar, similar to the background tasks indicator:

Opus 4.6 | Context: 14.0% used  |  3 loops

Task list integration (Ctrl+T)

Include active loops in the existing task list view alongside background processes:

Background Tasks:
  #1  npm run dev          running    3m ago

Active Loops:
  #1  /clear       every 5m    next: 2m
  #2  /compact     every 10m   next: 7m
  #3  /commit      every 30m   next: 12m

With the ability to stop individual loops from this view, just like background tasks.

Why reuse background tasks UX

• Users already know Ctrl+T and the status bar indicators
• No new UI concepts to learn
• Consistent with how Claude Code handles other "invisible" running processes
• Scales well for users with many active loops (task list already supports up to 10 items)

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

Reproduction of the core issue

1. Start Claude Code
2. Run /loop 5m /clear
3. Run /clear
4. Observe: no indication that a loop is still active
5. Wait 5 minutes — context gets cleared unexpectedly

Environment

• Claude Code CLI (v2.1.71)
• macOS / Linux