Zed Workspace Behavior on Linux: Implications for AI Tool Invocation

[Workflofr]

Hi,

When launching Zed with default— without explicitly opening a folder as a project — the editor appears to default to the parent directory of that file as its working context. This implicit behavior can have unintended consequences when invoking command-line tools from within Zed, such as gemini-cli.

In my case, running Zed with a file located directly in my home directory (/home/) results in the entire /home/ directory being treated as the root context. Consequently, any CLI tool executed from Zed inherits access to the full contents of my home directory, which raises concerns around workspace isolation and data exposure.

Regards, F.