About 187 wordsLess than 1 minute
To ensure clear traceability of operation sources, Cloud Native Build strictly distinguishes between user UI interactions and automated interactions (such as calling OpenAPI during a pipeline process).
In Cloud Native Build, automated interactions are collectively referred to as NPC behaviors, and the actor's identity is uniformly displayed as NPC.
Usage
You can directly mention @NPC in the Markdown editor to immediately trigger the pipeline corresponding to the NPC event and execute natural language commands. For example:

Interface Display
Taking Issue Commenting as an example, the NPC appears as follows:

Work Mode
Users with Repository Developer permissions or higher can enable Work Mode via the checkbox in the comment area. Once enabled, the NPC operates with code editing permissions, capable of actions such as pushing code, creating branches, and submitting merge requests.

Common "NPC" Scenarios
If you see an entry tagged with NPC, it usually originates from the following sources:
- Automated Tools: Such as comments added via pipeline builds or NPC auto-replies.
- System Automated Processing: Such as pipelines triggered by scheduled tasks.