[PR #55] [CLOSED] docs: Windows workaround for installing the Gemini extension #85

New issue

Closed

opened 2026-10-15 20:53:18 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 20:53:18 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/rehan-remade/universal-modder/pull/55
Author: @rehan-remade
Created: 10/5/2026
Status: ❌ Closed

Base: main ← Head: docs/gemini-windows-install

📝 Commits (1)

adc8c35 docs: Windows workaround for installing the Gemini extension

📊 Changes

1 file changed (+8 additions, -0 deletions)

View changed files

📝 README.md (+8 -0)

📄 Description

What: a README workaround for #13. On Windows, gemini extensions install https://github.com/rehan-remade/universal-modder can fail with "Configuration file not found".

Gemini CLI finds no GitHub release here, so it falls back to git clone.
The repo has 5 symlinks (GEMINI.md and skills under .agents, .claude, .gemini and .github). If Git for Windows is set to create symlinks but the account can't, the checkout stops at the first one and the clone has no gemini-extension.json.
This is not confirmed on Windows yet; I asked the reporter for their clone output.
Workaround: clone with core.symlinks=false and install from the folder.

Tested with Gemini CLI 0.62 on Linux:

The URL install works.
A core.symlinks=false clone installs from its folder after the trust prompt. All skills (from the extension's skills/), AGENTS.md and the fal MCP server load.
The only noise is a non-fatal "Failed to discover skills: ENOTDIR … .gemini/skills".

Follow-ups to consider (not in this PR):

Drop the .gemini/skills and GEMINI.md symlinks. The extension already loads skills/ and AGENTS.md (contextFileName) by itself; Gemini started inside a clone would then need a .gemini/settings.json instead.
Or publish releases with a packaged extension zip as an asset, so Gemini CLI never clones.

Refs #13

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/rehan-remade/universal-modder/pull/55 **Author:** [@rehan-remade](https://github.com/rehan-remade) **Created:** 10/5/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/gemini-windows-install` --- ### 📝 Commits (1) - [`adc8c35`](https://github.com/rehan-remade/universal-modder/commit/adc8c353047d34347819071490a947c916b92801) docs: Windows workaround for installing the Gemini extension ### 📊 Changes **1 file changed** (+8 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+8 -0) </details> ### 📄 Description **What:** a README workaround for #13. On Windows, `gemini extensions install https://github.com/rehan-remade/universal-modder` can fail with "Configuration file not found". - Gemini CLI finds no GitHub release here, so it falls back to `git clone`. - The repo has 5 symlinks (`GEMINI.md` and `skills` under `.agents`, `.claude`, `.gemini` and `.github`). If Git for Windows is set to create symlinks but the account can't, the checkout stops at the first one and the clone has no `gemini-extension.json`. - This is not confirmed on Windows yet; I asked the reporter for their clone output. - Workaround: clone with `core.symlinks=false` and install from the folder. **Tested** with Gemini CLI 0.62 on Linux: - The URL install works. - A `core.symlinks=false` clone installs from its folder after the trust prompt. All skills (from the extension's `skills/`), `AGENTS.md` and the fal MCP server load. - The only noise is a non-fatal "Failed to discover skills: ENOTDIR … .gemini/skills". **Follow-ups to consider (not in this PR):** - Drop the `.gemini/skills` and `GEMINI.md` symlinks. The extension already loads `skills/` and `AGENTS.md` (`contextFileName`) by itself; Gemini started inside a clone would then need a `.gemini/settings.json` instead. - Or publish releases with a packaged extension zip as an asset, so Gemini CLI never clones. Refs #13 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 20:53:18 +00:00