Instant compaction triggered on simple 'copilot set' prompt

[crmitchelmore]

Bug Report

User: crmitchelmore

Prompt:

Can we default the mcps to off in copilot set

Observed Behavior:
The conversation immediately triggered compaction after performing basic search operations, before any substantive response was generated.

Session Output:

✓ Grep "copilot set" (/Users/cm/.copilot)
  └ 2 files found

✓ Grep "mcps" (/Users/cm/.copilot)
  └ 14 files found

✓ Grep "copilot set.*mcps|mcps.*default" (/Users/cm/.copilot/pkg/universal/0.0.374)
  └ 145 lines found

✓ Read config.json
  └ 21 lines read

● Configured MCP servers: multitasker, vibium

● Connected to GitHub MCP Server

∙ Compacting conversation history... (28s)

Expected Behavior:
The prompt should have been answered without triggering compaction. The searches performed don't seem like they would generate enough context to warrant immediate compaction.

Version: 0.0.374
OS: Darwin (macOS)

[EvanBoyle]

It is possible that some of these searches returned a very large amount of context. The other possibility is that you have very large copilot instructions being loaded.

We shipped an improvement today for tools that return very large outputs (>30kb) we redirect them to a tmp file and instruct the agent to use search and system tools (ie jq) to filter the results down in a way that doesn't blow up context.

Please give that latest release a try.