[FEATURE] Default remote working directory option

[andortoth-central]

Use Case / Problem

Every time I launch an interactive session to work in my Fabric workspace, I have to first enter into it (cd). After a while this gets quite frustrating. It would be great if I could use an configuration option (e.g. default_remote_path), a command line option (e.g. --default-remote-path) to set the context in advance.

Proposed Solution

Add a default_remote_path config option and a --default-remote-path CLI option.

Alternatives Considered

I have tried to make a Bash alias, to switch to interactive mode and then fab cd ..., and then switching back to command_line, but "Mode configuration is deprecated", so it's not a viable option.

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

No response

[microsoft-github-policy-service]

Thank you for submitting this issue, @andortoth-central.
A member of the Fabric CLI team will review your submission and provide feedback shortly.

[github-actions]

AI Assessment: Needs Discussion

There is clear value in supporting a "default workspace path" for interactive sessions, as it improves UX and workflow efficiency. However, integrating a config option for persistent default context, as well as a global command-line flag, raises questions about consistency with CLI conventions and potential ambiguity across modes and command invocation.

A config option (e.g., default_remote_path) introduces implicit state and breaks the path-first model, increasing risk for confusion if users forget their context. A global flag such as --default-remote-path is not currently supported, nor is a generic mechanism for pre-setting working directory outside of command invocation. POSIX and GNU conventions typically rely on explicit path arguments or cd; implicit context switches may confuse users and impact script predictability. Intercepting this at shell entry (interactive mode) would require careful design. There are also implications for backwards compatibility and discoverability.

The request merits discussion around:
(1) Potential breakage or confusion from implicit state.
(2) Consistency with existing CLI patterns and standards.
(3) Whether the feature is best implemented as a config, flag, or via enhancement of interactive mode startup behavior.

Next Steps

🔔 Escalated to team — This issue requires team review and has been flagged for attention.

---

💡 If this issue requires the team's attention and was not escalated, you can tag @microsoft/fabric-cli-dev to notify the team.

[github-actions]

🔔 @microsoft/fabric-cli-dev — This issue has been flagged by AI triage as requiring team attention. Please review the assessment above.