Problem
When GitHub issues are created from within an Ambient session (e.g., bug reports, feature requests filed by the AI agent on behalf of the user), the issues contain no traceability metadata. If the team needs additional context or wants to contact the reporter, there's no way to trace the issue back to the session or user.
The GitHub token used by sessions has create-only permissions (no edit, no comment), so metadata cannot be added after the fact.
Examples
Issues #1070 and #1071 were filed from this session but contain no session or user context.
Proposed Solution
When issues are filed from a session, automatically include a metadata footer in the issue body:
---
**Session**: <SESSION_ID>
**Filed by**: <USER_ID> (<USER_EMAIL>)
**Project**: <AGENTIC_SESSION_NAMESPACE>
This could be:
- A convention enforced by workflow instructions (agent always appends metadata)
- Built into the platform (intercepting GitHub API calls from sessions and injecting metadata)
- A helper tool/MCP server that wraps
gh issue create with automatic metadata injection
Alternative
If the platform already tracks which session created which GitHub API calls on the backend, this may not be needed — but that tracking mechanism is not visible to session users today.
Session: session-f4a5410f-fb3c-453c-895b-ae66bdce1dbe
Filed by: ometelka (ometelka@redhat.com)
Project: ols
Problem
When GitHub issues are created from within an Ambient session (e.g., bug reports, feature requests filed by the AI agent on behalf of the user), the issues contain no traceability metadata. If the team needs additional context or wants to contact the reporter, there's no way to trace the issue back to the session or user.
The GitHub token used by sessions has create-only permissions (no edit, no comment), so metadata cannot be added after the fact.
Examples
Issues #1070 and #1071 were filed from this session but contain no session or user context.
Proposed Solution
When issues are filed from a session, automatically include a metadata footer in the issue body:
This could be:
gh issue createwith automatic metadata injectionAlternative
If the platform already tracks which session created which GitHub API calls on the backend, this may not be needed — but that tracking mechanism is not visible to session users today.
Session: session-f4a5410f-fb3c-453c-895b-ae66bdce1dbe
Filed by: ometelka (ometelka@redhat.com)
Project: ols