Fixed profile
The node administrator specifies the profile locally with the agent. Example configuration fragment of a separate Telepúrte Agent:uptime. Do not use this resolution as a “state only”.
Rights and launch
The operator requires permission for a specific profile and node; a regular SSH grant and the right to a typed operation do not replace it. The managed command contract is available through the/api/v1/commands API: first previews, then runs with preview ID. The preview shows the exact profile, parameters, goals and batches. It does not execute the command. Mass launch supports the canary, batch size and error threshold.
If your profile, policy, or rights have changed, form a new preview: Save your launch ID and check the results of each target, rather than repeat the request with a new ID when the network fails.
Agent’s arbitrary shell
For ad hoc modes on the node, aadhoc profile with /bin/sh and empty arguments is explicitly allowed. It executes the transmitted text through the shell; the mere appearance of a profile does not give the user the right.
This mode is not interactive: stdin is closed, the working directory begins with /, the environment and the current directory are not saved between launches. Profile time is limited to 30 seconds, command text is 1 MiB. For long repetitive work, use the script playbook, for interactive - terminal.
Conclusion and Uncertain Results
The agent saves up to 4,096 bytes of the total stdout/stderr. As a result, there’s a completion code, a checksum, and a crop sign. If the output is cropped, the rest won’t appear when you read the same result again. Losing the change-start confirmation gives youexecution_uncertain; there is no automatic repeat command. Check the actual state of the node. Reading the saved output does not repeat the command and is recorded in the audit.
Prohibition and suspension
The administrator can disable the profile on one node or throughout the installation, the prohibition is on top of the permissions, including when issuing a pending task to an agent, the command already issued can run out. Stopping a startup stops future output; it doesn’t equal sending aCtrl-C to an already running process. Prohibiting a profile doesn’t filter commands inside an interactive SSH or automatically block other execution methods.
Verification
Start with astatus reader profile on one node. Check the exact preview profile, completion code, output and audit. For multiple nodes, compare profile definitions and their pre-launch policies.
