Complete setup first, then let the Agent work in your project.

QiyanAgent V3.5 brings models, web access, environments, database connections, and Skills together in Settings. After a project is open, the Main Agent and specialist Agents share the project context and show their process and results in the center execution area.

Applies to QiyanAgent V3.5. Last updated: September 14, 2026.

Before You Start

  • Prepare at least one usable model-service configuration. Cloud models usually require an API key; fill in local Ollama or vLLM details as required by the service.
  • For web search, prepare a Bocha or Zhipu Search API key; web access is optional.
  • If you will connect to MySQL, Doris, or Oracle, prepare a read-only or read-write account and confirm that the database address is reachable.
  • Enter API keys, database passwords, and other secrets only in the relevant settings; do not put them in project files or task prompts.
Model setup steps: open provider configuration, enter the endpoint and test the connection, configure available models and capabilities, then save the settings. The API key is masked in the screenshot.
Model selection steps: open the current model selector in the task input area, choose Auto or a configured model, and select a vision or text model for the task.

Steps

  1. Click Settings in the toolbar and switch to Models.
  2. On a provider card, click Get Models or Configure, enter the OpenAI-compatible endpoint and API key, and complete Connection Test.
  3. Expand a provider card and enable the models for this task. To connect another service, use Custom OpenAI-Compatible Model and enter its endpoint, model name, context window, and maximum output tokens.
  4. Click Set as Default or reorder enabled models. The first enabled model is the default, and you can switch among enabled models from the conversation input after sending.
  5. Save the configuration before starting a task. Only models declared by the catalog as vision-capable accept JPEG, PNG, GIF, or WebP images; custom models are treated as text-only.

Web Search API Key

Web search is optional. When enabled, the Agent can retrieve public web information, but you should verify results against sources, dates, and the task definition.

Web access setup steps: enable web search, choose a provider, enter the Search API Key, complete the test, and save the web settings.

Steps

  1. Switch to Web Access and enable Web Access.
  2. Choose Bocha or Zhipu in Provider and enter the Search API Key. The provider supplies the endpoint; do not rewrite it manually.
  3. Complete Connection Test, set the Result Limit to 1–20, and click Save Web Access Settings.
  4. State the search topic, time range, and source requirements in the task. Turn web access off when it is not needed to avoid irrelevant searches.

Environment Check

The Environment page checks Python, Node.js, PowerShell, CMD, Stata, R, and LibreOffice. Python, Node.js, and LibreOffice can be prepared through the software guide; configure Stata, R, and other tools for the tasks that need them.

Environment check steps: recheck the runtime, confirm Python, Node.js, and other tool statuses, customize paths when necessary, and check Stata, R, and other tools as needed.

Steps

  1. Click Settings in the toolbar, switch to Environment, and click Recheck.
  2. First confirm that Python, PowerShell, and CMD are available. Check the relevant tools when a task needs JavaScript, document conversion, Stata, or R.
  3. If detection is incorrect, use the selector on the relevant row to specify the Python interpreter, Node.js, Stata executable, or R interpreter.
  4. Configure environments according to task needs rather than installing unrelated tools just to pass the check. Environment status affects the available tool range.

Remote Database Connections

To query external data sources, create a MySQL, Doris, or Oracle connection in Database Connections and choose read-only or read-write access. The Remote Database Agent uses these connections in the current project context.

Database connection steps: create a connection and choose the database type, enter the host, port, and account, set read-only or read-write access, then test and save the connection.
  1. Open Settings → Database Connections, click New Connection, and enter the address, port, database, username, and password.
  2. Prefer Read-only. Choose Read-write only when writing is necessary and backups and access controls are in place.
  3. Complete the connection test and save. In read-write mode, each SQL statement is written to the project sql/remote_db_history/ before execution; it will not run if saving fails.

Acceptance Checks

At least one model has passed connection testing and is enabled, web access matches your needs, the environment check is complete, and any remote database connection has passed its test. After a project opens, the left side shows the project and specialist workspaces, the center shows Agent execution, and the file workspace can be opened on the right. Manage Skills under Settings → Skills.

Fix Garbled Digital Signature Text

If Windows 11 SmartScreen or the digital signature window shows question marks, square boxes, or garbled publisher text, UTF-8 global language support is usually disabled. File integrity should still be checked with the SHA256 and MD5 checksums on the download page.

Enable “Use Unicode UTF-8 for worldwide language support” in Windows 11 language and region settings, then restart before running the installer again.
  1. Open Windows 11 Settings, then go to Time & language and Language & region.
  2. Find “Beta: Use Unicode UTF-8 for worldwide language support” and turn it on.
  3. Restart Windows when prompted, then run the QiyanAgent installer again.