Update create-safe-output-type custom agent to document handler manager architecture #9026
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The custom agent guide referenced an outdated architecture where safe outputs used individual jobs (
buildCreateOutputIssueJob), but the codebase now uses a handler manager that dispatches messages to factory functions within a consolidated job.Changes
Step 7: Handler Implementation
main(config)returns a message processing functionStep 10: Handler Manager Integration
HANDLER_MAPaddHandlerManagerConfigEnvVar()hasHandlerManagerTypesSuccess Criteria & Pitfalls
actions/setup/js/vspkg/workflow/js/)Architecture
The handler manager loads factories once, then dispatches messages to the returned handlers, enabling shared state and centralized temporary ID resolution across all safe output types.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.