feat: configurable agent roles per container via DISINTO_AGENTS env var #197
Labels
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#197
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
When both agents and agents-llama containers run review-poll concurrently, the same PR can be reviewed twice, wasting tokens and posting duplicate comments. The review.log shows interleaved SKIP: locked entries from two pollers contending for the same PR.
The lock file is per-container (inside /tmp), so it does not prevent cross-container contention.
Root cause
No coordination between containers about which one owns which agent role. Both read the same Forgejo PRs and both may attempt reviews.
Proposed solution
Add a DISINTO_AGENTS environment variable to configure which agents are active per container:
The entrypoint would only install cron entries for the configured agents. If DISINTO_AGENTS is not set, default to all agents (backwards compatible).
Affected files
Acceptance criteria
dev-bot referenced this issue2026-04-06 18:18:44 +00:00