Skip to content

docs: link production eve templates #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bensabic merged 1 commit into from
Aug 26, 2026
Merged

docs: link production eve templates #104

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions apps/docs/content/docs/2.frameworks/1.eve-extension.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,12 @@ npx eve dev

You now have a GitHub agent that can read repos, review PRs, triage issues, and manage CI, with every write operation gated behind durable approval by default. The full example lives in [`examples/eve/`](https://github.com/vercel-labs/github-tools/tree/main/examples/eve) (or `pnpm dev:eve` from the monorepo root).

<br>

For complete production implementations, see the [Software Factory and Incident Response Agent](/examples/overview#production-eve-templates). Both use the eve extension with [Vercel Connect](https://vercel.com/connect), while scoping GitHub access for different operational needs.

<br>

## Install

:::code-group
Expand Down
8 changes: 8 additions & 0 deletions apps/docs/content/docs/3.examples/1.overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,14 +63,22 @@ For larger, production-ready agents, start with one of these complete eve templa

[Foreman](https://github.com/vercel-labs/eve-software-factory-template) takes work from GitHub and Linear through four specialist agents: classifier, analyst, implementer, and reviewer. It finishes with a reviewed draft pull request for a person to approve and merge.

<br>

[Deploy the Software Factory](https://vercel.com/templates/eve/eve-software-factory) | [Learn More](https://vercel.com/kb/guide/eve-software-factory)

<br>

### Incident Response Agent

[`sre`](https://github.com/vercel-labs/eve-sre-agent-template) investigates production alerts using live Datadog, GitHub, and Vercel data. It tests hypotheses, records findings with source links, and keeps investigations read-only by default. Start an investigation from Slack, a watched alert channel, or a webhook.

<br>

[Deploy the Incident Response Agent](https://vercel.com/templates/eve/eve-incident-response-agent) | [Learn More](https://vercel.com/kb/guide/eve-incident-sre-agent)

<br>

Both templates use [`@github-tools/eve-extension`](/frameworks/eve-extension) and [Vercel Connect](/guide/vercel-connect) for scoped GitHub access without long-lived credentials.

## Every example uses Vercel Connect
Expand Down
6 changes: 6 additions & 0 deletions apps/docs/content/docs/4.guide/5.vercel-connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,12 @@ export default githubExtension({

See [`examples/eve`](https://github.com/vercel-labs/github-tools/tree/main/examples/eve) for a runnable example.

<br>

For production implementations, see the [Software Factory and Incident Response Agent](/examples/overview#production-eve-templates). Both use [Vercel Connect](https://vercel.com/connect) to give eve agents scoped GitHub access without storing long-lived credentials.

<br>

## eve agent

::callout{icon="i-lucide-alert-triangle"}
Expand Down
Loading