An Issues Tab Is Not a Laravel Package Ticket
GitHub Issues are off on most Laravel packages. The ticket is a pull request that documents the bug, with a named owner. laravel/framework Issues stay on.
Shinjae Kang
Read#Coding-Agents
15 posts tagged with #Coding-Agents
Shinjae Kang
Read
Name the Copilot Surface Before You Trust the Exclusion List
A Copilot content exclusion is a policy row. App and CLI now honor it. Agent chat in the editor still can. Name the owner of the list and of the surface before you call a secret recovered.
Shinjae Kang
Read
Leave Copilot Approve Off
GitHub now prints a ready-to-approve assessment on every Copilot review. That line is a note. The admin switch that turns it into a required approval is off by default. Keep it off.
Shinjae Kang
Read
Five Things I Refused This Week
A ranked cheat-sheet of five desk rules from this week: who pins the model, what .gitignore does not lock, who merges, who retries, and who still reads the diff.
Shinjae Kang
Read
I Do Not Let a Coding Agent Pick Its Own Model
The agent that writes the diff does not choose the model for that pull request. A named human pins the model before the session starts. Auto is a vendor default, not an owner.
Shinjae Kang
Read
I Do Not Give a Coding Agent Merge Rights
A coding agent may open the pull request. A named human still owns the merge click. Treat GitHub agent merge and auto-merge as opt-in shortcuts, never as the default.
Shinjae Kang
Read
Empty Tool Output Is Not Success Until the Harness Says Interrupted
An interrupted MCP tool in a headless coding-agent session used to look finished. Treat empty completion as a bug until the harness asserts an interrupted error.
Shinjae Kang
Read
Building a Background Agent Recovery CLI: The Three-Gate Check
Chat said done is not recovered. I wait for a file on disk, a job log that names why the run stopped, and one fail-once restart from the last good commit.
Shinjae Kang
Read
The Schema Change an AI Coding Agent Cannot Safely Guess
A generated migration that runs locally is not a production contract. Before an AI coding agent rewrites columns, require expand steps, dual-read boundaries, backfill evidence, worker compatibility, and an explicit rollback decision.
Shinjae Kang
Read
Audit the resume boundary: verify a coding agent from repository evidence
A practical way to decide whether a resumed coding-agent run is safe to continue: inspect local evidence, enforce command gates, review the diff, preserve test logs, and make rollback cheap.
Shinjae Kang
Read
A Coding-Agent Policy Is Change Control, Not a Settings File
Treat repository instructions for coding agents as a governed change-control system: owned, reviewed, scoped, evidenced, and reversible.
Shinjae Kang
Read
Grok 4.5 Is a Coding-Agent Moment Only If It Survives the Harness
Grok 4.5 is now available on the xAI API with pricing and reasoning controls that make developers pay attention. The real adoption test is whether it survives your local coding-agent harness.
Shinjae Kang
Read
The AI Coding Agent Arms Race — Why Model Portability Matters More Than Benchmarks
A current guide to keeping AI coding-agent instructions, verification, approval, and rollback in the repository so a tool or model change does not rewrite release control.
Shinjae Kang
Read
Long-Running AI Agents — From Demos to Production
A long-running coding agent can stay green after it changes directory. Production still needs a sandbox that survives /cd, a budget that counts nested work, and a human who owns both.
Shinjae Kang
Read
GLM 5.2 Just Became the Best Open-Weights Model — Here's What That Means
Z.AI's GLM 5.2 (744B MoE, 1M context, MIT license) tops open-weights benchmarks and runs coding agents at frontier level. Full breakdown.
Shinjae Kang
ReadAlso see: #Coding-Agents #Laravel #Change-Control #Vue #Code-Review