Operations are messy. That’s the first rule of the field.

You’re on a mobile engagement, tethered to a flaky 4G connection. Or maybe you’re deep in a red team assessment, pivoting through a chain of VPNs that feels like it’s held together by duct tape and prayers.

Then it happens. The connection drops. The shell hangs.

In the old world, that session was gone. Or worse, you’d restart, create a new log file, and end up with fragmented evidence: session-part1.tty, session-part2.tty. Trying to piece that together for a report is a nightmare I wouldn’t wish on a blue teamer.

Today, An pushed an update to PentLog that changes the game. We stopped treating crashes as failures and started treating them as interruptions.

The Zombie Problem

When a shell session dies uncleanly—network cut, battery death, rage quit—the .tty file is left on disk. It’s a “zombie” record. It has data, but no active process writing to it.

Previously, PentLog would just ignore it. You’d start a new shell, and that old zombie file would sit there, orphaned.

Now, PentLog checks for a pulse.

On startup, it scans the context. If it finds a recent log file that wasn’t closed properly, it flags it. And then, it asks the most important question a tool can ask in that moment:

⚠️ Found crashed session(s) for this context:
[1] Session ID: 95 File: session-kali-20260210-215009.tty (5.2 KKiB) Crashed: 37 minutes ago

? Resume crashed session or start new?: 
▸ Resume most recent
  Start new session

Append, Don’t Fragment

The technical shift here is subtle but tactical. Instead of spinning up a fresh file, we append to the existing one.

We resurrect the zombie.

This preserves the timeline. The evidence remains contiguous. When you replay it later, you don’t see two disjointed movies; you see one continuous operation with a pause in the middle.

UX for the Operator

We also cleaned up how you look back at the chaos.

If you’ve been busy, your log directory is probably a mess of hundreds of sessions. We fixed the replay ordering (newest first, finally) and added pagination.

(showing 1-15 of 86)
[Load More]

It’s small, but when you’re hunting for that one command you ran three hours ago, not having to grep through a directory listing is a luxury.

Why It Matters

Reliability is a feature. In security tools, it’s the only feature that counts when things go south.

You can’t control the network. You can’t always control the target environment. But you should be able to control your data.

PentLog just got a little bit harder to kill. And in this line of work, survival is everything.