This week half of Show HN is inventing a format for authorable agent skills — and the loudest open question is: how do you trust a skill an agent can author? Forge just shipped the governed answer. Any org can now write its own agent skills at runtime — org-scoped, role-gated, live to a real multi-agent fleet, with no conductor rebuild.
Should an AI assistant get co-author credit in your git log? Developers are actively fighting about it. This month Forge picked a side across the whole fleet: we dropped Co-Authored-By: Claude everywhere and adopted Assisted-By: instead — and we make external PRs follow the target project's own policy. Here's the reasoning, and why commit provenance is a supply-chain question, not a cosmetic one.
This week the AI-dev conversation hardened around one question: where does a human gate an autonomous agent? Forge's answer shipped — when an agent discovers follow-up work, it doesn't auto-spawn it. The work waits at a human Approve gate. Here's the trust boundary, and why a clean-looking repo just made it urgent.