# MemOps: Coding-Agent Tasks That Clean Up Their Own Processes

Developer tools · Creator, sole engineer · prototype

Launch a coding task through MemOps and everything it started stops when it ends.

## The detail

Coding agents start dev servers, test runners, browsers and containers, then finish and leave them running. MemOps launches a command inside a Windows Job Object and records what it owns. When the command finishes, fails, times out, or the supervisor itself crashes, the whole process tree stops. An isolated Docker Compose stack can be started and stopped the same way, with data volumes preserved.

Command success and cleanup success are reported separately, each with a receipt. A background worker reconciles exactly the resources a task owned after a crash, and never touches live owners or unrelated apps.

It ships as a native Windows app with Python bundled, a CLI and a standalone dashboard. It has no runtime Python dependencies. The limits are stated: only commands launched through it are covered.

Python, Windows Job Objects, Docker, SQLite.

## What I did

- Ran each task inside a Windows Job Object with recorded ownership, so its whole process tree stops with it
- Handled completion, failure, timeout and a crash of the supervisor itself
- Added owned Docker Compose stacks that stop their containers and keep their volumes
- Reported command success and cleanup success separately, with a receipt
- Built a background worker that reconciles exactly the resources a task owned after a crash
- Shipped a native Windows app, a CLI archive and a standalone searchable dashboard

## Stack

Python, Windows APIs, Docker, SQLite, Desktop Application, CLI Development, Process Management

Case study: https://www.siddhvasudev.com/projects/memops-coding-agent-tasks-that-clean
