@a5c-ai/triggers-adapter

@a5c-ai/triggers-adapter

Trigger glue for running any coding agent from CI. Normalizes GitHub, GitLab, Bitbucket, and generic webhook payloads into one event shape, enriches GitHub events with changed files and optional diffs, and evaluates compact trigger queries before launching adapters.

CLI

triggers evaluate --backend github --query "event:issue_comment text:@develop-this path:packages/adapters/**"
triggers enrich --backend github --include-diff --output event.json

GitHub Action

The reusable action at packages/adapters/triggers/action.yml supports all harnesses, providers, and invocation modes.

Quick Start

- uses: a5c-ai/babysitter/packages/adapters/triggers@main
  with:
    harness: claude
    provider: foundry
    model: gpt-5.5
    prompt: Review this PR for bugs and style issues
  env:
    AZURE_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY }}
    AGENT_MUX_API_BASE: ${{ vars.AZURE_OPENAI_ENDPOINT }}

Supported Harnesses

Invocation Modes

Set interaction-mode to control how the harness runs in CI:

When to use each mode

• non-interactive (default) — fastest, simplest. The harness gets a prompt, does the work, exits. Good for single-task automation.
• bridged-hooks — use with babysitter-plugin: true. The BridgeHookEmulator wraps the harness execution with session-start/stop/end hooks, enabling the babysitter orchestration lifecycle.
• bridged-interactive — spawns the harness via PTY for full interactive capabilities (tool use, multi-turn) while presenting structured NDJSON output externally. Use when the harness needs TTY features but you want machine-readable output.

Babysitter Plugin

Set babysitter-plugin: true to install the babysitter plugin before running:

- uses: a5c-ai/babysitter/packages/adapters/triggers@main
  with:
    harness: claude
    provider: foundry
    model: gpt-5.5
    interaction-mode: bridged-hooks
    babysitter-plugin: 'true'
    babysitter-prompt-prefix: '/babysitter:yolo'
    prompt: Implement the feature described in the issue
    process-file: .a5c/processes/feature-impl.mjs

The action will:

1. Install the harness CLI
2. Generate per-harness plugins (npm run generate:plugins)
3. Install the babysitter SDK globally
4. Install the babysitter plugin into the harness (babysitter harness:install-plugin)
5. Copy the process file to .a5c/processes/ (if provided)
6. Launch with the appropriate bridge flags

Babysitter prompt prefixes

Each harness uses a different prefix to invoke the babysitter skill:

Provider Configuration

The action uses adapters launch which handles provider resolution and proxy setup automatically. Set credentials via environment variables:

Azure Foundry (OpenAI)

env:
  AZURE_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY }}
  AGENT_MUX_API_BASE: https://your-resource.services.ai.azure.com

Google / Vertex AI

env:
  GOOGLE_API_KEY: ${{ secrets.GOOGLE_API_KEY }}
  GOOGLE_CLOUD_PROJECT: ${{ secrets.GOOGLE_CLOUD_PROJECT }}
  GOOGLE_GENAI_USE_VERTEXAI: 'true'

Anthropic (direct)

env:
  ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}

Trigger Queries

Filter which events trigger the agent using trigger-query:

trigger-query: |
  event: pull_request
  action: [opened, synchronize]
  paths: src/**/*.ts
  labels: needs-review

Query fields

Inputs Reference

Example Workflows

See .github/workflows/ for complete examples:

• claude-code-pr-review.yml — Claude Code + Foundry + babysitter-plugin + bridged-hooks for PR review
• codex-issue-triage.yml — Codex + Foundry + vanilla NI for issue classification
• gemini-scheduled-audit.yml — Gemini CLI + Google/Vertex + scheduled docs audit
• multi-harness-quality-gates.yml — Matrix of claude + codex + pi with babysitter-plugin
• copilot-webhook-dispatch.yml — Copilot CLI + bridged-interactive for repository_dispatch
• pi-comment-command.yml — Pi + NI triggered by /agent comment commands

Outputs