Realtime multiplayer, automation, and you! — Idan Gazit, GitHub

An unattended maintenance agent needs permissions enforced outside its written task instructions. In GitHub's Agentic Workflows presentation, a Markdown playbook describes an upgrade-checking job, while separate configuration specifies its tools, network access and permitted outputs. The playbook is compiled into a workflow that runs through GitHub Actions.

The example allows the agent to propose one code change for review, or to do nothing when there is no useful update. Limiting the output bounds how much noise the automation can create, while explicit network rules constrain where it can connect. The design separates the agent's judgment about maintenance work from the authority granted to carry it out.

“if you're prompting the guardrails at the agent, you're effectively letting the fox loose in the henhouse”

Idan Gazit

“If an agent can know a secret, that secret, you need to treat it as if it's already been compromised.”

Idan Gazit

“automations that run in the background while you sleep, that's the ballgame”

Idan Gazit

“the markdown is the source code. The YAML is like a compiled artifact. You never look at it.”

Idan Gazit

“Turns out that the hands-on keyboard typing part is 5% of the time. Now, AI has to help me with the other 95%.”

Idan Gazit