Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

LargeToolOutputConfig handler is not used in sub agents

Open
#2,161 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
api

Research direction

Start by inspecting .NET SDK session creation and custom-agent setup to trace whether LargeToolOutputConfig is propagated to sub agents. Reproduce a tool call with large output through both the orchestrator and a custom agent; done means custom agents apply the configured handler instead of always writing large results to disk.

Written by the indexing model from the issue text.

Description

I am using custom agents with .NET SDK (Copilot SDK Version: 1.0.8). I am passing LargeToolOutputConfig handler as part of session creation. This works fine if any tool was called as part of orchestrator agent and generated large output. Orchestrator agent handles large out as per LargeToolOutputConfig.

But it doesn't work in case of custom agents. Custom agents are not honoring LargeToolOutputConfig. So, tool calls always write data to disk file in case of large output.

How do we pass LargeToolOutputConfig to custom agents as well?

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 9h
Merged PRs (30d)
131

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.