Skip to content

fix(gemini): seed registry-shaped projects.json on startup #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Joseph19820124 wants to merge 4 commits into from
Closed

fix(gemini): seed registry-shaped projects.json on startup #390

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
598ed46
docs: add gemini first-run workaround
Joseph19820124 Apr 14, 2026
b44d027
docs: expand gemini workaround guidance
Joseph19820124 Apr 14, 2026
f779a4b
fix(gemini): initialize project registry on startup
Joseph19820124 Apr 16, 2026
492a166
docs(gemini): narrow first-run workaround guidance
Joseph19820124 Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/gemini.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,26 @@ helm install openab openab/openab \

> Set `agents.kiro.enabled=false` to disable the default Kiro agent.

## First-Run Workaround

Gemini CLI needs `~/.gemini/projects.json` to exist before the first ACP session starts. In ephemeral containers, the file may not be created yet, which can surface as `ENOENT`, `Unexpected end of JSON input`, or a `ProjectRegistry` startup failure during the first run.

This is a workaround for the upstream Gemini CLI issue: [google-gemini/gemini-cli#25509](https://github.com/google-gemini/gemini-cli/issues/25509).

If you control the Gemini container startup command, seed the directory before launching `openab`:

```json
{"projects":{}}
```

```bash
mkdir -p /home/node/.gemini && printf '{"projects":{}}\n' > /home/node/.gemini/projects.json && exec openab /etc/openab/config.toml
```

The `exec openab /etc/openab/config.toml` part assumes the Docker image default config path.

For Kubernetes or Helm deployments, use the same idea with an init container and a shared volume mounted at `/home/node/.gemini`, or wait for the Gemini CLI fix upstream.

## Manual config.toml

```toml
Expand Down
Loading