system · Command reference

qzx killProcess

What it does

Terminates a process by its ID (similar to 'kill' in Unix)

Canonical command: killProcess

Accepted aliases: None

Case-sensitive: no

Included in the published package

Available in PyPI 0.2.2.0.2. This page documents the 0.2.2.0.2 alpha development checkout.

Safety and effects

Can mutate state

No documented dry-run parameter

No native program invocation in the current classification

No documented network use

Outcome may depend on permissions

High-risk execution requires --dangerously-bypass-approvals-and-sandbox or --yolo.

This safety classification was reviewed against implementation digest sha256:ff34a2a47305a1aed63a1dd8b4bd2f9f7bbb98444dd5235a7b9e88dd7fa26779 on 2026-07-24.

Exact syntax

qzx killProcess <pid> [force] --json

Parameters

NameTypeRequiredDefaultDescription
pidintYesNot declaredProcess ID to terminate
forceboolNofalseWhether to force termination (like kill -9)

Input examples

qzx killProcess 1234 --yolo

Terminate PID 1234 when no restorable filesystem target exists

qzx killProcess 1234 true --dangerously-bypass-approvals-and-sandbox

Force terminate PID 1234 without a safety backup

For the complete structured payload, add --json: qzx killProcess <pid> [force] --json

Representative output example

This illustrative JSON is derived from the current implementation-backed result contract. It shows what the command can return without claiming a recorded execution; values vary with inputs, host, permissions, and optional tools.

Example command: qzx killProcess 1234 --yolo --json

{
    "success": true,
    "message": "Terminates a process by its ID (similar to 'kill' in Unix). In this illustrative example, the command completed successfully.",
    "cmd": "Example value",
    "cpu_percent": 42.7,
    "create_time": "Example value",
    "exe": "Example value",
    "forced": true,
    "memory_usage": {
        "rss": [
            {
                "name": "example",
                "status": "ok"
            }
        ],
        "rss_readable": "4.00 KiB"
    },
    "name": "Example value",
    "os_type": "Windows",
    "pid": "Example value",
    "signal": "Example value",
    "user": "Example value"
}
View the JSON result contract
{
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "type": "object",
    "required": [
        "success",
        "message"
    ],
    "properties": {
        "success": {
            "type": "boolean"
        },
        "message": {
            "type": "string"
        },
        "cmd": [],
        "cpu_percent": [],
        "create_time": [],
        "error": {
            "type": "string"
        },
        "exe": [],
        "forced": [],
        "memory_usage": {
            "type": "object",
            "properties": {
                "rss": [],
                "rss_readable": []
            },
            "additionalProperties": true
        },
        "name": [],
        "os_type": [],
        "pid": [],
        "signal": {
            "type": "string"
        },
        "user": []
    },
    "additionalProperties": true
}

Errors and limits

The public contract requires success=false and a descriptive message on failure. This catalog does not yet declare a command-specific error taxonomy; inspect the result and do not invent error codes.

QZX is alpha software. Optional dependencies, permissions, and host capabilities can change the result.

Evidence workflow: requires a controlled privileged environment.

Evidence and provenance

Tests
No command-specific test file with the same module name was found; this does not prove that all coverage is absent.
Documentation channel
Development documentation 0.2.2.0.2 · main · sha256:319b16857a87636ebc3b89734cc040a737bb56194464fca33ce73bdae2043096
Availability
0.2.2.0.2 or earlier

Keep exploring

These commands also belong to the system category. Compare them to choose the operation that best fits your task.

Explore all QZX commands