From 0a0294c5514900077a7f3111bf0cf2e2bddbf01d Mon Sep 17 00:00:00 2001 From: Maxime Date: Sat, 11 Jul 2026 17:53:19 -0700 Subject: [PATCH] docs: correct payload RECEIPT stdout/stderr cap to 1 MB The run task hardcodes MAX_SIZE to 1 MB (legion_tasking-go service/command_parser/command/run.go), which is the cap the sensor applies to the STDOUT/STDERR buffers returned in the RECEIPT. The page claimed ~10 MB. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_016UqKFhW4MXA1B33f6ohJ8D --- docs/2-sensors-deployment/endpoint-agent/payloads.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/2-sensors-deployment/endpoint-agent/payloads.md b/docs/2-sensors-deployment/endpoint-agent/payloads.md index 892af08ae..c63dcd334 100644 --- a/docs/2-sensors-deployment/endpoint-agent/payloads.md +++ b/docs/2-sensors-deployment/endpoint-agent/payloads.md @@ -19,7 +19,7 @@ It is possible to set the Payload's file extension on the endpoint by making the Payloads are uploaded to the LimaCharlie platform and given a name. The task `run` can then be used with the `--payload-name MY-PAYLOAD --arguments "-v EulaAccepted"` can be used to run the payload with optional arguments. -The STDOUT and STDERR data will be returned in a related `RECEIPT` event, up to ~10 MB. If your payload generates more data, we recommend to pipe the data to a file on disk and use the `log_get` command to retrieve it. +The STDOUT and STDERR data will be returned in a related `RECEIPT` event, up to 1 MB. If your payload generates more data, we recommend to pipe the data to a file on disk and use the `log_get` command to retrieve it. The payload is retrieved by the endpoint agent over HTTPS to the Ingestion API DNS endpoint. This DNS entry is available from the Sensor Download section of the web app if you need to allow it.