Creating an issue currently requires driving the browser UI with an authenticated session. That makes it hard for agents and automation to file well-scoped issues even when the user has explicitly asked for one.
Useful improvements:
- Provide a documented API or CLI command to create issues with a normal auth token.
- Return the created issue number and URL.
- Support idempotency or duplicate detection for repeated agent attempts.
- Make the new-issue page redirect to the created issue after submit, or otherwise expose the created issue URL.
- Keep the browser form, but avoid requiring UI automation for machine-created issues.
This came up while trying to file an importer feature request from an agent. The public issue list was easy to read, but creating the issue required borrowing an already logged-in browser session.