How Gentic Works: Issues, Agents, and Pull Requests - Gentic

Gentic connects two things: a web app where your team writes and manages work, and a background host process that turns that work into real code. Understanding how these two parts communicate helps you configure Gentic correctly and troubleshoot issues when something unexpected happens.

The end-to-end flow

Supported agents

Agent	Identifier	Notes
Claude Code	`claude_code`	Requires Claude credentials (API key or OAuth) present in the host environment before the host starts.
Codex	`codex`	Requires the Codex CLI installed on the host and authenticated. Set `CODEX_PATH` in the environment if the binary is not on `PATH`. Runs default in `agent-full-access` mode unless `INITIAL_AGENT_MODE` is overridden.

Issue status reference

Every issue carries a single status field. The most common values are summarised below; for the complete list — including review, deploy, and terminal statuses, plus how GitHub pull request events map back into Gentic — see Issue Statuses.

`status`	Meaning
`draft`	Issue is being written; invisible to the host.
`todo`	Issue is ready in the unclaimed pool; waiting for a host to pick it up.
`queued`	A host has claimed the issue and is cloning the repository.
`held`	The agent hit a usage or session limit; the host will retry after the parsed reset time.
`in-progress`	The agent session is running against the cloned repository.
`ready-for-review`	A pull request is open on GitHub and waiting for review.
`run-failed`	The agent run ended with an error before opening a pull request.

Quick Start

Follow a step-by-step guide from signup to your first pull request.

Agent Host Setup

Deploy, configure, and manage the background host process.

Hosts

Enroll, monitor, and manage host machines from Settings.