Every issue in Gentic carries two independent status fields: a workflow status that describes where the issue sits in the development lifecycle, and a run status that tracks the agent worker process for the current or most recent run. This page documents every possible value for both fields.
Moving an issue from Draft to Todo is the specific transition that queues an agent run. Until you make that change, no agent worker is started and no repository is cloned.
Workflow Status
Pre-work
These statuses indicate the issue has not yet been picked up by an agent.
| Status | Description |
|---|
draft | The issue is being prepared. The agent has not been queued. Use this status while you are still writing or refining the prompt. |
todo | The issue is ready and has been queued for an agent run. The agent worker will pick it up and begin cloning the repository. |
Agent Running
These statuses indicate an agent run is currently active.
| Status | Description |
|---|
in-progress | The agent is actively working — cloning the repo, writing code, or committing changes. |
waiting-for-input | The agent has paused and is waiting for you to send a message before it continues. Open the issue and reply in the chat interface to unblock it. |
Review
These statuses cover the period between the agent opening a pull request and the PR being merged.
| Status | Description |
|---|
testing | Automated tests are running against the agent’s changes. |
tests-failed | One or more automated tests failed. Review the test output and either send the agent a message to fix the failures or update the code manually. |
ready-for-review | The agent has opened a pull request and it is ready for human review on GitHub. |
changes-requested | A reviewer has requested changes on the pull request. Send the agent a message or push changes to address the feedback. |
approved | The pull request has been approved by a reviewer and is ready to merge. |
Merge and Deploy
These statuses cover the period after the pull request is merged through to production validation.
| Status | Description |
|---|
merged | The pull request has been merged into the target branch. |
deploying | A deployment pipeline is running the merged changes to a target environment. |
deploy-failed | The deployment failed. Check your CI/CD logs for details. |
validating | The deployed changes are being validated — for example, by smoke tests or a health check. |
Terminal
Issues in these statuses are no longer active. You can re-queue them by sending a new message in the chat interface.
| Status | Description |
|---|
completed | The issue has been resolved and all work is done. |
cancelled | The issue was cancelled before completion. No further agent work is planned. |
Run Status
The run_status field tracks the agent worker process lifecycle for the current or most recent agent run. It is separate from the issue workflow status and updates automatically as the worker progresses.
| Run Status | Description |
|---|
queued | The run has been accepted and is waiting for an available agent worker. |
cloning | The agent worker is cloning the GitHub repository specified by the issue’s project. |
running | The agent is actively executing — reading files, writing code, and running commands inside the cloned repository. |
completed | The agent worker finished successfully. The workflow status is updated based on the outcome (for example, to ready-for-review once a PR is opened). |
failed | The agent worker encountered an unrecoverable error. Check the run logs on the issue detail page for details. |
cancelled | The run was cancelled before the agent could finish, either manually or due to a system event. |
