# Laravel is replacing issue-first bug reports with AI-assisted pull requests across most packages Taylor Otwell says GitHub Issues are now disabled on most Laravel package repositories and users who hit a bug should describe it to a coding agent and open a pull request, even when the first fix is imperfect. The main `laravel/framework` repository still keeps Issues enabled. The change moves maintenance work earlier in the contribution funnel: instead of filing a report and waiting for a maintainer to reproduce it, package users are being asked to arrive with an executable patch candidate. It is a real workflow experiment, but Otwell's prediction that this becomes the norm should remain a founder/maintainer view rather than an industry fact. - Status: Active - Published: 2026-09-06T14:37:23+12:00 - Updated: 2026-09-06T14:37:23+12:00 - Categories: Artificial Intelligence, Web Development, PHP, AI Coding, Frameworks, Developer Tools - Tags: bug reports, Coding agents, Laravel, open-source maintenance, pull requests - Canonical HTML: https://beyondthe.news/dossiers/laravel-packages-disable-issues-ai-assisted-pull-requests ## What changed Laravel creator Taylor Otwell said on September 4, 2026 that he disabled GitHub Issues on most Laravel open-source package repositories. When users hit a bug, his requested workflow is to describe it to a coding agent and open a pull request instead of first filing an Issue. Otwell explicitly says an imperfect first patch is acceptable because the pull request can document the failure and give maintainers code to review. He later clarified that the central `laravel/framework` repository still has Issues enabled; examples such as Socialite are among the package repositories using the new approach. ## Why it matters Coding agents are changing more than how code is written: they can alter what maintainers expect from bug reporters. Asking for a patch first can reduce reproduction and triage work for a small maintainer team and turn a bug report into something directly testable. It can also raise the contribution barrier for users who cannot produce a safe patch, and AI-generated changes still require maintainer review. The significant development is the contribution-policy experiment itself, not a claim that issue trackers are obsolete. ## The change applies to most packages, not the main framework repository Otwell clarified that `laravel/framework` still keeps GitHub Issues enabled. The new policy targets package repositories where he says issue volume was relatively low, including examples such as Socialite. ## A pull request becomes the bug report Users are being encouraged to give a coding agent the failure context and open a PR with the attempted fix. Even when the code is incomplete, the diff, tests and PR discussion can give maintainers a more concrete starting point than a prose-only report. ## Agent output does not remove maintainer review The workflow shifts effort toward contributors and coding agents but does not establish that generated patches are trustworthy. Maintainers still need reproduction, tests, security review and architectural judgment before accepting a change. ## The broader claim is still an opinion Otwell has suggested this contribution pattern may become more common as coding agents improve. BTN treats that as his forecast, not evidence that other major open-source projects are following the same policy. ## Key details - Taylor Otwell says GitHub Issues were disabled on most Laravel open-source package repositories in early September 2026. - Users encountering bugs are asked to use a coding agent and open a pull request. - Otwell says an imperfect initial PR is acceptable as a starting point for maintainers. - The main `laravel/framework` repository still keeps Issues enabled. - The policy applies to package repositories such as Socialite rather than every Laravel repository. - The change is a maintainer workflow decision, not a GitHub platform requirement. ## Builder takeaways - If you maintain small open-source packages, test whether patch-first intake actually reduces triage time before removing a familiar support channel. - Require tests and clear reproduction notes even when contributors use coding agents; a generated diff is not evidence the root cause is understood. - Provide a path for security reports and bugs from users who cannot safely generate a patch. - Measure whether closing Issues changes contributor participation, duplicate reports and maintainer workload rather than assuming agent-assisted intake is automatically better. ## What to watch - Whether Laravel keeps the policy after enough real package bugs pass through it. - Whether issue volume moves to discussions, social channels or low-quality pull requests instead of disappearing. - Other open-source maintainers adopting or rejecting patch-first agent workflows. - New GitHub or coding-agent tooling that turns reproduction reports into governed PR workflows without removing issue intake. ## Uncertainties - There is not yet enough public data to know whether the policy reduces total maintainer workload. - Otwell's statements describe Laravel's chosen workflow; they do not establish a general open-source trend. - Repository-level settings may change as maintainers learn from the experiment. ## Sources - [Taylor Otwell Disabled GitHub Issues on Most Laravel Packages](https://laravel-news.com/taylor-disabled-github-issues) — Laravel News · specialist reporting · 2026-09-04T00:00:00+12:00. Reports and quotes Otwell's new package-maintenance workflow and his clarification about the main framework repository. - [Taylor Otwell public post on package Issues](https://zamantika.com/de/taylorotwell/status/2095516796748996843) — Taylor Otwell · founder statement · 2026-09-04T00:00:00+12:00. Mirrored public statement describing the AI-assisted PR-first policy; claims about future norms remain attributed.