#general
Oct 28October 29, 2026
hey community, i wanted to share a small feature preview: we’re now shipping 🤖 SRE in default package (search for SRE in Agents). it helps to triage misconfigurations and ops issues and can cross-reference the source code.
I expect it to be useful for early trials, please LMK if it is any useful!
👀1
7 replies
Hi guys! Can we make this:
env-based? I want to be able to override this to a much larger value on my installation. Ideally configuring it per agent would be awesome, but if not - global per-instance override will be good enough. We have an agent that by default deals with large tool responses. And unforunately downloading the tool result to a file is impossible because we are running it A2A, not in a conversation. And this, from what I understand, makes it impossible to download tool result because there is no conversation id:if (!conversationId || !toolCallId || context.suppressContentLogging) {
return null; // ← no spill, plain truncation
}```
So what would work best for us is, in order from the best option:
1. Allow A2A sessions to also download tool results to disk so it can be grepped/worked with
2. Allow customizing
MAX_TOOL_RESULT_CONTEXT_BYTES per agent3. Allow overriding
MAX_TOOL_RESULT_CONTEXT_BYTES on the instance as env varDo you think it is something that could be done? 🙏
FWiW, what we're doing is automating legal team's work for creating different kinds of contracts. Their requirements got too complex for our team to manage for them, so we tell the agent to fetch additional prompt/requirements from a google doc file that is managed by the legal team - basically doing a controlled prompt injection 😅
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!