GitHub

Developer Reference

This page covers internal implementation details. It is not included in the User Guide.

GitHub is a routing target in the integrations agent. The handler classifies queries as github and forwards them to the code-gen agent for Python script generation.

---

Repo

escher-dbai/v4-integrations-agent-go — internal/integrations/github/handler.go

---

Flow

User query (NL)
   │
   ▼
Integrations Agent classifier (Haiku)
   {"integration": "github", "confidence": ...}
   │
   ▼
GitHub handler:
   - emits SSE thinking_state ("Connecting to GitHub integration...")
   - builds CodeGenRequest{ Action: "github", UserQuery, ConversationContext, ... }
   - calls Code-Gen Agent (POST /api/v1/generate-playbook)
   - proxies the SSE stream back to the client

The handler is structurally identical to Linear and Jira — it routes and proxies; it does not implement GitHub-specific logic. The code-gen agent prompt set knows how to generate Python scripts that call the GitHub REST/GraphQL APIs.

---

What this is not

The user-facing positioning of GitHub elsewhere in the marketing copy describes deploy-to-cloud-event correlation, pre-merge risk scoring, author attribution from cloud events, and PR-linked Canvases. None of those are implemented in this codebase today.

The GitHub integration today is: natural-language → GitHub-flavored Python script. Anything richer is roadmap.

---

Adding capability

Same lever as Linear/Jira: extend the code-gen agent's prompt corpus for action: "github". The integrations-agent handler does not change with capability extensions.

---

See also

• Linear — same routing pattern
• Jira — same routing pattern
• Slack — handled differently (in-house Block Kit formatter, no code-gen)