FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Restoring project custom-agent loading
Rebuilding the resume boundary so saved trust is retained while external connections stay disabled
Purpose
The custom-agent recognition failure was caused not by the model but by resume startup also suppressing the project's trust configuration. The project settings had to load without re-enabling unnecessary external connections.
Implementation
The blanket option that ignored user configuration was removed so saved project trust could take effect. Before resume, configured MCP names are now enumerated and each safe name is disabled individually. Enumeration failure or an unsafe name stops execution before resume begins.
Existing boundaries that disable notifications, hooks, plugins, network access, and approval requests were preserved, separating configuration loading from connection suppression. Tests fixed the behavior for enumeration failures, unsafe names, argument generation, and failure paths that must not resume.
Instead of ignoring all user configuration, the Runner preserved project trust and enumerated configured MCP servers for individual disabling. Enumeration or name-validation failure stops startup.
Rendering diagram…
What was confirmed
Verification results
Resume was confirmed to proceed only after configuration enumeration and name validation succeeded.
A real diagnostic start recognized the project custom agent and began with the requested role.
At the cutoff, configuration loading was repaired. A subsequently discovered subagent-resume constraint was separated into another Activity.
Basis for completion
This scope was complete when project settings loaded with external connections still disabled and a real startup recognized the custom-agent role.