agent-dev

Name: agent-dev
Availability: InStock
Author: Arnav

Daemonize development server commands with session IDs and persistent logs.

Updated Feb 11, 2026

Search Tags:#automation #logs #cli #session-management #dev-server #daemon #process-control

Ready to run

npx skills add https://github.com/arnavsurve/dotfiles --skill agent-dev-arnavsurve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-dev
Source: https://github.com/arnavsurve/dotfiles/tree/main/agents/skills/agent-dev
Command: npx skills add https://github.com/arnavsurve/dotfiles --skill agent-dev-arnavsurve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing AI development servers can be error-prone and tedious when run as foreground processes. agent-dev provides a lightweight CLI to daemonize, monitor, restart, and log development server processes, giving you reliable background sessions.

Core Features & Use Cases

Daemonize commands to run in background and generate a session ID
Persist logs in ~/.agent-dev or a custom directory
Manage lifecycle: status, restart, and stop
Support named sessions and portless mode for accessible URLs

Quick Start

Start a development server in the background using agent-dev run <your-command>.

Frequently Asked Questions about agent-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a dev server as a background daemon process?▼

Run a dev server as a background daemon process by using a CLI to detach the command, generate a unique session ID, and track the PID for reliable background execution.

How do I manage background process lifecycle and status for development servers?▼

Manage background process lifecycle by executing deterministic CLI operations to check status, restart, or stop detached dev server sessions while preserving logs in a dedicated directory.

Where do daemonized dev server logs get stored for later searching?▼

Daemonized dev server logs get stored persistently in a dedicated directory like ~/.agent-dev or a custom path, allowing you to easily search and access historical session output.

Can I preserve dev server sessions across shell exits without losing the process?▼

Preserve dev server sessions across shell exits by daemonizing commands into detached processes with tracked PIDs, ensuring the server continues running independently of the active terminal shell.

Do I need any external dependencies to daemonize and track CLI processes?▼

No external dependencies are needed to daemonize and track CLI processes; the tool operates independently to manage PIDs, write logs, and expose deterministic start and stop operations.