Your agents start it. ProcLease stops it.
ProcLease is an open-source Rust CLI that runs local dev processes on a lease. Every service it starts appears in one list across agent sessions, with a declared owner, an optional task label, bounded logs and resource readings. A lease grows only when someone runs extend, and it expires on schedule whether or not the model takes another turn. See how it compares.
RUST CLI / macOS + Linux / MIT
--ttl 2h -- npm run dev
The conversation can end.
The deadline still applies.
01 / THE LIFECYCLE
Background work. Foreground control.
Use the same CLI across projects and agent sessions. Every service has an owner label, a deadline and a place in your process list.
- 01
Start with a lease
Wrap the foreground command you already use. ProcLease supervises its process group in the caller’s execution context.
proclease run --ttl 2h -- npm run dev - 02
See what’s alive
One terminal view for deadlines, CPU and resident memory. Bounded logs and JSON keep later tool calls informed.
proclease watch - 03
Extend, stop, or expire
Add time explicitly when work continues. Otherwise the deadline triggers TERM, then KILL after the shutdown grace.
proclease extend JOB_ID --by 1h
02 / SMALL BY DESIGN
Local supervision. Explicit deadlines.
A focused local tool for the dev server an agent starts and everyone forgets. No hosted service needed to run the CLI.
- Reads don’t renew
- Checking status, logs or resources leaves the lease unchanged.
- History stays bounded
- Up to five completions stay visible for 30 seconds. Finished history is retained for 24 hours or the newest 100 jobs.
- Control stays explicit
- Jobs are supervised individually. No shared service accepts arbitrary commands from another execution context.
03 / GET STARTED
From download to deadline.
Native binaries for macOS and Linux. No Rust toolchain or sudo needed. Each archive includes the portable agent skill.
v0.1.9 / EXPERIMENTAL PRERELEASEcurl -fsSL https://proclease.com/install.sh | sh -s -- --skills bothThe installer selects your platform, verifies the archive’s SHA-256 checksum and installs to ~/.local/bin. Existing unrelated skill folders are preserved.
Verify the archive against SHA256SUMS, extract it, and place proclease on PATH. The archive also contains skills/proclease.
macOS binaries are not Developer ID signed or notarized.
04 / THE AGENT SKILL
Teach the lifecycle. Keep the same workflow.
The shared skill guides Codex and Claude Code to launch with a lease, check readiness and clean up task-only services. Start a new agent session after installation.
$proclease/procleaseSkills guide behavior; they don’t intercept every shell command or grant extra execution permissions.
Read the shared skill05 / KNOW THE BOUNDARY
A few details before you run.
What is ProcLease?
An MIT-licensed Rust CLI and portable agent skill. It starts a foreground dev service under a lease, lists it with its owner and deadline, and stops its process group when the lease expires. It runs locally; no hosted service or account is needed.
Why choose ProcLease?
Choose it when an agent-started dev server needs a lifetime that holds after the conversation ends. Every job carries a declared owner label and an optional task label, appears in one list across sessions, and lives longer only when someone runs extend. Each job is supervised on its own, independent of model turns. Limits stay honest: it is not a sandbox, and a process that leaves its group can escape cleanup. GNU timeout, systemd-run and rentctl cover overlapping needs well, with different trade-offs.
How long does a lease last?
Two hours by default, set with --ttl. You can extend a job explicitly, up to 24 hours of total lifetime from creation. At the deadline it sends TERM, then KILL after a two-second default grace.
Will it find servers I already started?
ProcLease manages services launched through proclease run. It doesn’t adopt existing PIDs. A skill helps the agent choose ProcLease for future launches.
Does closing watch stop my services?
No. Ctrl+C closes the terminal view. A job stops on explicit stop, command exit, expiry or supervision failure. Status and log reads never extend the deadline.
Can I stop several jobs at once?
Yes. In v0.1.5 and later, proclease stop --all --task TASK --dry-run previews a task selection. Remove --dry-run to stop it; add --owner OWNER for an exact owner-and-task match. Run unfiltered stop --all only when you intend to stop every managed job in the selected registry. Labels do not grant permission to stop another task's jobs.
What do CPU and RSS include?
The service and children still in its managed process group, excluding ProcLease supervisors. CPU 100% is one core. RSS sums resident bytes and may count shared pages more than once. Finished jobs have no live readings.
What are the current support limits?
Foreground services on macOS and glibc-based Linux. No Windows, Docker management, auto-restart or arbitrary PID adoption. A descendant that creates a new group can escape cleanup. Use native VM storage for state; deadlines use wall time.
LET THE WORK END CLEANLY.