Use specialized Agents supplied by installed extensions.
A custom Agent is configured for a focused role and can work with its own instructions, context, and allowed tools. Use one when a larger task benefits from a specialist—for example, a code reviewer or test investigator—while the main Agent coordinates the overall result.
Agents can be supplied by installed Plugins. Before use, review the parent Plugin and its other components under Extensions → Plugins → Installed.
In a task:
To create a local extension that contains an Agent, open Extensions → Plugins, select Add Plugins, and choose Create with Qoder. Review the generated Plugin and keep tool access limited to what the role needs.
To import an existing package, choose Upload Plugin and select its ZIP file. Imported packages are kept on this device.
Give the Agent:
Start with a small task and confirm that the intended Agent appears in the execution. If it does not appear in the
Find and select an Agent
Agents can be supplied by installed Plugins. Before use, review the parent Plugin and its other components under Extensions → Plugins → Installed.
In a task:
- Enter
/in the task input. - Find the Agent in the suggestion list.
- Select it, then describe the task, scope, constraints, and expected output.
- Review any access request and the Agent's result before applying changes.
Create an Agent package
To create a local extension that contains an Agent, open Extensions → Plugins, select Add Plugins, and choose Create with Qoder. Review the generated Plugin and keep tool access limited to what the role needs.
To import an existing package, choose Upload Plugin and select its ZIP file. Imported packages are kept on this device.
Write a useful task
Give the Agent:
- a clear goal and completion criteria;
- the workspace or files it may use;
- constraints, such as read-only review or no dependency changes;
- the expected output format;
- any checks it must run before returning.
Verify and troubleshoot
Start with a small task and confirm that the intended Agent appears in the execution. If it does not appear in the / suggestions, verify that the parent Plugin is installed and enabled. If the result is too broad, make the task scope and acceptance criteria more specific rather than granting additional access.