Setting `LargeOutput` doesn't seem to have any effect

Open
#1,788 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the C# configuration shown in the issue with a small MaxSizeBytes value and a custom OutputDirectory. Trace how LargeOutput is handled when tool output exceeds that limit and verify which directory receives the file. Done means oversized outputs are written to the configured directory instead of $TMP.

Written by the indexing model from the issue text.

Description

question

By default, sessions write large outputs to the $TMP directory (e.g. /tmp/1782206406834-copilot-tool-output-s4fxvs.txt). We tried to set LargeOutput to redirect the files to a different directory but it doesn't seem to be change the target directory:

config.LargeOutput = new LargeToolOutputConfig
{
    Enabled = true,
    MaxSizeBytes = 2_000,
    OutputDirectory = outputDir,
}
Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 12h
Merged PRs (30d)
133

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.