Topic starter
20/08/2026 6:10 pm
TL;DR: AI coding sessions are ephemeral, so plans, decisions, and review context often disappear unless teams persist them somewhere durable, according to Fiddler’s GitHub workflow guide. Turning GitHub issues and pull requests into the shared record creates an auditable handoff model for AI agents, but it also raises new governance questions about identity, attribution, and review accountability.
Editorial analysis by NHI Mgmt Group, based on content published by Fiddler: “Using GitHub to Integrate AI Agents into Your Dev Workflow”.
Key questions
Q: How should teams preserve AI agent context across coding sessions?
A: Use a durable task artefact such as a GitHub issue or pull request to store the plan, open questions, and review feedback.
Q: Why do AI agent workflows need provenance and attribution?
A: Because humans and models can both comment on the same task, teams need a way to tell which recommendations came from an agent and which came from a person.
Q: What are the signs that an AI agent has too much workflow context?
A: Common signs include agents repeatedly searching across unrelated files, pulling in tickets that are not relevant to the change, citing vague summaries, or making edits that satisfy code mechanics but miss business intent.
Practitioner guidance
- Define GitHub as the task record Require AI-assisted implementation work to record plans, open questions, and decisions in the issue or pull request that owns the branch.
- Persist model-generated output with attribution Add a consistent footer or metadata marker to agent comments so reviewers can distinguish machine output from human feedback.
- Reload context from the issue before resuming work Train teams to ask the agent to load the saved issue context after a restart, branch switch, or handoff instead of rebuilding the plan from scratch.
Bottom line: Ephemeral AI coding sessions create a governance gap because the reasoning behind code changes can vanish even when the code itself is preserved.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
20/08/2026 6:46 pm
Persistent agent context is now part of software governance, not just workflow design. AI-assisted development creates decisions that outlive the session in which they were made, so the real control question is where those decisions are stored. If the context sits only in an ephemeral conversation, the organisation loses the ability to reconstruct intent, review history, and handoff state. Practitioners should treat persistence as a governance boundary for agent-assisted change.
A few things that frame the scale:
- 62% of organisations are at least experimenting with AI agents, but only 23% have scaled one into a single business function, according to McKinsey's 2025 State of AI survey.
A question worth separating out:
Q: What should teams do when AI-generated plans need human review?
A: Keep the review in the same issue or pull request where the work lives, and ask the agent to load the existing comments before responding. That lets reviewers see the original plan, the objections, and the updates together, instead of forcing a disconnected review loop across separate tools.
👉 Read our full editorial: GitHub issue persistence for AI agent workflows and auditability