Releases: opencue/gitguardex
v7.1.0 — Cross-repo agent coordination
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)andmy_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 startdefaults 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 mergeintegration 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 finishpreflight is quiet by default (summary on pass, failure
tail on fail) instead of streaming hundreds of lines of passing test output.
Restore full output withGUARDEX_PREFLIGHT_VERBOSE=1.
🚀 Features
gx mcpserver + tools, batch PR correlation (oneghcall per repo), stale-lane
detection andprLookupError(distinguishes a failed PR lookup from "no PR"). (#628, #630, #633)gx claude installauto-registers the gx MCP server in.mcp.json;check/doctor/uninstallcover it. (#629)- Any non-protected branch treated as agent-managed, with opt-in lockdown knobs. (#626)
- Default
gx branch starttier 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/ghcalls 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
v7.0.42
GitGuardex v7.0.42
Changes since v7.0.41.
v7.0.42
- Bumped
@imdeadpool/guardexfrom7.0.41to7.0.42so the current
mainpayload can publish under a fresh npm version after7.0.41reached
the registry. - Improves the agent-session and cockpit workflow:
gx agents start/status
now share canonical session storage, agent lanes can be previewed, claimed,
finished by session, and launched through safer supported-agent metadata,
and cockpit can render live session state through tmux-backed panes. - Hardens setup and status hygiene by ignoring local
.codex/state during
setup/doctor, avoiding generic OpenSpec dirty-worktree reuse, and pruning
stale agent sessions from user-facing status surfaces.
v7.0.41
v7.0.41
- Bumped
@imdeadpool/guardexfrom7.0.40to7.0.41so the currentmainpayload can publish under a fresh npm version after thev7.0.40GitHub release landed without a matching npm registry package. - Ships the Colony companion setup as the default global companion surface:
colonymaps to@imdeadpool/colony-cli, README setup documentscolony install --ide ..., and status tests/images expect Colony instead of cavemem.
Publish from the merged commit with:
npm publish --access public
v7.0.40
GitGuardex v7.0.40
Changes since v7.0.39.
v7.0.40
- Bumped
@imdeadpool/guardexfrom7.0.39to7.0.40so the current
mainpayload can publish under a fresh npm version after7.0.39reached
the registry. - No new CLI command behavior is introduced in this release lane.
v7.0.39
v7.0.38
v7.0.37
GitGuardex v7.0.37
Changes since v7.0.35.
v7.0.37
- Bumped
@imdeadpool/guardexfrom7.0.36to7.0.37so the current
package can publish under a fresh npm version after7.0.36reached the
registry. - Synced the shipped Active Agents template with the canonical VS Code
extension source so Colony task counts and details install with the package. - No new CLI command behavior is introduced in this release lane.
v7.0.36
- Bumped
@imdeadpool/guardexfrom7.0.35to7.0.36so the latest
branch-finish cwd-prune fix can ship under a fresh npm version after PR #424. - No new CLI command surface is introduced in this release lane.
v7.0.35
GitGuardex v7.0.35
Changes since v7.0.34.
v7.0.35
- Bumped
@imdeadpool/guardexfrom7.0.34to7.0.35so the current
mergedmainpayload can publish on a fresh npm version after PR #420. - Refreshed README release/skills metadata and shipped Active Agents template
parity so the currentmainpayload passes release verification. - No new CLI command behavior is introduced in this release lane.
v7.0.34
Highlights
- Fix: primary-checkout branch-flip guard now survives a dirty tree. The
templates/githooks/post-checkouthook auto-stashes dirty edits asguardex-auto-revert <ts> <prev>-><new>(including untracked files) before reverting primary to the protected branch. Previously a dirty tree caused the guard to printauto-revert skippedand silently leave primary flipped onto anagent/*branch — the exact symptom where localmainappeared to become the agent worktree branch. (#417) - Contract tightening in
AGENTS.md/CLAUDE.md: new explicitPrimary-tree lock (blocking)rule enumerating every disallowed command on the primary checkout (git checkout <ref>,git switch <ref>,git switch -c ...,git checkout -b ...,git worktree add <path> <existing-agent-branch>), plus aDirty-tree rulepointing at the new auto-stash safety net. (#417)
Changes
- chore(release): bump to 7.0.34 (#418)
- fix(guardex): auto-stash dirty primary on branch-switch (#417)
Full Changelog: v7.0.33...v7.0.34
v7.0.33
What's Changed
- Reduce launch tax when bare gx finds drift by @NagyVikt in #400
- feat(vscode-active-agents): distinct icons per tree section by @NagyVikt in #402
- feat(vscode-active-agents): refine file-icon SVGs by @NagyVikt in #403
- docs(AGENTS): make Claude finish always include via-pr + wait-for-merge + cleanup by @NagyVikt in #404
- Default Active Agents tree toward raw details view by @NagyVikt in #401
- Let gx doctor auto-finish agent branches without a GitHub remote by @NagyVikt in #405
- feat(worktree): prefix worktree leaves with repo basename instead of literal 'agent' by @NagyVikt in #406
- Group gx help commands + quickstart and bump to 7.0.28 by @NagyVikt in #408
- Show green check when agent finished editing worktree by @NagyVikt in #407
- Compact gx status banner with context-aware next-step hint by @NagyVikt in #409
- Default auto-doctor to --current so bare gx stays in this repo by @NagyVikt in #410
- Prompt on bare gx to install missing companion tools by @NagyVikt in #411
- Rewrite README against Claude Design handoff (929 -> 248 lines) by @NagyVikt in #412
- README: add back hero/problem/workflow images + companion tools table by @NagyVikt in #413
Full Changelog: v7.0.27...v7.0.33