jfrog / jfrog/boost

boost init --codex writes the BoostGraph MCP server as "boostgraphgraph" with a bare "boost" command; Codex cannot start it (v0.13.14)

Open
#80 0 comments 0 reactions 1 assignee View on GitHub

@menachemm-byte is already working on this.

Since Sep 10, 2026.

Dominant language
Shell
Stars
500
Forks
20
Avg merge
55m
Merged PRs (30d)
6

Description

On Windows, with boost-graph-integration enabled, boost init --codex appends this to ~/.codex/config.toml:

[mcp_servers.boostgraphgraph]
command = "boost"
args = ["graph", "serve", "--mcp"]

Codex then prints on every start:

MCP client for `boostgraphgraph` failed to start: MCP startup failed: program not found
MCP startup incomplete (failed: boostgraphgraph)

Three bugs in one write:

  1. Name doubled. The key should be boostgraph; the subcommand looks appended to it. The --claude target writes boostgraph correctly, so this is the Codex writer only. It also breaks the tool prefix: the AGENTS.md Boost installs alongside it tells the agent to call boostgraph_explore under mcp__boostgraph__.

  2. command = "boost" does not resolve. %LOCALAPPDATA%\boost\bin is on the user PATH but holds only boost.exe, and Codex appears not to apply PATHEXT when spawning an MCP server. The absolute path works: an older [mcp_servers.boostgraph] entry in the same file points at ...\bin\boost.exe and starts fine. Boost writes that absolute path elsewhere already, e.g. $env:BOOST_EXE in ~/.codex/hooks/boost-hook-codex.ps1.

  3. Appends instead of reconciling. An existing [mcp_servers.boostgraph] block is left alone and the new one lands at EOF, so two BoostGraph servers end up configured. %LOCALAPPDATA%\boost\boostgraph-managed.json lists the codex target three times across upgrades, so the bookkeeping is not idempotent either.

Repro: run boost init --codex --boostgraph on Windows with the flag on and read ~/.codex/config.toml. Against a throwaway home (git bash):

mkdir -p /tmp/fh/.codex /tmp/fh/.boost
printf 'model = "gpt-5"\n' > /tmp/fh/.codex/config.toml
cp ~/.boost/config.toml /tmp/fh/.boost/config.toml   # boost-graph-integration = true
HOME=/tmp/fh USERPROFILE='C:\tmp\fh' HOMEDRIVE=C: HOMEPATH='\tmp\fh' \
  CODEX_HOME='C:\tmp\fh\.codex' boost init --codex --boostgraph --accept-terms

Expected: a single [mcp_servers.boostgraph] entry with the absolute boost.exe path, updated in place on reinstall.

boost v0.13.14, Windows 11, Codex CLI.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.