gemini-cli - 💡(How to fix) Fix Plan Mode Path Flattening in `write_file` [1 participants]

What happened?

A critical path-handling bug occurs specifically in Plan Mode when using the write_file tool during the execution of newTrack via the Conductor extension. Even when authorized to write within a specific directory (e.g., base_dir/), any attempt to write to a nested subdirectory (e.g., base_dir/nested/path/file.md) results in the tool stripping all intermediate directories and writing the file directly to the root of the authorized directory (base_dir/file.md).

This behavior causes silent overwriting of existing root-level files (such as index.md) if a nested file shares the same name.

• Intended Path: conductor/tracks/<id>/index.md
• Actual Execution Result: conductor/index.md (Overwrites the main project index)

What did you expect to happen?

The tool should preserve the full relative path provided in the file_path argument, provided that the entire path resides within the authorized directory tree. The directory hierarchy should be respected exactly as specified by the AI agent during the Plan Mode execution.

Client information

Login information

Google Account (via OAuth)

Anything else we need to know?

In Plan Mode, the framework's attempts to organize track-specific files into subfolders result in the accidental destruction of the project's root index.md.

Ref: gemini-cli-extensions/conductor#159

We verified that this only occurs in Plan Mode. In Default Mode, the path handling works correctly and preserves the directory structure.