---
title: "List Worktrees Pending Cleanup"
method: GET
path: "/projects/{project_id}/worktrees/pending_cleanup"
---

# List Worktrees Pending Cleanup

`GET /projects/{project_id}/worktrees/pending_cleanup`

## Request

- Base URL: `https://usemeridian.us` (the document declares no server; this is the origin it was published from)
- URL: `https://usemeridian.us/projects/{project_id}/worktrees/pending_cleanup`
- Auth: none declared

e401221d — read-only: worktree rows still marked active in the DB whose
owning sprint item/session has reached a terminal state (see
`db.list_worktrees_pending_cleanup`, a03c0eeb), i.e. "dead" worktrees.

Non-destructive — unlike `POST /worktrees/sweep` this never touches disk
or the DB; it just exposes the same candidate list so a CLIENT-SIDE hook
(the e401221d orphan-process reaper, `meridian/orphan_reaper.py`) can
cross-reference locally running pixi/python/node processes against these
paths and reap the ones rooted in a dead worktree. Exposed on both
self-hosted and hosted deployments (unlike the sweep endpoint) since it
performs no filesystem access itself — only the caller's own local hook
process touches the caller's machine.

## Path parameters

- `project_id` string, required

## Response `200`

Successful Response

- object[]

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/usemeridian/apis/meridian.md) · [All operations](https://skmtc.dev/usemeridian/apis/meridian/llms.txt) · [OpenAPI document](https://skmtc.dev/usemeridian/apis/meridian/revisions/f37a894bd374?raw)