FAQ

BugIt runs inside Visual Studio Code with GitHub Copilot Chat, the Claude extension, or another assistant and a recent version of Python (3.10 to 3.14). Windows 11 is fully supported and release-validated; macOS and Linux are supported but currently in Preview while validation broadens. BugIt does not include an AI model or subscription; you bring your own.

No. Every ticket, comment, attachment or notification that carries your report is previewed first. Before an irreversible filing, you approve it by typing FILE IT; chat text alone never files. A plain "yes" is not enough. Use dry run for zero-write practice. Connection tests are the one exception: when you deliberately run notify connect, notify test or notify doctor --live, BugIt sends one fixed test message without a preview, to the channel you name or, if you name none, to every channel you have switched on. Those tests carry no report content, and dry run blocks them too.

All eleven include built-in, tested field mapping and create tickets directly through the tracker’s REST API, using a credential you create in your own account: Jira Cloud, Azure DevOps, GitHub Issues, GitLab Issues, Bugzilla, YouTrack, Linear, Shortcut, ClickUp, Asana and Trello. Filing does not use MCP. Crash tools and other services still connect through your own MCP server. Screenshot and log uploads through BugIt reach eight of the eleven; uploads to GitHub Issues, GitLab Issues and Bugzilla are not supported, and you are told before you try.

GitHub Copilot is the easiest setup and is recommended. BugIt also works with the Claude extension in VS Code, another assistant, or a plain terminal. Filing is a command, so it works the same in all of them.

Yes, inside GitHub Copilot where those models are available to your plan. Standalone mode supports your own OpenAI or Anthropic key.

No. Bug reports, specs, glossary, screenshots, code, settings and tickets are not sent to Taskivator. Only license/update data is used.

BugIt sends Taskivator only licensing and update data: your Portal sign-in; an anonymous, one-way hashed device identifier; a random installation identifier; your device label and operating system; the BugIt version and selected plan; short-lived cryptographic challenge data; the one-time approval token from the Portal link your browser opened; a per-activation acknowledgement secret, whose hash is sent when you activate and whose value is sent only if you withdraw access for this device; and the entitlement approved for this device.

BugIt Team is available now. A 1-year license with no subscription covers up to 5 members, does not renew automatically, and each member gets their own BugIt account, their own sign-in, and their own device activation, instead of a shared license. Team configuration is shared and managed centrally in the Portal, and it does not auto-renew. Solo is unaffected and available too. Need more than five? A second Team license adds five more seats to the same Team, and each license runs its own term.

Yes. Use dry run to generate the full report without creating tickets, comments, attachments or notifications. Dry run stops BugIt’s bundled helpers from writing and tells the agent to refuse tracker writes; that refusal follows BugIt’s instructions rather than a platform lock, so use read-only credentials when evaluating.

Safe buyer-owned files include config.json, .vscode/mcp.json, .github/glossary/terms.template.md, .github/instructions/learned.instructions.md, and .github/instructions/house-style.instructions.md if you create it.

Do not hand-edit .github/agents/bugit-qa-agent.agent.md, other shipped files under .github/instructions/, or anything in tools/. Updates overwrite those product files and they are not backed up.

BugIt backs up your buyer-owned settings, verifies signed updates, installs in place, and preserves your config, glossary, house style, license and connections.

BugIt is a 1-year license with no subscription and does not auto-renew. Your one-year license covers updates and license/activation services; when it ends, a 3-day grace period follows, after which filing and activation features need a current license, while your local files and settings stay yours. You can buy a new license to continue. There is no automatic charge. Licensing-server outages are separate: cached verification lets you keep working for up to 72 hours offline. The year begins on the date of purchase.

No. Buying again replaces your current activation and starts a fresh one-year license from that date, so buy again near the end of your current license. Purchases never renew automatically.

First ask the AI assistant to diagnose the issue, then run Check status or Check readiness. If you are still stuck, open a support ticket from your BugIt dashboard. There is no need to include confidential project details.