`-i` / `--init` flag to `install` command? Or self-contained MCP server?

[ftzi]

Hi, instead of two separate long commands, could we have -i / --init to the bunx @colbymchenry/codegraph install command so we can do all in one?

OR

Couldn't we have everything baked inside

[mcp_servers.codegraph]
command = "codegraph"
args = ["serve", "--mcp"]

with a flag to do it all at once?

My use case is that I spawn each AI session in a fresh new container - but this container should be generic enough, as I am doing a tool like Opencode Desktop (still private, will be public soon). I don't want codegraph to be baked in by default (at least for now) as this could end up making it bloated.

[ftzi]

Wait, this seems to work so no PATH is required?

[mcp_servers.codegraph]
command = "bunx"
args = ["@colbymchenry/codegraph", "serve", "--mcp"]

Still lacks installation beforehand.

The issue with PATH is that the install --yes skips PATH setup.

[colbymchenry]

Thanks — this is a reasonable ask, and your second comment found the right shape for the server half, so let me answer both halves.

The MCP entry. Yes: command = "bunx", args = ["@colbymchenry/codegraph", "serve", "--mcp"] is fully self-contained — nothing needs to be on PATH. (Same with npx -y.) That's the form to bake into a generic container.

Why install --yes skipped PATH setup. By design, not an oversight: --yes is the scripted/upgrade path, and the one thing it assumes is that the CLI is already present — it won't run npm install -g for you. In a fresh container that assumption is false, which is what you hit. Either install it first (npm i -g @colbymchenry/codegraph) or skip install entirely and use the bunx entry above.

The index. That's the part that was genuinely missing a one-shot path, so #1595 adds two things:

• codegraph install --init — wires agents and then runs init in the current directory, in one command. It's explicit on purpose: the installer never indexes implicitly (an accidental index of $HOME is the thing we refuse), so the flag is you choosing. It shares every guard with init (an unsafe root is refused, an already-initialized project just says so) and also runs when --target none.
• codegraph init --yes — non-interactive: every post-index offer takes its default instead of prompting, so a container/CI bootstrap can't block on a question.

So the unattended bootstrap becomes npm i -g @colbymchenry/codegraph && codegraph install --yes --init, or — with the bunx MCP entry and no install at all — just bunx @colbymchenry/codegraph init --yes in the project directory before the session starts. Ships in the next release.

[ftzi]

Wonderful!!!! Thank you so much!