bryllen-close

Stop Bryllen dev servers and free their ports by PID.

2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/madebynoam/bryllen --skill bryllen-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bryllen-close
Source: https://github.com/madebynoam/bryllen/tree/main/plugin/plugins/bryllen/skills/bryllen-close
Command: npx skills add https://github.com/madebynoam/bryllen --skill bryllen-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bryllen can leave local development servers running and bind ports that block other work. This Skill stops all Bryllen dev servers and frees the used ports to reclaim system resources.

Core Features & Use Cases

  • Safe termination of Bryllen per-project servers by PID, avoiding collateral damage.
  • Cleanup of the .bryllen-ports.json state file to prevent stale port mappings.
  • Quick re-init with Bryllen when needed after stopping the servers.

Quick Start

Stop all Bryllen dev servers for this project and free the associated ports.

Frequently Asked Questions about bryllen-close

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

FAQPage Schema
How do I stop Bryllen dev servers and free their ports?

Stopping Bryllen dev servers safely involves reading the .bryllen-ports.json file to identify specific PIDs and terminating only this project's processes. It then removes the ports record to prevent stale state and confirms completion.

Why do my development ports remain blocked after stopping servers?

Ports remain blocked when stale state mappings persist. This Skill cleans up the .bryllen-ports.json record after terminating the identified PIDs, ensuring ports are actually freed for other work.

Does stopping Bryllen servers terminate other unrelated processes?

No, stopping Bryllen servers does not terminate unrelated processes. The Skill ensures safe termination by targeting only the PIDs listed in this project's ports file, avoiding collateral damage to other system processes.

What is the best way to reclaim system resources from local dev servers?

The best way to reclaim system resources is to safely terminate the specific dev server PIDs and clear their port mappings. This Skill reads the per-project ports file, stops the associated processes, and deletes the stale record.

Can I quickly re-init Bryllen after stopping its dev servers?

Yes, you can quickly re-init Bryllen after stopping its dev servers. The Skill removes the stale ports record during cleanup, which allows for a clean re-initialization when you need to start the servers again.