Goose forwards upstream ACP server context window limits to clients

{
  "event_id": "event_dce9dc0240762d43",
  "topic_id": "ai_coding",
  "event_type": "Bug Fix",
  "event_time": "2026-05-29T01:12:57Z",
  "title": "Goose forwards upstream ACP server context window limits to clients",
  "summary": "The Goose coding agent now dynamically reads the context window size advertised by upstream ACP servers instead of relying solely on a static local configuration, ensuring accurate compaction and truncation decisions.",
  "contribution": "Dynamic propagation of upstream ACP context limits to local client agents.",
  "impact": "Developers wrapping external ACP servers with Goose will no longer experience broken context compression or unexpected token truncation when the remote model’s actual context size differs from their local settings. By dynamically adopting the upstream server’s reported context limit, the agent aligns its compaction and truncation logic with the true capacity of the backend, preventing silent data loss or inefficient memory usage during long sessions. Operators should monitor whether aggressive upstream context reporting triggers premature compaction in edge cases where the local cache assumes a larger window.",
  "maturity": "Code",
  "confidence": 0,
  "importance_score": 0.75,
  "risk_flags": [
    "Context Compaction Overshoot",
    "Upstream Config Drift"
  ],
  "evidence_count": 1
}