# AI Agents Inside Your Repository Workflow

> Deploy bots, models, and automations where your code lives. Trylle agents comment on pull requests, triage issues, and run on repo events with clear credits and permissions.

## Agents on your timeline

Trylle pairs models, bots, and workflow automations so you move faster without giving up ownership. Signals stay tied to the branch; runs stay attributable; credits stay beside the pull.

## Configure who runs, what they touch, and when.

### 01. Who runs the agent

Workspace scopes billing and repos. The bot is the service account on your timeline. Runtime and model pick the sandbox and weights for each run.

### 02. What it can touch

Repositories and triggers decide when a run starts. Permissions trim the toolkit—inherits from the bot or tighten per automation.

### 03. Cadence when you need it

Optional cron beside event triggers—hourly checks, weekly sweeps—without wiring a second scheduler outside the repo.

## How agents show up where you already review.

Agents enhance Trylle—appearing in timeline comments, automations, and Settings. No extra "AI app" required.

### Bots flag risk on the timeline

Kick off service accounts on `pr.opened`, `ci.failed`, or a `@bot` mention to surface secrets drift, flaky touchpoints, or policy gaps—where maintainers already ship.

### Assist cues beside approval

Confidence, scope locks, and check status stay in the review footer so reviewers skim signals before they decide—not after three extra tabs.

### Repo scope by default

Automations inherit organization and repository grants. Bots cannot wander into projects you never connected or approved.

### Start from official templates

PR Review, CI Failure Fixer, Issue Triage, Release Notes Drafter, Dependency Updater—install one beside your repo and it runs on real events, with permissions you control.

## Agents & automation, answered.

### What counts as an "agent" in Trylle?

Bots (service accounts), automation templates that call models, and assist features in review. They share repo scope, permissions, and a credit ledger—not a separate AI product.

### Can a bot merge my default branch?

Only if your branch protections and bot grants allow it. We default to draft-and-comment: agents surface context; humans approve merges.

### What data do models see?

Only context you wire into a template: diffs, issues, and metadata for repositories the automation is scoped to. Nothing outside that grant.

### How do automation credits work?

Each model run debits your org pool. Failed runs still log status and reason. Balances and history live under Settings → AI.

### Where do I configure bots and templates?

Settings → AI for credits and defaults; Automations for templates; Bots for service accounts. Everything on this page maps to a control in the product today.

## Bring review home to your repository.

Migrate a repo from GitHub or push a new one, invite reviewers, and keep diffs, issues, and automation on the same timeline as the code.

---

HTML version: https://trylle.com/agents
Canonical: https://trylle.com/agents