What's new in TidyPorts.

Ask what's holding a port, from the terminal.

tidy-ports who 3000 names the owner — the agent, the terminal, the branch — then offers a free port to use instead, or the command to stop it.

Agents check before they act.

The Claude Code skill now tells agents to ask who owns a port rather than editing your app's config around a conflict.

An odd process name no longer blanks the list.

A control character in a process or folder name could hide every port behind an error.

Usage reporting now actually sends.

In 1.1.0 and 1.2.0 events were collected but never left the app. What's sent is unchanged, and the switch in Settings still turns it off.

TidyPorts updates itself.

It checks about once a day, and asks before the first automatic check.

Every update is verified twice.

A maintainer signature, plus macOS's own check of the Developer ID signature and notarization ticket.

1.0.0 and 1.1.0 can't update themselves.

They shipped before this, so moving off them takes one manual download.

Anonymous usage data.

A random per-install ID, the app and macOS version, and counts of which features get used. Never port numbers, process names, paths, project or branch names, URLs, or anything you type.

This changes what 1.0.0 promised.

1.0.0 said nothing left your machine, and that was true. From 1.1.0 it isn't: the app makes one outbound request when it opens, unless you turn it off in Settings → General.

First public build.

A notarized universal app for macOS 15 and later, free, with no account and no sign-in.

Every dev server, one glance.

Local Ports lists everything listening on your Mac, with the agent, terminal and worktree that launched it.

Tidy up in one click.

The sweep stops what's safe to stop and shows the RAM you get back. Databases, Docker and active stacks are never touched.