Realtime multiplayer, automation, and you! — Idan Gazit, GitHub
GitHub Next’s prototypes move coding agents from personal chat into governed background workflows and shared cloud workspaces that can act on team conversation.
Agentic Workflows turns plain-English tasks into Markdown playbooks that compile to GitHub Actions, with permissions in front matter. Ace gives each session a repository branch in a **cloud micro-VM** and can act on shared conversation history.
Use **Markdown as workflow source** for recurring maintenance such as dependency upgrades, then constrain what agents may read, write, and access. For collaborative work, preserve team discussion as context so people do not have to restate decisions to an agent.
Agentic Workflows turns plain-English tasks into Markdown playbooks that compile to GitHub Actions, with permissions in front matter. Ace gives each session a repository branch in a **cloud micro-VM** and can act on shared conversation history. Use **Markdown as workflow source** for recurring maintenance such as dependency upgrades, then constrain what agents may read, write, and access. For collaborative work, preserve team discussion as context so people do not have to restate decisions to an agent. Agentic Workflows was available in the talk, while **Ace remained a technical preview target**. The demos show a direction for automation and multiplayer development, not evidence about reliability at production scale.
This combines two previously separate tool directions: declarative, permission-scoped automation for repeatable repository work and conversation-aware cloud sessions for collaborative development. It makes Markdown a reviewable workflow boundary and shared discussion a context source, while narrowing confidence in the multiplayer vision because Ace was still a preview and no production-scale reliability evidence is supplied.