Skip to content

v0.8.0 — Support Engineer Agent

Choose a tag to compare

@nikhilsoman nikhilsoman released this 21 Jun 10:21
ccd3454

What's new

Support Engineer Agent (synlynk agent run support)

synlynk now watches itself. On every push to main (and on a 6-hour schedule), the Support Engineer collects health signals across 5 dimensions, deduplicates against a 7/30-day history, dispatches Claude to investigate new findings, files GitHub issues with results, and opens draft fix PRs when the investigation produces a passing diff.

New commands:

  • synlynk agent run <name> — run a named agent (support, or any .agents/*.json config)
  • synlynk agent list — list configured agents and their last run time
  • synlynk agent run support --dry-run — print findings without filing issues or writing DB

Signal collectors:

  • Test suite health (pass rate trends)
  • Sentinel alerts (FLATLINE, SUCCESS_LOOP, QUOTA_EXHAUSTED)
  • Telemetry anomalies (duration spikes, error rate)
  • Capability score drops (agent routing degradation)
  • GitHub issues (open bug reports)

Deduplication: 7-day window for ephemeral signals, 30-day for structural findings. New autopilot_runs SQLite table tracks run history.

Agent config: .agents/support.json (stdlib JSON). Add more agents by dropping a new JSON file — the engine picks them up automatically.

GitHub Actions: .github/workflows/support-engineer.yml fires on push to main and on 0 */6 * * *. Requires ANTHROPIC_API_KEY secret.

Tests

342 passing (up from 318 in v0.7.0). 24 new tests cover all collectors, dedup windows, issue filing, fix attempt, dry-run no-side-effects, and cron idempotency.