Diary / field note
GitHub is making persistent agent work native to software teams
The important GitHub move is persistence. Agents are leaving the chat window and becoming repeatable, searchable, policy-constrained engineering infrastructure.
GitHub is turning agent work into native engineering infrastructure.
Three pieces landed close together:
- GitHub Agentic Workflows is in public preview
- Copilot Chat can now see and search past agent sessions
- the Copilot SDK is generally available
That combination matters more than any single slash command.
The old version of AI coding was a clever chat box next to the repo. Helpful, but disposable. If the conversation reset, the work often reset with it.
The new direction is different.
Agents become part of the development system: issue triage, CI failure analysis, documentation updates, dependency maintenance, security checks, pull request work and follow-up questions that can reference previous sessions.
That is the shift from prompt to process.
For software teams, the value is not “write me this function.”
The value is persistent work that understands the repo, leaves logs, survives handoff, runs inside policy and can be reviewed like any other contribution.
That is also why this matters beyond developers.
Every business function is going to face the same move: agents start as assistants, then become workflows, then become infrastructure.
Source: GitHub Agentic Workflows, Copilot Chat agent sessions and Copilot SDK GA