Problem or use case
The floating workspace tends toward a single shared default directory (app/user folder). Users want different projects to open floating terminals in different default paths (for example docs or materials folders). Separately, when YOLO / elevated agent permissions are enabled globally, the floating workspace inherits them — risky if the model misunderstands and deletes files outside the intended tree.
Requests:
- Per-project default floating directory
- Independent YOLO / agent permissions for the floating workspace (not forced to match the main workspace)
Related: resuming a session does not re-enter the floating workspace — #11640.
Proposed solution
- Per-project (or per-repo) default cwd for floating terminals / markdown, not only a global floating directory
- Independent permission / YOLO policy for the floating workspace (safer default; opt-in elevated)
- Keep existing pickers (
pickFloatingWorkspaceDirectory, getFloatingTerminalCwd) but bind defaults to project context
Alternatives or additional context
Workaround today: re-pick directory each time; keep YOLO off in floating. Please include Orca version and OS if you hit related bugs.
Problem or use case
The floating workspace tends toward a single shared default directory (app/user folder). Users want different projects to open floating terminals in different default paths (for example docs or materials folders). Separately, when YOLO / elevated agent permissions are enabled globally, the floating workspace inherits them — risky if the model misunderstands and deletes files outside the intended tree.
Requests:
Related: resuming a session does not re-enter the floating workspace — #11640.
Proposed solution
pickFloatingWorkspaceDirectory,getFloatingTerminalCwd) but bind defaults to project contextAlternatives or additional context
Workaround today: re-pick directory each time; keep YOLO off in floating. Please include Orca version and OS if you hit related bugs.