DEV Community

Cover image for Coding Agents Shouldn’t Have Your Git Credentials
Trent Seed
Trent Seed

Posted on Originally published at Medium

Coding Agents Shouldn’t Have Your Git Credentials

Why I built and open-sourced GitSeed to run cloud and local coding agents in one governed pipeline.

First, I had both cloud frontier models and local GPU models (Ollama and vLLM), and getting them to work together coherently was duct tape — frontier models were great at shaping specs and catching subtle bugs in review, while local or cost-capped models were ideal for implementation, yet nothing connected them into one auditable flow.

Second, I looked at four coding agents running in parallel across local worktrees on my machine and realized every single one could push straight to main and read ~/.ssh, ~/.aws, and my browser profile while doing it.

I wanted a streamlined pipeline where I could feed a rough idea or bugfix in from anywhere — whether at my terminal, speaking a quick note into my watch, or reviewing a gate on my phone — and let cloud and local agents move it toward a pull request safely on infrastructure I control.

Today I’m open-sourcing the GitSeed platform under Apache 2.0: gitseed.dev | github.com/gitseed-dev/gitseed.

Untrusted Agent, Trusted 3-Phase Broker
GitSeed models every change as a Seed moving through Ideate → Plan → Execute → Review → Merge. For targeted or quick changes, you may Fast-Track with Execute → Review → Merge.

Instead of putting repository code and Git push tokens inside the same container as the LLM, every stage splits into three container phases behind docker-socket-proxy and an SSRF-guarded egress-proxy:

  • prepare: Clones repositories, neutralizes executable .git/config directives and .git/hooks, strips Git tokens, and exits before the agent starts.
  • agent (Untrusted): Runs Claude Code, Codex, Gemini CLI, OpenCode, Antigravity, or Grok Build non-root (CapDrop: ALL) with zero Git credentials.
  • finalize (Trusted Broker): Starts only after agent stops, mounts /workspace read-only, enforces blocked_paths (including symlink target checks so .github/workflows/** cannot be altered indirectly), scans added lines for secrets, and commits/pushes from a clean /tmp .git directory.

Cloud + Local Models, Signed Receipts & Live Rescue

  • Frontier Specs, Flexible Execution: Dispatch up to three models in parallel for Second Opinions on Ideate, Plan, or Review (where a blocking fail verdict cannot be silently bypassed). Then route Execute through LiteLLM API keys with hard USD caps (enforced spend), local Ollama/vLLM GPUs with no external model API traffic, or opt-in single-user Personal Mode (estimated spend; owner-bound — you’re responsible for your provider’s subscription terms, and teams should use API keys).
  • Ed25519 Governance Receipts (gitseed.receipt.v1): Every PR gets a cryptographically signed receipt attesting to the locked spec hash, models used, trusted broker checks, spend mode, and human approvals — verifiable via gitseed receipt verify #14.
  • Seamless Continuity & Rescue: Approve stage gates from mobile or desktop, steer live sessions via @agent PR comments, auto-remediate failing CI, sync directly with Local Folders on disk, or drop into any running sandbox via browser terminal or embedded VS Code.

What GitSeed Doesn’t Protect Against

  • Bad logic in allowed source files: finalize blocks protected paths and leaked secrets, not buggy or backdoored code in src/—code review remains the defense there.
  • Outbound context to your model provider: Agents send prompts and code snippets to whichever inference endpoint you configure.
  • Hard dollar cutoffs in Personal Mode: Subscription CLIs talk directly to vendor endpoints, so spend is estimated and bounded by timeouts and --max-turns rather than a proxy dollar cap.

Try It Locally
Quickstart builds locally in ~2–3 minutes so vendor CLIs install from upstream rather than being redistributed in public images:

git clone https://github.com/gitseed-dev/gitseed && cd gitseed
./scripts/init.sh # (generates fail-closed secrets; Windows: .\scripts\init.ps1)
docker compose up -d --build
Enter fullscreen mode Exit fullscreen mode

Open http://localhost:8421 and login with the admin details found in your generated .env file from init.sh.

Repo & overview: github.com/gitseed-dev/gitseed | gitseed.dev

Top comments (0)