Use qoder-helper for product questions, app configuration, issue diagnosis, and extension discovery and installation.
Need to find a feature, adjust a setting, or resolve an issue? Select qoder-helper in a local task in the Qoder desktop app and describe what you need. It can explain how features work, change settings, help investigate problems, and find and install extensions.
Available actions depend on the tools and permissions in your app version. For setting changes or extension installation, specify the target and scope, and review any operation confirmation before allowing it.
Ask qoder-helper where to find a feature, how to use it, or how Skills, plugins, and MCP connectors differ.
You can also ask how Skills, MCP connectors, and plugins differ, or what a setting means. Specify whether you use standalone Qoder, Qoder IDE, or CLI so that instructions for different products are not mixed. See Skills for the full skill management workflow.
To check the current theme, font size, or other settings, ask qoder-helper to read and report their values. For example:
To change a setting, describe the result you want, such as âSwitch the app to dark mode and make the text larger.â After the change, return to the relevant interface to check the effect. If the assistant cannot read or change the setting, use Settings.
For loading failures, connection failures, or settings that do not take effect, include the product version, operating system, time, reproduction steps, observed behavior, and error message. For example:
qoder-helper can use current state, configuration, and accessible logs to investigate the cause. For log inspection, specify the time and affected feature. Review the proposed fix, then state which settings may be changed and the scope of the change. Repeat the original operation to check whether the issue is resolved. See Troubleshooting if the cause remains unclear.
Check whether the answer or action meets your request:
| Capability | Supported actions | Example request |
|---|---|---|
| Product questions | Explains features, options, entry points, and how concepts such as Skills, plugins, and MCP are used. | âHow do Skills and plugins differ? Which should I use?â |
| App settings | Finds, reads, and changes exposed settings, such as themes, fonts, and notifications; resets settings that support restoring defaults. | âSwitch the app to dark mode and make the text a little larger.â |
| Find and install Skills / plugins | Searches the extension marketplace and installs selected Skills or plugins; also imports local ZIP packages and enables installed plugins. | âFind a Skill for code review and explain its purpose and installation requirements. Do not install it yet.â |
| Connect and manage MCP connectors | Checks connection state and configuration; adds, edits, enables, disables, or deletes user-defined connectors, or retries connections. | âCheck which connectors are disconnected and try reconnecting them.â |
| Create and manage custom Agents | Prepares a creation draft for a new Agent; views, edits, enables, disables, archives, or restores existing Agents. | âPrepare a draft for a code review assistant that focuses on edge cases.â |
| Log-assisted diagnosis and configuration-level fixes | Uses accessible logs, configuration, and error information to analyze causes and attempts fixes within available permissions and tool support. | âThis connector keeps failing to start. Investigate the cause and first explain which configuration changes you recommend.â |
Ask for product help
Ask qoder-helper where to find a feature, how to use it, or how Skills, plugins, and MCP connectors differ.
- Start a local task in Qoder.
- Type
/in the task input and select qoder-helper. - Confirm that the qoder-helper skill chip appears, then add your question.
- Send the message and review the answer and its sources. Continue in the same task to ask follow-up questions.
Query current settings
To check the current theme, font size, or other settings, ask qoder-helper to read and report their values. For example:
Describe a problem
For loading failures, connection failures, or settings that do not take effect, include the product version, operating system, time, reproduction steps, observed behavior, and error message. For example:
Verify the result
Check whether the answer or action meets your request:
- After a product question: Check the product and version the answer applies to. Ask follow-up questions in the same task if anything is unclear.
- After reading or changing settings: Review the returned values. After a change, check the effect in the relevant interface.
- After installing an extension: Check the installed name and select the skill in a new task to try it. The marketplace display name may differ from its invocation name. See Skills for usage steps.
- After generating an Agent draft: Select Continue configuration, check the model, permissions, and extensions, then select Save Agent. The Agent is created only after saving succeeds. See Custom agents for the full workflow.
- After troubleshooting: Retry the original task after applying the suggested fix. If the issue persists, provide the new behavior and error message to continue the investigation.
/ menu reports a loading failure, close and reopen it, then search again. If it remains unavailable, describe your product question directly and check your network and skill availability.