Torpor for macOS

With several coding sessions open, I wanted to understand their memory footprint and decide which ones could be closed. The usual resident-memory figure did not tell the whole story for idle processes whose memory macOS had compressed.

Torpor uses macOS's physical-footprint measurement and discovers sessions through Claude Code's registry. That makes the implementation specific to how these sessions run, rather than relying only on a process-name match.

Before ending a session, Torpor records its command line and terminal context. The revive path uses that saved information to resume the conversation with its original launch options.

The interface keeps the frequent actions close: inspect the sessions, choose an idle one, hibernate it, and bring it back later. SwiftUI and AppKit provide the native settings and menu bar experience.

• Session discovery through the Claude Code registry
• Memory measurement using macOS phys_footprint
• Saved command-line and terminal context for revival
• Native appearance and menu bar controls

Torpor is available as an open-source macOS app. The repository includes the implementation, documentation, and releases; the screenshots above show the actual product.

It grew out of a practical problem in my own development workflow. The interesting engineering sits behind the small interface: process discovery, meaningful memory accounting, and the transition from an active session to one that can be resumed.