sandboxed-agent-git-relay

Publish sandboxed agent commits to GitHub via a host-side relay.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/okayus/okayus-skills --skill sandboxed-agent-git-relay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sandboxed-agent-git-relay
Source: https://github.com/okayus/okayus-skills/tree/main/skills/sandboxed-agent-git-relay
Command: npx skills add https://github.com/okayus/okayus-skills --skill sandboxed-agent-git-relay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the security challenge of allowing sandboxed coding agents to create GitHub branches and pull requests without exposing credentials or granting direct repository write access inside the sandbox.

Core Features & Use Cases

  • Credential-Free Agent Delivery: Uses a host-side relay with GitHub App tokens to push agent commits and create pull requests while keeping secrets outside the sandbox boundary.
  • Controlled Merge Automation: Supports explicit commit-trailer based merge delegation with server-side CI safeguards and protection against squash-merge replay loops.
  • Use Case: Enable an autonomous Claude Code workflow in a Docker sandbox where the agent can commit changes, while a host service safely handles GitHub publishing and optional merging.

Quick Start

Use the sandboxed-agent-git-relay skill to configure a host-side GitHub App relay that publishes agent-created branches as pull requests without storing credentials in the container.

Frequently Asked Questions about sandboxed-agent-git-relay

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let a sandboxed coding agent create GitHub pull requests without exposing credentials inside the container?

A host-side git relay uses GitHub App authentication to publish agent-created branches as pull requests, keeping credentials isolated outside the Docker sandbox boundary. The relay handles GitHub publishing autonomously while the agent remains credential-free.

What is the best way to automate merging pull requests from autonomous agent workflows while preventing squash-merge replay loops?

Controlled merge automation uses explicit commit-trailer based delegation with server-side CI safeguards to prevent squash-merge replay loops. This ensures autonomous agent merge requests are validated and safely executed through the host-side relay.

Can I use a Docker sandbox workflow with systemd scheduling to autonomously push agent commits to GitHub?

Yes, the host-side relay automation supports systemd scheduling for reliable autonomous delivery of agent commits to GitHub. The Docker sandbox handles agent execution while systemd ensures the relay consistently publishes changes as pull requests.

Does the git relay approach require branch policy enforcement on GitHub repositories for autonomous agent changes?

Yes, branch policy enforcement is required alongside GitHub App authentication to safely ship agent changes. This combination ensures autonomous development workflows maintain repository protection standards while the relay handles credential-free publishing.

Why do I need credential isolation for autonomous coding agents operating in bind-mounted repositories?

Credential isolation prevents sandboxed agents from accessing direct repository write permissions or storing secrets inside the execution environment. The host-side relay acts as an intermediary, ensuring agents can commit changes without compromising GitHub credentials.