- Auto-detected repo connection the panel detects this project’s GitHub repo from your actual git remote and offers a one-click connect, rather than a free-text field you have to get right yourself; manual entry is still available for the rare case origin isn’t the repo you want
- Issues & Pull Requests both listed side by side, each with title, author, and a color-coded state badge (open / closed / merged)
- State filter Open / Closed / All, defaulting to Open so a busy repo’s closed history doesn’t drown out what’s actionable
- Create issue a title + body form posts directly to GitHub; the list auto-refreshes with backoff to cover GitHub’s own list-endpoint lag after a write
- Open-count badge open issue count shown on the Tickets activity-bar icon once you’ve opened the panel at least once that session (no background API calls before then)
- Add to Kanban board one click imports an issue or PR as a Kanban card (title + body), tagged so re-importing later updates the same card instead of duplicating it; your card’s column/status is never overwritten by a re-import
- Provider-agnostic under the hood built against a small
TicketProviderinterface; GitHub is implemented today, GitLab/Bitbucket are a matter of adding a sibling implementation - Token stored in Settings → Integrations (classic personal access token recommended; fine-grained works too, with the setup steps spelled out in-app)
Core
Tickets
GitHub issues and pull requests, connected to your project’s own git remote.
