[Feature Request] Increase 50 GB workspace disk limit for large product repos in Local mode

[BabjiRishi]

Problem

Azure SRE Agent workspaces have a 50 GB disk limit. When connecting large product repositories (e.g., enterprise .NET monorepos with 10+ projects, build artifacts, and history) in Local mode, the repo clone can consume a significant portion of this limit — leaving insufficient space for the agent's working files, memory, and other connected repos. and Remote option is not working.

Current Behavior

• Workspace disk: 50 GB hard limit
• Local mode: full git clone + platform indexing
• Large repos (>5 GB) risk filling the workspace, especially when multiple repos are connected
• Workaround: use Remote mode, but Remote mode returns 401 for Azure DevOps repos (confirmed May 2026)

Proposed Solution

1. Increase the workspace disk limit to 100 GB or make it configurable per agent
2. OR implement shallow clone / sparse checkout for Local mode to reduce disk footprint
3. OR allow selective file-type indexing (e.g., index only .md, .cs, .json, .yaml — skip .dll, .exe, build outputs)

Use Case

We run 19+ SRE Agents across multiple products. Each product agent connects two repos:

• ops (~50 MB) — agent configuration, skills, knowledge
• Product repo (e.g., 2–8 GB) — source code for code-aware RCA

With the 50 GB limit, connecting a large product repo in Local mode risks workspace exhaustion, forcing us to choose between full code grounding and workspace stability.

Impact

• High — blocks full code-aware RCA for large enterprise codebases
• Affects any team with monorepo or large multi-project solutions

Environment

• Azure SRE Agent (GA, June 2026)
• Regions: East US 2, Australia East
• Model: Claude Opus 4.6 (Anthropic)

[dm-chelupati]

Thanks for the feedback, we are looking into increasing the limits