Workspace Management Strategy: Fixed vs. Flexible Approach

[Ram9199]

Question:
Should Agent_Sudo require a configured workspace?

Options:

1. Fixed workspace
2. Auto-discovery
3. Multiple workspaces
4. Session workspace

Current decision:
Keep fixed workspace for now because:

• Solves Claude Desktop "/" problem
• Simple implementation
• Low maintenance

Next Steps:
Revisit this decision after feedback from the first 5 external users.

---

Tagging under: archietcture, design

[Ram9199]

This issue is a speculative design roadmap item. The current decision is to keep the fixed workspace strategy to avoid issues with sandbox environments and provide a simple, maintainable implementation. We have deferred this topic and labeled it as 'roadmap' and 'deferred', to be revisited once external user feedback is collected.

[Ram9199]

Observation (2026-06)

Dogfooding with Antigravity revealed configuration duplication.

Many runtimes already provide workspace/project context.
Agent_Sudo currently requires a second workspace boundary.

This creates UX friction because users may expect Agent_Sudo
to govern the runtime environment rather than require a separate
workspace configuration.

Current decision remains unchanged:
keep fixed workspace for now.

However, future evaluation should consider:

• workspace optional mode
• runtime-provided workspace integration
• full-environment governance with policy controls
• preserving workspace restriction as an opt-in safety boundary

No implementation planned at this time.
Collect additional dogfood evidence first.