Windows: ACP agent session does not find the current workspace cwd

[larock22]

Summary

On Windows 11, the Athas ACP agent/chat session does not appear to reliably know the current workspace directory. When asked to inspect or operate in the current project, the agent cannot find the expected current pwd/working directory.

Steps to Reproduce

1. On Windows 11, open a project folder in Athas.
2. Start an Athas agent / ACP agent chat for that workspace.
3. Ask the agent to report the current working directory or inspect files in the opened project.
4. Compare the agent's result with the workspace folder shown in Athas.

Expected Behavior

The agent process and ACP session should use the opened workspace folder as the current working directory, so pwd/path-sensitive operations resolve to the current project.

Actual Behavior

The agent cannot find or use the expected current workspace directory.

Operating System

Windows 11

Version

0.7.0-preview.1

Logs or Screenshots

Code-path notes from local research:

• The frontend gets the workspace path from useProjectStore.getState().rootFolderPath in src/features/ai/services/acp-stream-handler.ts.
• start_acp_agent receives that value as workspace_path in src-tauri/src/commands/ai/acp.rs.
• The ACP bridge passes workspace_path to both the child process startup and ACP session bootstrap in crates/ai/src/acp/bridge_init.rs.
• spawn_agent_process calls cmd.current_dir(path) when workspace_path exists.
• ACP session/new, session/load, and session/resume requests are created with the same derived cwd.
• Relative file paths in AthasAcpClient::resolve_path resolve against workspace_path when it exists.

Checklist

• I searched existing issues first.
• I reproduced this on the latest available version.