Skip to main content
An issue represents a discrete coding task — a feature, bug fix, piece of feedback, or idea — that you hand off to an AI agent. Once you move an issue from Draft to Todo, Gentic queues an agent run: the host clones your repository and the agent follows the instructions in the issue body. Every issue tracks its own status, agent conversation, publishing preference, and pull requests in one place.

​
Create an Issue

1

Open the new issue form

From Home, click New issue in the top-right corner.
2

Select a project

Choose the project (GitHub repository) the agent should work in. If you have no projects yet, create one in Settings first.
3

Fill in the issue fields

Choose a Project, write the Body, and optionally attach files. Gentic generates a title and issue type after submission.
4

Submit

Click Save draft to review the issue first, or choose Run with Claude Code or Run with Codex to queue it immediately.
Write a detailed body with explicit acceptance criteria — for example, “Add a /health endpoint that returns { status: 'ok' } with HTTP 200. Include a Jest test.” The more context you give the agent, the fewer revision cycles you need.

​
Field Reference

​
string
required
The project whose GitHub repository the agent will clone and work in. You cannot change the project after the issue is created.
​
string
Gentic generates a short title in the background after creating the issue. You can edit it later. Edited titles accept up to 160 characters.
​
feature | bug | feedback | idea | spec
Gentic classifies the issue in the background after creation. You can change the result on the edit page. The classifier only ever picks feature or bug; the rest — including spec — are yours to choose.
​
Claude Code | Codex
The AI agent that will execute the issue. The primary run button uses Claude Code; use its dropdown to run with Codex. You can change the agent before the first run from the issue detail page.
​
text
Detailed instructions for the agent. Include background context, step-by-step requirements, acceptance criteria, links to relevant files, and any constraints. The body is passed directly to the agent at the start of each run.
​
enum
Save draft creates the issue as draft. A Run with… action creates it as a draft and immediately transitions it to todo, which queues the agent. See the Issue Statuses reference.
​
boolean
Enabled by default for new issues created in the web app. After a successful turn with unpublished changes and no existing pull request, Gentic adds a visible publishing request and continues the same agent session. Saving a draft preserves your selection. Existing issues and issues created through non-web clients remain disabled unless a client explicitly opts in.

​
Issue Workflow

​
Triggering an Agent Run

Moving an issue’s status from Draft to Todo queues the agent run. The Run with… actions perform that transition during creation; Save draft lets you do it later from the issue detail page.

​
Sending Messages While the Agent Runs

The chat composer is available on the issue detail page. During an active run, new messages are delivered to the current session. Sending a message after a run has ended re-queues the issue and resumes its stored session.

​
Slash Commands

Type / at the start of the composer to open a picker of the underlying agent’s built-in slash commands — for example /model, /plan, /compact, /review. The list is filtered as you type and scoped to the issue’s selected agent, so a Claude Code issue shows Claude Code commands and a Codex issue shows Codex commands. Use the arrow keys to move through suggestions, Tab to insert the highlighted command, Esc to dismiss the picker, and Enter to send. The command text is delivered verbatim to Claude Code or Codex, which handles it natively — Gentic does not translate or intercept it. Add any arguments the underlying command expects after the command name before sending.

​
Re-queuing an Ended Run

If an agent run has ended and you want more work, send a new message from the chat interface. Gentic re-queues the issue and resumes the stored agent session with the prior conversation context intact.

​
Tracking Pull Requests

Every pull request the agent opens for an issue is attached to it and shown on the issue detail page. Each PR appears as its own button labelled owner/repo#number — click one to review those changes on GitHub. An issue can accumulate multiple pull requests over its lifetime. When you re-queue an ended run, any new PR the agent opens is added to the list alongside the earlier ones. Older PRs stay visible so you can trace every change the agent has shipped for that issue in one place. Automatic publishing runs once at most for each active run. The publishing request appears in the transcript with Gentic attribution. It reuses an existing branch or pull request, avoids empty commits, and requires a ready-for-review pull request with a Conventional Commit title plus Summary and Test plan sections. The first Gentic-requested branch follows issue-key-issue-slug; later pull requests can use any branch name. If a finished, idle run has unpublished changes and no pull request, the issue sidebar shows Create PR. This manual action appears with your attribution. It is unavailable during an active run, while automatic publishing is pending, and after a pull request is attached.

​
Merging a Pull Request

Once a pull request is open and approved on GitHub, the issue sidebar shows Merge PR beneath it, so you can land approved work without leaving Gentic. The button appears only while the PR is open, carries GitHub’s approved review decision, and has not failed CI. Pending checks do not hide it — your repository’s branch protection rules still decide whether the merge goes through. Gentic merges with the first method your repository still allows, preferring squash, then merge commit, then rebase, and leaves the commit message to your repository’s own defaults. The merge is pinned to the exact commit the approval was checked against, so a push that lands between your click and the merge is rejected rather than merged unreviewed. Gentic re-checks the pull request’s live state before merging, so if the approval was dismissed or the PR was closed since the page last refreshed, the button reports that instead of merging. Merging requires the GitHub App’s Contents permission to be Read & write — see GitHub Integration.
Merging cannot be undone from Gentic, so the button asks for confirmation first.

​
Spec Issues

A Spec is an issue that records intent instead of asking for it to be built — a written requirement, a design decision, a brief that other issues implement. Set the type to Spec from the type menu on the issue detail page or the edit page. A Spec differs from every other type in two ways:
  • No agent runs it. Hosts skip Spec issues when claiming work, so a Spec left in Todo is never picked up. Its statuses are a marker of your own progress; moving one from Draft to Todo does not queue anything.
  • It has no conversation. The detail page shows the body and the issue’s history with no chat composer, because there is no agent session to send to.
Everything else — labels, priority, relations, files, and the body — works exactly as it does for other issues, so a Spec can block the issues that implement it. Changing a Spec back to another type restores its agent behaviour. You cannot convert an issue into a Spec while an agent run is active on it; finish or retry the run first.

​
Edit an Issue

Open the issue detail page and click Edit. You can update the Title, Body, Agent, Type, and Create PR automatically fields. Once a pull request is attached, the publishing preference becomes read-only historical data. The Project field cannot be changed after creation.

​
Reset an Issue

Resetting clears the agent session and re-queues the issue as if it were starting fresh, on the agent and model it is already set to. Open the issue, click the ⋮ menu beside the title, choose Reset, and confirm. Reset is offered on any issue that has left Draft. A draft has nothing to reset — move it to Todo to start it. A Spec never shows the action, because no agent runs it.
Resetting is irreversible: Gentic deletes the stored conversation and pull-request links for the issue, then creates a fresh kickoff message — Work on Gentic issue {Issue Code}. — that the agent uses to read the current body. It does not delete pull requests from GitHub.
Switching the agent or model from the composer’s picker takes the same path once a conversation exists, and asks for the same confirmation.

​
Delete an Issue

To permanently remove an issue, open the issue detail page, click Delete, and confirm. Deletion redirects you back to the Home issues list.