--- title: GitHub Issues --- # 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, which has full parity plus a codebase browser, a unified siderail, and a repo navigator. Install the plugin for GitHub features. The **GitHub Issues** tab is a cross-repo GitHub issue manager, built as a sibling of the Pull Requests tab. It lists the open issues you are involved in across every repo your GitHub account can access, and lets you open an issue to read its description and comment thread, add a comment, and close or reopen it — all without leaving Omniscio. It is released for everyone: the **GitHub Issues** entry appears in the left sidebar by default, with no toggle to find first. ## Where to find it It used to be a sidebar panel inside Omniscio; that surface is gone. GitHub now comes to the app through the **GitHub Integration** marketplace plugin, which you install from the Marketplace and open from its own sidebar entry. ## How it behaves ### How it works - **Connect** — the tab shells out to the GitHub CLI (`gh`). If `gh` is missing or not signed in, it shows a one-click **Connect GitHub** prompt. Browsing needs only a signed-in `gh`; commenting and closing/reopening need the `repo` permission, which the tab requests with a one-time device code the first time you act. - **Browse (Pane 2)** — filter chips switch between **All** (everything you are involved in), **Created** (issues you opened), and **Assigned** (issues assigned to you). Each row shows the repo, number, title, author, and how recently it was updated, newest first. When the list spans more than one repo, a dropdown narrows it to a single repo. The list shows **open issues only** and never includes pull requests. - **Read + act (Pane 3)** — open an issue to see its title, state, labels, assignees, author, and dates, the issue body rendered as Markdown, and the full comment thread. The action bar lets you: - **Comment** — posts to the issue thread and refreshes the view. - **Close** — asks you to confirm first (it is the state-changing action), then closes the issue on GitHub. You can **Reopen** it again with one click at any time. - **Open on GitHub** — every issue links out to its page on github.com for anything the tab does not do yet. - **Arrive from a notification**: when the tab is visible, clicking an Issue-type notification in the GitHub channel opens this view with that issue already selected. ### Create a new issue A **+** button appears in the GitHub Issues header, next to refresh. It opens a dialog where you: - **Pick a repository** — choose from the repos already in your issue list or your own repos, or type any `owner/repo`. - **Write a title** (required) and a description. If the repo has an issue template, the description is prefilled with it; your own edits are never overwritten. - **Add labels and assignees** — both are multi-select pickers populated from that repo's own labels and assignable users, and you are pre-selected as the default assignee. - **Create** — Omniscio creates the issue through the GitHub CLI's identity (it requests the `repo` permission once if needed) and shows the new issue number with a **View on GitHub** link. It can take GitHub a moment to show the new issue back in your list. The pickers only offer labels and people that already exist on the repository, so you cannot create a brand-new label here. ### What is deferred Editing an existing issue's labels / assignees after creation, milestones / projects, a multi-template chooser, per-repo browsing, and a "show recently closed" toggle are planned follow-ups, not part of this version. ## For agents ### Where it lives A virtual project (`__github_issues__`) in the project bar, all data over `gh:issue-*` IPC channels, registered in the unreleased-feature registry (id `github-issues`, status `'shipped'`, so the visibility gate passes for every user). The **New issue** button is controlled by its own `github-issue-create` registry entry (status `'shipped'`, so it shows for every user) and uses two more channels — `gh:issue-create-meta` (one GraphQL call for labels, assignable users, the viewer, and the issue template) and `gh:issue-create` (the REST write). Because every call goes through the `gh` CLI, the feature carries over unchanged when GitHub later becomes a plugin. ## Related The plugin carries the features this page used to describe, plus a codebase browser, a unified side rail and a repository navigator.