city stop

Stop console (and managed child agent processes).

The current implementation also tries to clean up detached orphan processes:

• city runtime (run) processes that are still alive without a pid file
• Console (console run) processes that are still alive without a pid file
• agent daemons (agent start --foreground true) that are still alive without a pid file

On macOS and Linux, city stop stops the matching process group first. ACP executors, shell sessions, and watch child processes started by an agent receive the same stop signal, which prevents orphaned children from continuing to consume memory after the parent process exits.

Usage

city stop

Related commands

• city start
• city status

Example Output (Based on Current Implementation)

The examples below are aligned with current command implementations in packages/downcity/src (including default output mode and field structure). Placeholder values are used for environment-specific fields.

$ city stop
city version: 1.0.0
✅ Console UI stopped
   pid: <uiPid>
   pidFile: <uiPidPath>
   log: <uiLogPath>
✅ DC console stopped
   pid: <pid>
   pidFile: <consolePidPath>
   log: <consoleLogPath>
✅ orphan process stopped
   pid: <orphanPid>
   command: <orphanCommand>

$ city stop
city version: 1.0.0
ℹ️  DC console is not running
   pidFile: <consolePidPath>
   log: <consoleLogPath>