vibeissue
GitHub Issues from AI agent chat — for vibe coders.
Works on Windows, macOS, and Linux with Cursor, Claude Code, GitHub Copilot, Windsurf, Cline, Gemini CLI, Codex CLI, and any agent that can read repo instructions and run shell commands.
IT — Perché esiste
Stai sviluppando con vibe coding (LLM, iterazione rapida) e perdi il filo di bug, task e idee sparse in chat? vibeissue collega qualsiasi agente AI all'issue tracker ufficiale su GitHub: l'agente crea e aggiorna issue con un comando Python, senza gh CLI e senza script PowerShell.
- CLI stdlib (
urllib) — Windows, macOS, Linux - Token da env,
.env,.secrets/(su Windows anche lettura opzionale da registry) - Regole agente multi-piattaforma — Cursor, Claude Code, Copilot, e altro via
AGENTS.md - Template issue GitHub generici (bug, evolutiva, task)
adopt.pyper copiare tutto in un progetto esistente in un colpo solo
Guide: vibeissue.github.io/docs/it (MkDocs IT/EN) · Sito: vibeissue.github.io
EN — Why it exists
You ship with vibe coding (LLMs, fast iteration) and lose track of bugs and tasks buried in chat? vibeissue wires any AI agent to GitHub Issues: the agent creates and updates issues via a Python CLI — no gh CLI, no PowerShell scripts.
- Stdlib CLI — Windows, macOS, Linux
- Token from env,
.env,.secrets/(on Windows, optional registry read for IDE terminals) - Multi-platform agent rules — Cursor, Claude Code, Copilot, and more via
AGENTS.md - Generic GitHub issue templates
adopt.pyto copy the skeleton into any repo
Guides: vibeissue.github.io/docs (MkDocs IT/EN) · Marketing site: vibeissue.github.io
Quick start
Install from PyPI (CLI)
pip install vibeissue
vibeissue --help
vibeissue-adopt --target ../my-repo --repo myorg/my-app
Run vibeissue from a project that already has the skeleton (tracker/, AGENTS.md, …), or adopt first.
1. GitHub token
Create a Personal Access Token with Issues: read & write on your repo.
Set GITHUB_TOKEN in your environment (see token guide for Windows, macOS, and Linux), or use .secrets/github_token (one line, gitignored).
2. Repository slug
python -c "from pathlib import Path; Path('tracker/github_repo').write_text('myorg/my-app\n')"
Or in .env:
GITHUB_REPO=myorg/my-app
GITHUB_TOKEN=github_pat_...
3. Labels + first issue
python scripts/github_issue.py labels --apply
python scripts/github_issue.py create "Test issue from vibe tracker" --labels task
python scripts/github_issue.py list
4. Adopt into another project
python scripts/adopt.py --target ../my-repo --repo myorg/my-app
5. Wire your AI agent
| Platform | Instruction file |
|---|---|
| Cursor | .cursor/rules/github-issues.mdc |
| Claude Code | CLAUDE.md + AGENTS.md |
| GitHub Copilot | .github/copilot-instructions.md + AGENTS.md |
| Other | See docs |
6. Optional: SSL / corporate proxy
If you see certificate errors toward api.github.com (common on Windows with corporate AV):
pip install -r requirements-optional.txt
7. Documentation (MkDocs IT/EN)
pip install -r docs/requirements.txt
mkdocs serve
Publish to vibeissue.github.io/docs: python scripts/publish_docs.py
Structure
| Path | Role |
|---|---|
scripts/github_issue.py |
CLI: list, create, comment, close, labels, import |
scripts/adopt.py |
Copy skeleton into another repo |
tracker/ |
Labels, manifest, repo slug config |
.github/ISSUE_TEMPLATE/ |
GitHub web forms |
AGENTS.md |
Universal agent instructions |
CLAUDE.md |
Claude Code pointer |
.cursor/rules/github-issues.mdc |
Cursor rule (alwaysApply) |
.github/copilot-instructions.md |
GitHub Copilot workspace instructions |
docs/en/, docs/it/ |
MkDocs sources (published to vibeissue.github.io/docs/) |
mkdocs.yml |
MkDocs + i18n config |
Origin
Extracted and generalized from the Qwibo project tracker. MIT licensed — Antonio Trento, 2026.
Repository: github.com/vibeissue/vibeissue
Metadata
Release files for vibeissue 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vibeissue-0.1.0.tar.gz | 34.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vibeissue-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.3 kB
Release files / vibeissue-0.1.0.tar.gz
| Download URL | vibeissue-0.1.0.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dee86c3c120801a2de76b4ef4bafbea543e2d3dabfc7fd9a663715e635f3ae6
|
|
BLAKE2b-256 checksum How to use checksums |
64b77fcf6db411524f611e0f7e2980a07c420889c638edea96c81677757331af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / vibeissue-0.1.0-py3-none-any.whl
| Download URL | vibeissue-0.1.0-py3-none-any.whl |
|---|---|
| Size | 37.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed6186614e7021ebb4cfbe111f7bf89b8990d0ef1238c7e67abc29ed1988c93c
|
|
BLAKE2b-256 checksum How to use checksums |
76b996657029f9cf6803f96d7e714774d93a62dd7349cbf8397214d6e8f5a97e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for vibeissue 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.