---
title: New issue button (GitHub Issues)
---

# New issue button (GitHub Issues)

## What it is

> **REMOVED from Omniscio core (in-core GitHub detachment).** This built-in gh:\* GitHub
> feature has been removed; install the **github-integration** marketplace plugin for
> it. This page is kept for historical reference.

> **Status: the built-in GitHub feature is FULLY REMOVED (plugin-only).** The in-core code is gone — there is no longer any way to restore it (the old Settings > Lab > "Built-in GitHub (legacy)" toggle and the `AMC_SHOW_INCORE_GITHUB` env var no longer exist). It is superseded by the **GitHub Integration** marketplace plugin. Install the plugin for GitHub features.

A **+** button in the GitHub Issues header that lets you create a new GitHub issue
— with title, description, labels, and assignees — without leaving Omniscio. It is an
additive feature on top of the [GitHub Issues](github-issues.md) tab, gated
separately so it can be tested independently.

## Where to find it

### Where

The **+** button appears in the GitHub Issues tab header, next to the refresh button.
It is only visible when the **New issue button** feature is enabled (Settings → Lab →
"New issue button", the `githubIssueCreateEnabled` toggle).

## How it behaves

### What is NOT included

Editing a created issue's labels or assignees after the fact, milestones, projects,
multi-template choosers, and per-repo browsing are not part of this version. Do those on
GitHub.com.

## For agents

### How it works

1. **Click +** to open the New Issue dialog.
2. **Pick a repository.** Choose from the repos already in your issue list, your own
   repos, or type any `owner/repo` combination directly.
3. **Write a title** (required) and a description. If the chosen repository has an issue
   template, the description field is pre-filled with it — your own edits are never
   overwritten by the template.
4. **Add labels and assignees** (optional). Both are multi-select pickers populated from
   that repository's own labels and its assignable users. You are pre-selected as the
   default assignee. The pickers only offer labels and people that already exist on the
   repository; creating new labels is not supported here.
5. **Click Create.** Omniscio creates the issue through the GitHub CLI's identity. If the
   `repo` permission has not been granted yet, a one-time device-code flow asks for it
   first (the same flow as commenting or closing an issue). On success the dialog shows
   the new issue number and a **View on GitHub** link.

### For developers

- Feature id: `github-issue-create`, display name: **New issue button**, status:
  `shipped`.
- Setting key: `githubIssueCreateEnabled`; env var: `AMC_SHOW_GITHUB_ISSUE_CREATE`.
- Two IPC channels: `gh:issue-create-meta` (one GraphQL call to fetch labels, assignable
  users, the viewer, and any issue template) and `gh:issue-create` (a REST write via the
  GitHub API — `POST /repos/{owner}/{repo}/issues`).
- Because every call goes through the `gh` CLI identity, the feature carries over
  unchanged if GitHub later becomes a plugin.

## Related

GitHub features now reach Omniscio through the **GitHub Integration** marketplace plugin, installed from the Marketplace — it covers issue creation along with browsing, a unified side rail and a repository navigator.