Skip to content

v7.1.0 — Cross-repo agent coordination

Latest
Latest

Choose a tag to compare

View all tags
@NagyVikt NagyVikt released this 05 Jun 15:26
· 10 commits to main since this release
v7.1.0
c4627e0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

gitguardex 7.1.0 — Cross-repo agent coordination

This release turns gitguardex from a single-repo branch guard into a cross-repo
agent coordination layer: agents can now see who is working on what across all
your repos, ad-hoc branch names just work, and routine flows stop burning context
tokens. All default changes are backward-compatible and overridable.

✨ Highlights

gx mcp — a read-only, cross-repo agent radar (new).
A dependency-free MCP server so any agent (Claude Code, Codex) can answer "who is
working on what, and is anyone else editing this file?" before it starts. Tools:

  • list_agents — every active lane across all discovered repos: branch, worktree,
    task, dirty files (live, uncommitted edits), held file locks, last commit,
    age, and the PR it is shipping.
  • who_owns(file) — which agent/branch holds the lock on a path (aggregated across
    all worktrees), for a real collision check before editing.
  • repo_state(repo) and my_context — per-repo and current-session views.
  • Warns when a lane is editing the protected primary checkout (the classic
    "my changes got auto-stashed" trap), and flags stale lanes (old, no open PR,
    clean — safe to prune).

Turn it on per repo automatically: gx claude install now writes a .mcp.json
registering the server (opt out with --no-mcp). Or globally:
claude mcp add gx -s user -- gx mcp serve.

Any non-protected branch is agent-managed.
vendor/*, feat/*, or any ad-hoc name now edits and commits cleanly — being
off a protected base (main/dev/master) is the only load-bearing rule.
Lockdown is still available via GUARDEX_AGENT_BRANCH_PREFIXES_ONLY=1 and
GUARDEX_REQUIRE_AGENT_BRANCH=1.

Leaner defaults, fewer tokens.

  • gx branch start defaults to tier T1 (notes-only scaffold) instead of T3
    (full plan workspace), saving thousands of tokens on small changes. Escalate
    with --tier T2/T3; gx merge integration lanes stay T3.
  • The protected-branch advisor now shows its full guidance once per session
    and a one-line reminder thereafter, instead of repeating on every prompt.
  • gx branch finish preflight is quiet by default (summary on pass, failure
    tail on fail) instead of streaming hundreds of lines of passing test output.
    Restore full output with GUARDEX_PREFLIGHT_VERBOSE=1.

🚀 Features

  • gx mcp server + tools, batch PR correlation (one gh call per repo), stale-lane
    detection and prLookupError (distinguishes a failed PR lookup from "no PR"). (#628, #630, #633)
  • gx claude install auto-registers the gx MCP server in .mcp.json; check/doctor/uninstall cover it. (#629)
  • Any non-protected branch treated as agent-managed, with opt-in lockdown knobs. (#626)
  • Default gx branch start tier T1 with an escalation hint. (#632)

⚡ Performance / token efficiency

  • Protected-branch advisor de-duplicated to once-per-session. (#627)
  • Preflight quiet by default. (#631)

🐛 Fixes

  • Preflight: a single failing check no longer falsely passes ("No recognized
    project stack detected" exit-0 path). (#631)
  • MCP: protocol-version pinning, bounded git/gh calls so a hung lookup can't
    exceed the client timeout, and cross-worktree lock aggregation. (#628, #630)

📦 Install / upgrade

npm i -g @imdeadpool/guardex@7.1.0

Full changelog: v7.0.42...v7.1.0

Assets 2
Loading