Slack Output Limits in DocsFab

Look up message chunking, question evidence, and replay-window budgets for hosted Slack output.

Slack live-agent answers use the following separate message-formatting settings.

Setting	Default	Behavior
`DOCSFAB_HOST_SLACK_TRANSPORT_TEXT_CHARS`	40,000 characters	Maximum text sent in one Slack message.
`DOCSFAB_HOST_SLACK_LIVE_AGENT_ANSWER_CHUNK_BUDGET`	40,000 characters	Message allowance including its sequence marker. A smaller value produces more messages.
`DOCSFAB_HOST_SLACK_LIVE_AGENT_ANSWER_MAX_CHUNKS`	`0`	Compatibility setting for complete delivery. Positive legacy values are rejected with migration guidance.

Slack truncates message text above 40,000 characters. Its recommendation of 4,000 characters is a readability preference. You can lower the chunk budget for shorter messages without reducing the total answer. DocsFab reserves the actual sequence-marker width and preserves whitespace and Unicode characters while splitting the answer. It no longer cuts the runtime answer to 2,700 characters or stops default delivery after three messages. Remove a legacy positive total-chunk setting or set it to 0. Use the message chunk budget to control readability while preserving the complete answer.

Slack questions have the following separate input allowance.

Setting	Default	Behavior
`DOCSFAB_HOST_SLACK_LIVE_AGENT_TURN_TEXT_MAX_BYTES`	160,000 bytes	UTF-8 question bytes admitted before a job is created. You can lower this allowance.

This is DocsFab’s qualified full-message capacity, not an asserted Slack inbound limit. It preserves 40,000 four-byte Unicode characters. The event, combined frozen inputs, and worker request reserve the actual JSON framing and escaping space needed for that question. Questions over the configured allowance name the byte count, limit, and next action. Reference repository files instead of pasting additional material that does not fit.

A Slack question that names no target= reads only the documentation pages that best match it. The following settings bound how many pages it approves and how much of their text reaches the model.

Setting	Default	Behavior
`DOCSFAB_LIVE_AGENT_ASK_INDEX_PAGES`	6 pages	Pages a Slack question without `target=` may approve from the project’s documentation index. The answer names them and, when more pages matched, how many.
`DOCSFAB_LIVE_AGENT_ASK_INDEX_PAGE_TEXT_BYTES`	32,768 bytes (32 KiB)	Bytes of one approved page a Slack question without `target=` passes to the model. A longer page is cut at the bound, and the evidence and the answer say so.
`DOCSFAB_LIVE_AGENT_ASK_INDEX_TEXT_BYTES`	98,304 bytes (96 KiB)	Bytes of approved page text one Slack question without `target=` passes to the model, shared across its pages. Each page gets its whole text or an equal share; a page cut short is marked in the answer.

Each approved page gets its whole text or an equal share of the per-question allowance, so no page arrives as a few bytes. The answer names the approved pages, marks any page passed only in part, and, when more pages matched, says how many. The model’s evidence and the run record show the same cut, and the model can read the rest with its read tool.

You can continue using the same thread without a lifetime turn quota. Hosted Slack turns remain one-shot jobs: include the required context in each question or reference repository files. Submit the next question after the active turn settles; duplicate Slack deliveries do not create another job.

The complete terminal record still must fit the existing 4 MiB read envelope, including metadata. Citation metadata retains every approved path cited in the answer. The separate runtime replay format has a 32 KiB, six-exchange window: when an exchange does not fit, it is omitted whole and the next model prompt reports the omission. The complete answer remains available for Slack delivery.