Skip to content

testlauncher/bugagent

v0.1.0-preview.2MIT

Capture bugs with approval, check possible duplicates, and look up reports in bugAgent using an existing bugAgent license.

bugAgent Plugin (Preview)

Public source for bug capture, possible-duplicate checking and report lookup with an existing bugAgent license. This MIT-licensed package does not grant a bugAgent service license or change service entitlements.

Unpublished tester preview: 0.1.0-preview.2. The production endpoint https://mcp.bugagent.com/mcp/capture is live. The package is not submitted, approved or published in the OpenAI directory. Full authenticated ChatGPT OAuth end-to-end testing remains UNVERIFIED.

Implementation and launch status

Production v19.18 release verification records successful protected-resource metadata checks, HTTP 200 discovery of the five capture tools, and HTTP 401 for an anonymous tool call. Those checks establish endpoint availability and an authentication boundary, not successful sign-in or an authenticated report flow. They were not rerun during this documentation update.

The five-tool interface, report_id UUID, inputs, defaults, pagination and retry behavior are documented in the implementation-verified contract. The pagination contract is confirmed, not provisional.

Directory launch remains blocked on full hosted OAuth/reviewer verification and publisher submission access. Listing assets and the eight proposed review cases remain checklist gates. Endpoint discovery, local smoke, package validation and local installation are not proof of an authenticated end-to-end pass or publication.

Scope

One skill uses five restricted tools: capture_get_profile, capture_list_projects, capture_search_reports, capture_get_report and capture_create_report. It resolves workspace/project scope, searches for possible duplicates, shows a sanitized draft, and asks for explicit approval before creation. The read-only profile tool returns the stable identity for the authenticated connection, not a workspace selector. Lookup and search do not write.

There are no attachment uploads in v1. The skill can help describe a screenshot, but cannot store its image. Use a returned ticket link to upload in the ticket UI. Administration, deletion, automation and test-case creation are outside this MVP.

Local discovery

The repository's .agents/plugins/marketplace.json points to ./plugins/bugagent relative to the repository root. It supports local discovery, not public directory approval or automatic installation. Use the desktop repo-marketplace workflow to test before directory submission; full ChatGPT OAuth remains unverified. Never paste credentials into this package or chat. Use the host's secure connection UI.

Tester instructions are in plugins/bugagent/TESTING.md in the source checkout. That repository-only guide is not included in the ZIP's fixed file allowlist. This internal tester preview requires a dedicated account provisioned by the test owner. Public source and an existing license do not automatically grant external users access to this tester program. Use only synthetic data in the TestLauncher workspace's Test Bed project. Do not test customer projects or the production bugAgent project. No staging access or public staging endpoint is implied.

Do not substitute the general bugAgent MCP endpoint if the preview is unavailable. Offline drafting remains possible; no successful capture should be claimed.

Offline validation and build

From the repository root, with Node.js 22 or newer and no dependencies:

node --test scripts/bugagent-plugin.test.mjs
node scripts/bugagent-plugin.mjs validate
node scripts/bugagent-plugin.mjs build
node scripts/bugagent-plugin.mjs validate-zip

Output: plugins/bugagent/dist/bugagent-preview.zip (ignored by Git). Build uses an explicit file allowlist, fixed ZIP timestamps/modes/order and no compression. The ZIP root contains plugin.json, mcp.json, one skill and public documentation. No marketplace catalog, build scripts, repository source, credentials or local configuration enter the ZIP. Symlinked inputs are rejected.

Validation checks this package's deliberately narrow format and common sensitive content, not the full upstream schema or all possible secrets. ZIP validation requires exact equality with the canonical build from the current validated source; it is not a general-purpose ZIP validator. Human public-content review is mandatory. No command contacts the MCP endpoint. Passing checks proves package consistency, not runtime behavior, endpoint readiness, security certification or marketplace approval.

For an explicit network check against the published portable JSON schemas:

node scripts/bugagent-plugin-schema.mjs

This command fetches only the two declared Agent Plugins schemas and validates plugin.json and mcp.json with a dependency-free evaluator for their current keyword set. Unknown keywords fail closed. It prints schema SHA-256 hashes for review; it is not a general JSON Schema implementation. OpenAI extension semantics are checked separately by the local package validator, since the portable schema allows host-defined extension objects.

See the implemented interface, the submission checklist, and proposed review cases. All eight review cases are unexecuted.

Format references

Official packaging and submission documentation was fetched before implementation on 2026-10-01. The package uses the portable root manifest and MCP format. The OpenAI interface includes verified public URLs; registered server IDs and unverified submission metadata are omitted.

Verified public listing destinations

On 2026-10-01, HTTP GET returned 200 for the website, support documentation, privacy policy, and terms. The support document includes a support section and public support email. This verifies the public pages, not the capture endpoint or legal sufficiency.

Listing descriptions describe intended functionality without preview/trial/demo wording. That wording change is not a readiness claim: keep this package out of submission until the authenticated hosted workflow, account identity, review cases, and listing assets have been verified. The README and submission checklist remain the source of release status.

Package source is covered by MIT. Hosted bugAgent access remains subject to its existing license and service terms.