PanOps

Start, stop, and restart from a tile

• Start checks that the app's address is free, launches it the one registered way, and watches its health until it is ready. Slow starters get a longer window.
• Stop asks the app to close gracefully. Force stop appears only if that fails.
• Restart with a new process ends the running copy and starts a fresh one, so a stuck app gets a clean slate and a new process ID.
• Only what it can prove. Before any stop, PanOps checks again that the running program is the one registered for that tile. Apps it did not start, or that others depend on, are shown but never killed.

OllamaRunning

Local language models

Up for

3 h 12 min

Process

00000

Who can connect

This computer only

Identity

Expected program

StopRestart · new processOpenLogs

Icons where they count

A wall of text tiles is hard to scan. Apps you already know, like Blender, Krita, Ollama, and VS Code, now carry their own icons, read straight from the programs themselves. Containers get the container icon while they run, and plain background services stay plain, so the icons you do see mean something.

BlenderRunning

3D creationUp for 42 minReach This computer

KritaStopped

PaintingUp for –Reach –

OllamaRunning

Local modelsUp for 3 hReach This computer

VS CodeRunning

Code editorUp for 5 hReach This computer

Notes vaultRunning

Background serviceUp for 5 daysReach Home network

Private networkRunning

Background serviceUp for 9 daysReach Your devices

A redrawn example: real app icons, placeholder times, and the background services renamed.

Every open port, without a terminal

The Active listeners view lists everything on the machine that is waiting for connections, with a friendly name, the program behind it, and who can reach it. It replaces the command-line tools I used to squint at. Docker containers appear under the plain names I give them, each with the Docker icon, and anything reachable beyond this computer is flagged for review.

PurposeProgramAddressWho can connectManaged

Ollamamodel server0000This computerYes

VS Code helpercode editor0000This computerObserved only

Web searchcontainer0000This computerYes

Memory databasecontainer0000This computerYes

Card showcasepython0000This computerYes

Notes vaultnotes app0000Home networkReview

Unknown helperscript host0000This computerObserved only

A redrawn example. Names are placeholders and addresses are hidden.

A history of every port

Listeners come and go, so PanOps keeps a record. Port History lists every port it has seen in use: the program that held it, when it was first and last seen, and whether it is still open. When something unfamiliar turns up, I search by port, name, or program and see exactly when it started, instead of guessing.

A redrawn example. Ports and process numbers are hidden.

Add your own tile

{
  "name": "My new app",
  "start": "the one command that starts it",
  "stop":  "the one command that stops it",
  "health": "how PanOps knows it is ready"
}

Written down, and closed to the outside

• Every action logged. Starts, stops, and refused requests go into a local journal.
• Signed-in sessions only. Controls need a session from this computer and a fresh check on every change.
• Honest about limits. It reports what it can see; it does not claim the machine is spotless.