Runs
A run is one end-to-end context update cycle.
Every time Kontrua is triggered - by a webhook, the CI endpoint, a schedule, or a manual button click - it creates a run. Each run processes the code diff, calls the relevant generators, and produces updated context artifacts and doc views.
Run states
| State | Meaning |
|---|---|
| pending | Run created, waiting to be picked up |
| running | Agents are actively generating content |
| success | All agents completed, PR opened |
| failed | An error occurred; details shown in the dashboard |
| queued | Monthly quota exceeded; run will retry when space opens |
Queued runs
When your monthly run limit is reached, new runs are not dropped. They enter a queued state and are retried automatically at the start of the next billing period or if a run slot becomes available earlier (e.g. after plan upgrade).
Viewing output
Open any run in Dashboard - Runs to see the generated content, which context artifacts and doc views were updated, a step-by-step progress log, and a direct link to the context pull request.
Trigger types
| Trigger | Source |
|---|---|
| pr_approved | GitHub PR approval or GitLab MR approval via webhook |
| pr_merged | PR / MR merged event via webhook |
| ci | Direct call to POST /api/trigger |
| scheduled | Recurring schedule configured on the repository (daily / weekly / monthly) |
| manual | "Run now" button in the dashboard |
Ready to keep your repo's context current?
Connect your first repository and Kontrua opens a reviewed PR with AGENTS.md, a codemap, and your conventions.