Devotd Github
NewAI agents

the-aie/the-gibson — Fix to the repository boundary guard with linked worktree support

The latest commit 4981b4f of the-aie/the-gibson fixes the repository boundary guard script so that it allows linked worktrees of the same repository while blocking Git environment variable manipulation that reaches across into other repositories or storage locations with rejection code 86.

Repositorythe-aie/the-gibson ↗

The latest commit 4981b4f of the-aie/the-gibson fixes the repository boundary guard script so that it allows linked worktrees of the same repository while blocking Git environment variable manipulation that reaches across into other repositories or storage locations with rejection code 86.

GitHub description: A portable, self-improving SDLC harness for agent fleets — plan → issues → build → test → review → UX-eval → security → ship, on any runtime (Claude Code, Codex, Grok, Hermes). Apache-2.0.

stars
★ 41
Forks
7
Language
Shell
License
Apache-2.0
Read original source ↗View on GitHub ↗

the-aie/the-gibson is a harness that weaves multiple coding agents together (agent fleet) into a single software development lifecycle (software development lifecycle, SDLC) procedure as if they were one team. The repository description states that it is a self-improving harness, and the license is Apache-2.0. The plan defines everything from issue creation, build, test, review, UX evaluation, security check, through deployment as one single flow. The latest commit 4981b4f (2026-11-04 07:57 UTC) is a change that fixes the repository boundary guard script of this harness, scripts/repo-boundary-guard.sh. The entire change is 992 lines, with 975 added lines and 17 deleted lines split between scripts/repo-boundary-guard.sh and the test file scripts/tests/repo-boundary-guard.test.sh.

This script is the gatekeeper that prevents the agent from touching anything outside the designated repository. This commit also recognizes linked worktrees (separate checkouts of the same repository) that share the target repository and the Git common directory as being inside the boundary. On the other hand, if environment variables such as GIT_DIR, GIT_WORK_TREE, GIT_INDEX_FILE, or GIT_OBJECT_DIRECTORY point to another repository or storage location, it aborts with rejection code 86. The commit message states that it blocked overrides that slip another repository in and early global options that bypass protected behavior, maintained control plane protection, and added regression tests that cover the actual effects together with fixtures for failure diagnostics.

However, what this commit touched is only the script and its test file, two files in total. No results from running the whole harness and no performance figures are given, and how the agent handles the 86 signal after the guard halts cannot be known from this commit alone. The shape of the boundary rule has become clear, but its actual effect on the working flow remains to be observed further.