gemini-cli - 💡(How to fix) Fix Feature request: expose GEMINI_SYSTEM_MD path in --include-directories for relative reference resolution [1 participants]

TL;DR

To fix the issue with relative file references in custom system prompts, automatically add the directory of the GEMINI_SYSTEM_MD file to the list of directories used for relative file reference resolution.

Guidance

• When setting GEMINI_SYSTEM_MD, consider using the --include-directories option with the directory of the GEMINI_SYSTEM_MD file to ensure relative file references are resolved correctly.
• Verify that the directory of the GEMINI_SYSTEM_MD file is included in the list of directories used for relative file reference resolution to prevent silent failures.
• To implement the suggested fix, modify the Gemini CLI to automatically add dirname(GEMINI_SYSTEM_MD) to the list of directories used for relative file reference resolution.
• Document the requirement to pair GEMINI_SYSTEM_MD with --include-directories $(dirname $GEMINI_SYSTEM_MD) to ensure correct relative file reference resolution.

Example

GEMINI_SYSTEM_MD=/path/to/agent/instructions/AGENTS.md
--include-directories /path/to/agent/instructions/

Alternatively, the Gemini CLI could be modified to automatically include the directory of the GEMINI_SYSTEM_MD file:

GEMINI_SYSTEM_MD=/path/to/agent/instructions/AGENTS.md
# Automatically include /path/to/agent/instructions/ in the list of directories

Notes

The suggested fix assumes that the Gemini CLI has the capability to modify the list of directories used for relative file reference resolution. If this is not the case, an alternative solution may be required.

Recommendation

Apply workaround by using --include-directories with the directory of the GEMINI_SYSTEM_MD file, as this provides a reliable solution until the Gemini CLI is modified to automatically include the directory of the GEMINI_SYSTEM_MD file.