file · Command reference

`qzx changePermissions`

What it does

Changes permissions of a file or directory

Canonical command: changePermissions

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

Before mutation, QZX creates a recovery archive; --dangerously-bypass-approvals-and-sandbox/--yolo explicitly skips it.

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

Exact syntax

qzx changePermissions <path> <mode> [recursive] --json

Parameters

Name	Type	Required	Default	Description
path	str	Yes	Not declared	Path to the file or directory
mode	str	Yes	Not declared	Permission mode in octal (e.g., 755) or string format (e.g., "a+x")
recursive	bool	No	false	Whether to apply permissions recursively: -r/--recursive for unlimited, -rN/--recursiveN for N levels

Input examples

qzx changePermissions myfile.txt 644

Change file permissions to 644 (rw-r--r--)

qzx changePermissions myscript.sh "a+x"

Make a script executable for all users

qzx changePermissions mydir 755 -r

Change directory permissions recursively

qzx changePermissions mydir 755 -r2

Change directory permissions up to 2 levels deep

For the complete structured payload, add --json: qzx changePermissions <path> <mode> [recursive] --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 changePermissions myfile.txt 644 --json

{
    "success": true,
    "message": "Changes permissions of a file or directory. In this illustrative example, the command completed successfully.",
    "items_modified": "Example value",
    "mode": "default",
    "path": "C:\\project\\example.txt",
    "recursive": true,
    "type": "file",
    "warnings": [
        {
            "name": "example",
            "status": "ok"
        }
    ]
}

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"
        },
        "error": {
            "type": "string"
        },
        "items_modified": [],
        "mode": [],
        "path": [],
        "recursive": [],
        "type": {
            "type": "string"
        },
        "warnings": {
            "type": "array"
        }
    },
    "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

Implementation: src/qzx/commands/file/change_permissions.py
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 file category. Compare them to choose the operation that best fits your task.

Explore all QZX commands