getsentry

Outpost — Git skill for Claude Code

Git community

Autonomous GitHub agent powered by OpenCode.

How to install Outpost

This entry records only its repository, not the path inside it, so there is no exact command to give. Open getsentry/outpost and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Outpost does

Autonomous GitHub agent powered by OpenCode.

Alternatives in Git

Perfup — Autonomous performance optimization: research, PoC, benchmark, implement, review, PR 3.6k ★
Memorix — Open-source cross-agent memory layer for coding agents via MCP 392 ★
Deep Research — Execute autonomous multi-step research using Gemini Deep Research Agent for market analysis, competitive lands 162 ★

README

Outpost

AI coding agent infrastructure for Sentry. Outpost connects GitHub issues to an autonomous coding agent ([Flue](https://flueframework.com), powered by [Pi](https://pi.dev)) running on Cloudflare Workers + Containers, with a dashboard to monitor sessions in real time.

How it works

Label a GitHub issue with jared — a webhook fires to the Outpost Worker
A Flue Durable Object admits the prompt; a thin Sandbox container provides git/gh/node
The agent analyzes the issue, explores the codebase, implements a fix, runs tests, and opens a draft PR
Monitor progress in the Outpost dashboard — see live sessions, messages, tool calls, and cost

When the agent creates a PR that references the issue (e.g. "Fixes #123"), subsequent PR events (reviews, CI results) are routed to the **same conversation**, preserving full context.

Architecture

**Default today (Phase 1):** in-container Flue + Lore (`FLUE_NATIVE=0` + `Dockerfile.phase1`).

GitHub Webhook → Cloudflare Worker (Hono)
                      ├─ Cloudflare Sandbox container
                      │     ├─ Flue Node (Jared + explore/implement/ship)
                      │     └─ Lore gateway (optional; health-probed)
                      └─ D1 (webhook events + dashboard session mirror)

**Phase 2 target** (`FLUE_NATIVE=1` + thin `Dockerfile` — flip both together):

GitHub Webhook → Cloudflare Worker (Hono + Flue)
                      ├─ Flue Jared Durable Object  (agent brain + session + cron)
                      │        └─ Cloudflare Sandbox container (git / gh / node)
                      ├─ D1 (webhook events + dashboard session mirror)
                      └─ Lore gateway (standalone) ← model traffic via setProvider

Worker: Hono app on Cloudflare Workers — webhooks, dashboard, auth-gated Flue agent routes
Flue agent: Tiered subagents (explore, implement, ship); DO schedules only in Phase 2
Container: Phase 1 = Flue+Lore; Phase