Repository navigation
Releases
agents-infra 2.4.0
Version bump 2.3.1 → 2.4.0 (minor): cmux config features plus the titlebar unread badge toggle.
- cmux remote tmux mirroring is on by default: mirroring, new-workspace-on-host, origin colors and host titles, plus the shared-connection multiplexer (#285).
- New
newLocalTmuxWorkspaceaction bound tocmd+shift+t; one session per directory, named from the directory plus a short path hash (#286, #287). - New
openRemoteTmuxaction bound tocmd+shift+opt+t(cmux ssh-tmux mac-mini) (#288). - The mirrored cmux config turns off the titlebar bell unread count badge (
notifications.titlebarBadge=false, supported from cmux 0.65.2.2-r29). Sidebar unread badges, the notifications panel, desktop banners and sound are unchanged (#292). VERSIONand both README version badges are now 2.4.0.
agents-infra 2.3.1
Publishing moves back to the authoring MacBook. agents-infra is now synced and merged from this machine only.
Why: the mirror was published from the Mac mini. On 2026-11-16 another session over there ran publish.py on its own schedule, producing several duplicate mirror PRs and a duplicate release; two pushers on two machines keep generating redundant work. The Mac mini no longer holds a copy of this repository.
What changed:
publish.py: the hostname gate is inverted — it no longer requires the Mac mini, and now refuses to run on the Mac mini.- Docs updated to the single-publisher-on-the-MacBook model:
patch/agents-infra-publish/README.md,docs/capability-sync.md,docs/macmini-mirror.md, globalAGENTS.md. - This repository's own docs:
README/AGENTS/ the project-level pi rules now say the MacBook publishes, and "no local clone on this machine" became "a local clone is required" (it is the only publisher and the place whereapps/publish.shcollects the app-config mirrors). patch/skill-custom/conflicts/added to the publish excludes — a runtime directory that is permanently empty, so syncing it only produced a permanent phantom diff.- Version
2.3.0→2.3.1.
Regression risk: low. The publish mechanism is unchanged (rsync → CHANGELOG → branch → PR → auto-merge); Syncthing convergence checks were verified working from this machine; the only behavioural change is that publishing from the Mac mini is now refused, which is the intent.
agents-infra 2.3.0
apps/ stops being a symlink target. The config file in your home directory is now the source of truth; the copy in this repository is a mirror.
Why: the previous setup symlinked ~/.config/{ghostty,cmux} into the repo, so there was exactly one copy. That holds until an app writes atomically — writing a temp file and renaming it over the target — which silently replaces the symlink with a regular file. From that moment the repo tracks nothing and git status still looks clean. A plain live file cannot fail that way.
What changed:
install.shreversed: now mirror → system (one-shot deploy withcp, no symlinks; a leftover symlink is replaced by a real file; a differing file is backed up as.bak.<timestamp>first). Still idempotent.publish.sh(new): system → mirror — collects the live files, refreshes the UserDefaults snapshot, runs the secret gate.scripts/check-secrets.py(new): publishing aborts on any non-emptypassword/token/secret/apiKeyfield (includingcmux.json'ssocketPassword); also runs gitleaks when available.check.sh: compares both sides — a missing file or a leftover symlink fails, "changed on disk but not published" is reported.export-defaults.shremoved; its job is part ofpublish.sh.- Docs rewritten to the mirror model:
mappings.conf, bothapps/READMEfiles, theghostty/andcmux/directory notes, the managed-path comments in the two config files, rootREADMEandAGENTS.md. - Version
2.2.0→2.3.0.
Regression risk: none. The live configs did not change (the three files on the authoring machine went from symlinks to real files with only comment-level differences); the pi/agent/ mirror pipeline is untouched; cmux.json keeps mode 600 — now applied to the live file by install.sh.
agents-infra 2.2.0
Add apps/: migrate the dotfiles repo's app configs into this repo as infrastructure.
Why: ghostty and cmux are the terminals every agent session runs in — a wrong config breaks every agent at once. They are infrastructure, not a side repo maintained by a separate pipeline; keeping them in agents-infra means the full picture of "what the fleet runs on" lives in a single repo.
What changed:
- New top-level
apps/, hand-maintained (not generated bypublish.py):ghostty/{config,README.md},cmux/{cmux.json,config.ghostty,defaults.plist,README.md},mappings.conf,install.sh,check.sh,export-defaults.sh,scripts/{apply-defaults,export-defaults}.py, plusREADME.md/README_cn.md(rewritten from the dotfiles root docs). - Managed paths in config comments changed from
~/Developer/dotfiles/...to~/Developer/agents-infra/apps/...; a duplicated managed-path note inghostty/configwas removed. check.sh's git-status check narrowed to this directory: it previously covered the whole repo and reported pendingpi/agent/mirror changes as uncommitted app configs.- Root
README.md/README_cn.mdgained anapps/row and a "mirror vs live config" distinction;AGENTS.mddocuments the two halves;.gitignoreadds*.bak.*(backups produced byinstall.sh). - Version
2.1.0→2.2.0(new content is a minor-level change).
Regression risk: none. The pi/agent/ mirror pipeline is untouched (publish.py only rsyncs pi/agent/, never apps/); install.sh / check.sh still resolve their root from the script location, and the symlink mechanism, the UserDefaults snapshot whitelist, and cmux.json's 600 permissions are unchanged.
v2.1.0 — 更名 TeamToolkit → agents-infra
本项目是智能体团队通用能力底座的开源镜像:仓库里的 pi/agent/ 逐字节镜像全局 ~/.pi/agent/(规则、技能、pi 扩展、辅助脚本、参考文档、第三方包清单)。
这一版只做一件事:改名。
原名 TeamToolkit 读起来像某个 agent 的专属工具箱,看不出它是全队 17 个 agent 共用的基础设施;现名 agents-infra 把「agent 们的基础设施」直接写进名字。
变更
- GitHub 仓库
xhqing/TeamToolkit→xhqing/agents-infra(旧地址由 GitHub 自动重定向) - 发布机 clone 目录改为
~/Developer/agents-infra,发布脚本路径改为patch/agents-infra-publish/publish.py - 双语 README:标题、类型徽章(
Type-Team Toolkit→Type-Agents Infra)、示意图路径、clone 指令、正文自称全部换新,并补三段名字的沿革(CapabilityManagerAgent→TeamToolkit→agents-infra) pi/agent/镜像内容同步此前的全局改动(规则、文档、扩展、技能一并更新)
兼容性
- 旧 URL 与旧
git remote由 GitHub 重定向,clone / fetch 不受影响 patch/npm-manifest/refresh.py的环境变量TEAM_TOOLKIT_DIR改名为AGENTS_INFRA_DIR(本机工具,无外部使用者)
说明
本项目不构建发布产物,源码即产物(clone 后 pi/agent/ 直接可读可用)。
TeamToolkit v2.0.0
更名 + 降级为普通项目
本项目原为 CapabilityManagerAgent(由 Prometheus 角色维护),现更名为 TeamToolkit,退化为普通项目(归 Kit 负责),不再作为智能体维护。
变化
- 仓库与目录改名:
CapabilityManagerAgent→TeamToolkit(旧 URL 自动重定向) - README 双语重写:去掉智能体人设,改为「团队共享工具箱」的说明;类型徽章改为
Team Toolkit - 发布改为单 pusher:由
patch/team-toolkit-publish/publish.py在单一设备上单向生成镜像 → 提交 → PR → 自动合并 - npm 清单不由发布机生成:
~/.pi/agent/npm是架构相关目录、两机版本可能不同,清单只在装了包的机器上生成后随内容提交 - 版本号 1.14.0 → 2.0.0(身份变化)
兼容性
镜像内容(pi/agent/ 下的规则 / 技能 / 扩展 / 脚本 / 文档)结构不变,只是仓库名与发布通道变化。
CapabilityManagerAgent 1.14.0
Finalize the macmini migration: retire the git read-only guard and settle on two shared directories.
Read-only guard retired
- Deleted
extensions/git-readonly-guard.ts. Its premise (a.gitshared through Syncthing) no longer exists: each machine now has its own clone, so every machine follows the same rules - remote main stays locked, changes go through branches, PRs and CI. - The
core.hooksPathread-only hook on macmini was cleared as well.
Migration wrap-up
~/Developeris no longer synced. macmini's 38 repositories were adopted in place (fetch --prune+reset --hard origin/<branch>, dependencies preserved, no 7.7 GB re-download) and 10 broken worktree remnants were removed.- GitHub access on macmini works again over HTTPS + gh token: 34 SSH remotes were rewritten to
https://github.com/xhqing/<repo>.git, and no SSH private key was copied to macmini.
Docs and scripts
CLAUDE.md: macmini git permission entry now records the removal (2026-11-05) instead of a future plan.docs/macmini-mirror.md: the transition section is marked complete; credentials documented as the final HTTPS + token setup.skills/macmini-use/SKILL.md: commit / push / PR / Release are allowed on both machines; GitHub connectivity and failure-mode rows updated (rate limit / expired credentials instead of read-only).patch/macmini-use/README.md: macmini repositories are independent clones with normal git read/write.patch/macmini-git-readonly/README.md: retired banner, kept as historical reference.patch/macmini-mirror/setup.py: the developer share is created only with--with-developer;drop_folder()now usesDELETE /rest/config/folders/<id>and goes throughapi()so remote requests travel over ssh + curl (using the remote API key against the local endpoint returns 403).
CapabilityManagerAgent 1.13.2
Second follow-up for the pre-change snapshot tool: stabilize fingerprints across machines and fix lark-cli discovery on macmini.
Machine-local configuration excluded from fingerprints
anysearchruntime config,session-linkruntime json files,trust.jsonandmcp-project-approvals.jsonare maintained per machine and never synced, so they made the private-directory fingerprint differ between hosts (and leaked local paths into the backup).PI_AGENT_EXCLUDESnow lists them alongside the Syncthing metadata already excluded.
lark-cli discovery
- Non-interactive shells (
ssh mac-mini '...') do not have~/.local/binin PATH, so callinglark-clidirectly raisedFileNotFoundError. - Added
_lark_bin(): resolves throughshutil.which,~/.local/bin,~/bin, and the two Homebrew prefixes; all Feishu calls use the resolved path.
Docs
- README now documents the per-machine setup (lark-cli location, separate Feishu apps per host, one shared backup root folder), the two classes of paths that must stay out of the fingerprint with a two-host verification command, and the macmini github.com rate-limit workaround (download locally, then scp).
CapabilityManagerAgent 1.13.1
Fix unstable snapshot fingerprints for the private shared directory.
Snapshot fingerprints now exclude Syncthing-local metadata
- The pre-change snapshot mechanism relies on a content fingerprint to decide whether a snapshot is fresh and whether a deletion still matches the current state.
- Syncthing-local files (
.stignore/.stfolder) and machine-localnode_modulesdiffer between hosts, so identical logical content produced different fingerprints and the other machine rejected an otherwise valid snapshot. _private_excluded()now skips.stignore*,.stfolderandnode_modules/at any depth, with a comment explaining why those paths must stay out of the fingerprint.
CapabilityManagerAgent 1.13.0
Cross-machine architecture redesign plus the follow-up mirror updates and fixes since v1.12.0.
Cross-machine architecture: code via GitHub, only two shared directories on Syncthing
- Abandoned the full
~/DeveloperSyncthing mirror; each machine clones the repositories and exchanges code through GitHub (push -> PR -> CI -> merge -> fast-forward local main). - Syncthing now syncs only two directories: the private-content store and the global capability layer.
- Added
patch/private-links/: keeps private, gitignored content outside the repository and links it in (adopt / materialize / check / restore), including.git/info/excludemaintenance. - Added
patch/dev-snapshots/: pre-change snapshots of the two shared directories (tar.gz, local + Feishu, five most recent copies, token shared across machines). - Added
extensions/snapshot-guard.ts: blocks writes without a fresh snapshot (30 minutes) and deletions without an identical snapshot; deleting either shared root is always denied. - Rewrote the macmini deletion red line, sync scope and git-permission sections: project directories are ordinary clones, the two shared directories are the protected ones, and macmini returns to normal read-write git once the old
~/Developershare is removed.
Extension syntax guard
- Added
extensions/ts-syntax-guard.tsandpatch/ts-syntax-check/check.mjs: validate extension code with the same parser pi uses (stripTypeScriptTypes) before it is written, and re-check files touched through shell redirection. A single parse error makes pi exit with code 1 and takes every session down.
Macmini usage
gh issueis now allowed on macmini (GitHub-side objects, no local.git), whilegh workflow runis now blocked as well.- Added an editor status indicator showing when the current call is running on macmini.
add-mode/commit-modeare always off onmainand can only be turned off there.- Fixed add / commit auto-triggering inside AI-created worktrees (
git -C <worktree>handling).
Rules and docs
- New rule: currency symbols must be explicit -
US$/USDfor US dollars,HK$/HKDfor Hong Kong dollars, never a bare$. - Removed the visitor-count badge from READMEs after the central traffic collection was shut down, and dropped the corresponding exception from the commit skill.
- Recorded that macmini
ghis authenticated (credentials stay machine-local and are not mirrored). - Removed the obsolete
xhqingtraffic.ymlnote from the branch-protection reference.
npm manifest
- Refreshed the pi package manifest (
pi-mcp-adapter7.0.0 -> 7.0.1).