new agent called intern #7

New Issue

2026-07-02T17:08:31+02:00

ffaerber commented

2026-07-02 17:08:31 +02:00

please create me a new agent called intern he is using the local ollama model ornith

ffaerber commented

2026-07-02 17:08:37 +02:00

@pm here

🚀 1

gitea-actions bot commented

2026-07-02 17:09:25 +02:00

🤖 @pm

@ffaerber — before I draft a plan, I need a few specifics since "intern" isn't just a config toggle — it needs a role definition like the others, and several things in agent.yml intentionally couple to a fixed agent list:

Role/responsibilities: What should @intern actually do? @junior already runs on the local ornith model for "small, low-risk YAML/compose/config" changes — if @intern uses the same model, what's the differentiation (e.g. docs-only, tests-only, "even smaller/no-PR" scope, or just extra capacity/parallel junior)?
Mode: Should @intern open PRs like @junior/@senior/@lead (mode: pr), or comment-only like @pm/@qa (mode: comment)?
Vision: Ornith is text-only (same as @junior), so I'll assume vision: false unless you say otherwise.
Own Gitea identity: Do you want a TOKEN_INTERN secret/bot user (so commits/PRs are authored as intern), or is falling back to the shared bot token fine for now?

Why this matters technically: adding a new name isn't a one-line edit. It requires touching several tightly-coupled spots in agent.yml that AGENTS.md explicitly calls out as sensitive (the trigger gate, delegation-target regex used in multiple places, and the token-selection case blocks) — plus the README's roster/secrets table. Getting the role/mode wrong means redoing all of those, so I'd rather confirm intent first.

If @intern is meant to just be "a second @junior-style low-risk YAML/config dev," say so and I'll skip straight to planning with that assumption.

🤖 **@pm** @ffaerber — before I draft a plan, I need a few specifics since "intern" isn't just a config toggle — it needs a role definition like the others, and several things in `agent.yml` intentionally couple to a fixed agent list: 1. **Role/responsibilities**: What should `@intern` actually do? `@junior` already runs on the local `ornith` model for "small, low-risk YAML/compose/config" changes — if `@intern` uses the *same* model, what's the differentiation (e.g. docs-only, tests-only, "even smaller/no-PR" scope, or just extra capacity/parallel junior)? 2. **Mode**: Should `@intern` open PRs like `@junior`/`@senior`/`@lead` (`mode: pr`), or comment-only like `@pm`/`@qa` (`mode: comment`)? 3. **Vision**: Ornith is text-only (same as `@junior`), so I'll assume `vision: false` unless you say otherwise. 4. **Own Gitea identity**: Do you want a `TOKEN_INTERN` secret/bot user (so commits/PRs are authored as `intern`), or is falling back to the shared bot token fine for now? Why this matters technically: adding a new name isn't a one-line edit. It requires touching several tightly-coupled spots in `agent.yml` that AGENTS.md explicitly calls out as sensitive (the trigger gate, delegation-target regex used in multiple places, and the token-selection `case` blocks) — plus the README's roster/secrets table. Getting the role/mode wrong means redoing all of those, so I'd rather confirm intent first. If `@intern` is meant to just be "a second `@junior`-style low-risk YAML/config dev," say so and I'll skip straight to planning with that assumption.

ffaerber closed this issue

2026-07-03 11:18:13 +02:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: gitea/agents#7