Found by the code and security reviewers during #217.
Problem
make build produces ./databricks-agents (the multiplexer, #203/#213), but .gitignore lists only:
/databricks
/databricks-claude
/databricks-codex
/databricks-opencode
/databricks does not match databricks-agents — gitignore patterns are exact, not prefixes. git check-ignore -v databricks-agents confirms it is NOT ignored, so the compiled binary sits untracked in any worktree where make build has run.
Why it matters
One git add -A commits a multi-MB, locally-built, unreviewed binary into a repo that is itself a software distribution channel. That is a supply-chain-shaped accident waiting for a distracted moment.
Fix
Add /databricks-agents to .gitignore. Pre-existing gap from the #203 fold-in — the other three launchers were ignored, this one was missed when it was added.
Deliberately kept out of #217 to preserve that PR's scope.
Found by the code and security reviewers during #217.
Problem
make buildproduces./databricks-agents(the multiplexer, #203/#213), but.gitignorelists only:/databricksdoes not matchdatabricks-agents— gitignore patterns are exact, not prefixes.git check-ignore -v databricks-agentsconfirms it is NOT ignored, so the compiled binary sits untracked in any worktree wheremake buildhas run.Why it matters
One
git add -Acommits a multi-MB, locally-built, unreviewed binary into a repo that is itself a software distribution channel. That is a supply-chain-shaped accident waiting for a distracted moment.Fix
Add
/databricks-agentsto.gitignore. Pre-existing gap from the #203 fold-in — the other three launchers were ignored, this one was missed when it was added.Deliberately kept out of #217 to preserve that PR's scope.