Skip to main content
Gentic is a platform for managing AI coding agents. Instead of context-switching into a terminal or IDE to prompt an AI tool, your whole team works from a shared web app where they write issues, track progress, and review pull requests — all in one place. You write the requirements; Gentic’s agent host picks them up, runs Claude Code or Codex against your real codebase, and can publish the resulting changes as a pull request for you to review.

​
How Gentic is structured

Gentic has two parts that work together: the web app you use every day, and the agent host you deploy once on a server.

Web App (app.gentic.chat)

Create and manage projects, write issues, choose an AI agent, upload attachments, and watch pull requests appear — all from your browser.

Agent Host CLI

A background process you deploy on any server or VM. It polls Gentic for queued issues, clones the right repo, runs the agent, and pushes a PR.

​
Key features

Issue Management

Create issues from a detailed body and attachments, then move them through Draft → Todo → In progress → Ready for review.

Claude Code & Codex

Assign each issue to Claude Code or OpenAI Codex. The host selects the right agent automatically based on the issue setting.

GitHub Integration

Connect a GitHub App so pull-request and review events update the matching Gentic issue. The host keeps separate Git credentials for cloning and pushing.

File Attachments

Attach images, text files, and other documents to the issue body or a follow-up message.

Issue Dependencies

Block one issue on another to sequence work. Dependent issues won’t be picked up by the host until their blockers are resolved.

MCP Server

Manage Gentic from Claude Desktop, Cursor, or any other MCP-compatible AI client without opening the web app.

​
Supported AI agents

Gentic currently supports two AI coding agents. Choose one when you run an issue. You can switch it from the issue detail page until the first run starts.

​
Architecture overview

When you move an issue from Draft to Todo, Gentic queues it for the host. Your deployed agent host polls the Gentic API every few seconds, claims the next queued issue, clones the project’s GitHub repository into a fresh working directory, and runs the chosen agent through the Agent Client Protocol (ACP). The issue status updates in real time. When Create PR automatically is enabled, a successful changed turn receives a visible publishing follow-up in the same session. The host never exposes a public endpoint — it is a private outbound polling process that you run in a trusted environment.
Because the agent host runs in your own environment, it has access to your source code and Git credentials. Run it on a server or VM you control, and treat your GENTIC_HOST_CREDENTIAL as a secret.