Simplify GitHub Integration for Agents

[jason1804]

Feature Request: Simplify GitHub Integration for Agents

Problem Statement

Currently, configuring GitHub access for GoClaw agents requires multiple manual steps that are error-prone and poorly documented:

1. Manually creating GitHub Personal Access Token (PAT)
2. Adding GH_TOKEN to .env file
3. Restarting the entire GoClaw container
4. Dealing with permission issues when gh CLI runs as non-root user
5. No UI feedback to confirm token is working

This is too complex for a simple "read repo" use case.

User Journey (Current)

User wants agent to read GitHub repo
  ↓
Create PAT on GitHub (manual)
  ↓
Edit .env file (manual)
  ↓
Restart container (downtime)
  ↓
Agent still fails due to permission issues
  ↓
Debug environment variables, user permissions, volume mounts
  ↓
Finally works after 30+ minutes of troubleshooting

Proposed Solutions

Option 1: Dashboard UI for GitHub Integration (Best UX)

• Add "Integrations" section in Dashboard
• OAuth flow: "Connect GitHub" button → authorize → auto-inject token
• Auto-restart agent runtime without full container restart
• Visual status indicator (✅ Connected / ❌ Not connected)

Option 2: Hot-reload Environment Variables

• Allow adding/updating env vars without container restart
• API endpoint: POST /api/config/env with { "GH_TOKEN": "..." }
• Agent runtime picks up changes automatically

Option 3: Built-in GitHub Tool

• Native github tool in GoClaw (like web_fetch, exec)
• Configurable via Dashboard → Tools → GitHub
• Handles auth internally, no manual env setup

Documentation Gaps

Current docs do not cover:

• How to grant GitHub access to agents
• Troubleshooting gh auth permission issues in containers
• Difference between env_file and environment in docker-compose
• How to verify token is loaded in agent runtime

Environment

• GoClaw: v3.0.0
• Deployment: Docker Compose
• Use case: Agent needs read-only access to GitHub repos

Impact

This friction prevents users from leveraging GoClaw for:

• Code review automation
• Repo status monitoring
• CI/CD integration
• Developer workflow assistance

A simpler integration would significantly improve the developer experience.