What did Hlido score persistproc?

persistproc scored 64/100 (FADING) in Hlido's independent, hands-on review.

How much does persistproc cost?

Hlido recorded the pricing model as: Open source. Derived from evidence Hlido holds, not vendor-supplied; verify current prices on the vendor's pricing page.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

persistproc

Name: persistproc review
Item: persistproc
Rating: 64
Author: Hlido Editor

Infrastructure · tested 2026-08-18 · re-test due 2026-11-16 · by the Hlido desk, not the vendor

In short: A deliberately tiny MCP server that gives any agent shared visibility and control over your long-running dev processes — the copy-paste killer for AI coding — and its restraint (three tools, no config file) is the design, not a gap.

Visit persistproc → scorecard.json

Quick answer

persistproc scores 64/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-08-18). FADING (64) because persistproc is a focused, well-designed and honestly-scoped utility — an MCP + CLI process layer with a deliberately minimal three-tool surface, tool-agnostic, MIT-licensed and runtime-configured — th Pricing: Open source (free entry point documented).

Hlido Editor · 2026-08-18

persistproc solves an unglamorous but constant friction in AI-assisted development: your dev server, database and build watcher run in terminals your agent cannot see, so you spend the session copy-pasting error output from your terminal into Cursor or Claude Code and back. persistproc is an MCP server and CLI that puts those processes on a shared layer — prefix a command with `persistproc` (e.g. `persistproc npm run dev`) and any MCP-compatible agent can list processes, read their output, and start/stop/restart them, while you still see the output in your own terminal and can Ctrl+C as usual. The design choices are quietly excellent and stated with rare honesty. There is no config file — processes are managed entirely at runtime — and the author explicitly scopes it: 'this is not a replacement for supervisord.' The tool surface is intentionally just three (ctrl, list, output) because 'LLMs perform worse with too many tools, to the point where some IDEs cap how many you can have' — a maturity most tools lack. It is tool-agnostic (Claude Code, Cursor, Gemini CLI all see the same processes, unlike Cursor's own terminal which only its agents can see), MIT-licensed, and pip-installable. The limits are exactly what you would expect from an early, focused utility: it is at v0.2.1 with a small apparent following, solo-maintained, narrow by design, and there is no adoption or reliability evidence on the surface beyond the documentation. It also only helps for processes you start through it. But as a small, honest, well-reasoned piece of agent-dev plumbing, it is easy to recommend for its exact job.

Why FADING

FADING (64) because persistproc is a focused, well-designed and honestly-scoped utility — an MCP + CLI process layer with a deliberately minimal three-tool surface, tool-agnostic, MIT-licensed and runtime-configured — that genuinely removes copy-paste friction in agent-assisted development. It sits below STEADY because it is early (v0.2.1), solo-maintained, narrow by design, and carries no adoption, scale or reliability evidence on the captured surface beyond its documentation.

What it does well

Gives any MCP agent shared visibility and control (list, read output, start/stop/restart) over long-running dev processes
Removes the copy-paste loop — the agent reads process output directly instead of you relaying errors
Keeps the tool surface deliberately to three (ctrl, list, output) because LLMs degrade with too many tools
Is tool-agnostic: Claude Code, Cursor and Gemini CLI all see the same processes, unlike editor-locked terminals
Needs no config file — processes are managed entirely at runtime — and installs via pip

What it fails at

Only helps for processes you start through persistproc; externally-started processes need a different approach
Early (v0.2.1), solo-maintained, with a small apparent following and no adoption/reliability evidence on the surface
Deliberately narrow — explicitly not a supervisord replacement or a general process supervisor
Requires running a dedicated server process and adopting the `persistproc <cmd>` habit
No security/auth discussion on the surface for the local MCP server it exposes

Best for

Developers using AI coding agents who are tired of copy-pasting dev-server errors into and out of the chat
Multi-agent or multi-tool setups (Claude Code + Cursor + Gemini CLI) that need one shared view of running processes
Complex local stacks (API + frontend + builder + database) where an agent reading all logs at once speeds diagnosis
Anyone wanting a minimal, MIT-licensed, config-free process layer rather than a heavy supervisor

Not recommended for

Production process supervision — the author explicitly says it is not a supervisord replacement
Teams needing managed support, auth controls or reliability guarantees
Workflows whose processes are started by other systems and can't be launched through persistproc
Users wanting a rich, many-tool control surface rather than three deliberate primitives

Pricing & access

ModelOpen source
Free entry pointYes — a free tier or open-source edition is documented

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-18.

Compared to

Agent Manager shared-process-visibility-for-agents
persistproc manages the processes agents depend on (dev servers, databases) and gives agents shared read/control over them; Agent Manager orchestrates the agent sessions themselves. One sits under the agents, the other over them — complementary layers of an agent-dev workflow rather than substitutes.

Agent relevance

CLI MCP Behavioral-testable

Agentic-Commerce Readiness 50/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

Runs a standard MCP server on 127.0.0.1:8947 with three tools (ctrl, list, output) any MCP-compatible client can call; `persistproc serve` prints per-agent configuration on start. Squarely agent-facing plumbing — its purpose is to let an agent see and control the developer's running processes. Install via pip and start processes through persistproc.

Agent-friendly score: 7/10

Evidence

MCP server + CLI; prefix a command with persistproc to expose it to agents — source (2026-08-18) verified
Three tools (ctrl, list, output), intentionally minimal for LLM reliability — source (2026-08-18) verified
Tool-agnostic (Claude Code, Cursor, Gemini CLI), MIT-licensed, pip-installable, no config file — source (2026-08-18) verified
Adoption or reliability evidence beyond documentation — source (2026-08-18)

scorecard.json · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-16

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/irskep-persistproc.svg)](https://hlido.eu/check/?agent=irskep-persistproc)

HTML

<a href="https://hlido.eu/check/?agent=irskep-persistproc"><img src="https://hlido.eu/badge/irskep-persistproc.svg" alt="Hlido trust score"></a>