diff --git a/nginx.conf b/nginx.conf index 66bfa90ea4..3e75106487 100644 --- a/nginx.conf +++ b/nginx.conf @@ -836,6 +836,11 @@ server { rewrite ^/limits$ /account/limits redirect; rewrite ^/proxy/unblocker-proxy$ /proxy/unblocker redirect; + # Qoder surfaces consolidated onto one page (#2934). + rewrite ^/integrations/qoder-cli$ /integrations/qoder permanent; + rewrite ^/integrations/qoder-ide$ /integrations/qoder permanent; + rewrite ^/integrations/qoder-work$ /integrations/qoder permanent; + # Soft-landings for deleted URLs (better UX than a 404) rewrite ^/platform/integrations/airtable/console-integration$ /integrations/airtable permanent; rewrite ^/platform/?$ / permanent; diff --git a/sources/_partials/_apify-plugin-skill-prompts.mdx b/sources/_partials/_apify-plugin-skill-prompts.mdx new file mode 100644 index 0000000000..e9723adacf --- /dev/null +++ b/sources/_partials/_apify-plugin-skill-prompts.mdx @@ -0,0 +1,11 @@ +To run `apify-ultimate-scraper`: + +> Find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website. + +To run `apify-actor-development`: + +> Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. + +To run `apify-sdk-integration`: + +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. diff --git a/sources/_partials/_apify-plugin-skills.mdx b/sources/_partials/_apify-plugin-skills.mdx new file mode 100644 index 0000000000..5015eca9cb --- /dev/null +++ b/sources/_partials/_apify-plugin-skills.mdx @@ -0,0 +1,7 @@ +| Skill | Description | +| --- | --- | +| `apify-ultimate-scraper` | Extraction using existing Actors for multi-step scraping and lead-generation workflows. | +| `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | +| `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | +| `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | diff --git a/sources/platform/integrations/ai/index.mdx b/sources/platform/integrations/ai/index.mdx index 1f1fc94763..440f72509d 100644 --- a/sources/platform/integrations/ai/index.mdx +++ b/sources/platform/integrations/ai/index.mdx @@ -166,8 +166,22 @@ Chat and coding assistants you connect to Apify through the Apify MCP server or imageUrlDarkTheme="/img/platform/integrations/github-copilot-white.svg" smallImage /> + + ## By provider -See everything for a provider on one page: the [OpenAI hub](/integrations/openai) (ChatGPT, Codex, Agents SDK), the [Claude hub](/integrations/claude) (Claude Desktop, Claude Code CLI), and the [Qoder hub](/integrations/qoder) (Qoder CLI, Qoder IDE, QoderWork). +See everything for a provider on one page: the [OpenAI hub](/integrations/openai) (ChatGPT, Codex, Agents SDK), the [Claude hub](/integrations/claude) (Claude Desktop, Claude Code CLI), and the [Alibaba hub](/integrations/alibaba) (Qoder CLI, IDE, Desktop, QoderWork, Qwen Code, and QwenWork). diff --git a/sources/platform/integrations/ai/qoder/_category_.yml b/sources/platform/integrations/ai/qoder/_category_.yml index eaafc950c5..e924da24dc 100644 --- a/sources/platform/integrations/ai/qoder/_category_.yml +++ b/sources/platform/integrations/ai/qoder/_category_.yml @@ -1 +1 @@ -label: 'Qoder' +label: 'Alibaba' diff --git a/sources/platform/integrations/ai/qoder/images/qoder-cli/04-test.webp b/sources/platform/integrations/ai/qoder/images/qoder-cli/04-test.webp deleted file mode 100644 index c075e0e91c..0000000000 Binary files a/sources/platform/integrations/ai/qoder/images/qoder-cli/04-test.webp and /dev/null differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-ide/2-test.webp b/sources/platform/integrations/ai/qoder/images/qoder-ide/2-test.webp deleted file mode 100644 index 7c8d22421c..0000000000 Binary files a/sources/platform/integrations/ai/qoder/images/qoder-ide/2-test.webp and /dev/null differ diff --git a/sources/platform/integrations/ai/qoder/images/qoder-work/2-chat-list-tools.webp b/sources/platform/integrations/ai/qoder/images/qoder-work/2-chat-list-tools.webp deleted file mode 100644 index ba30e3c499..0000000000 Binary files a/sources/platform/integrations/ai/qoder/images/qoder-work/2-chat-list-tools.webp and /dev/null differ diff --git a/sources/platform/integrations/ai/qoder/images/qwen-code/1-marketplace.webp b/sources/platform/integrations/ai/qoder/images/qwen-code/1-marketplace.webp new file mode 100644 index 0000000000..a7c54c47e7 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qwen-code/1-marketplace.webp differ diff --git a/sources/platform/integrations/ai/qoder/images/qwen-work/1-skill-download.webp b/sources/platform/integrations/ai/qoder/images/qwen-work/1-skill-download.webp new file mode 100644 index 0000000000..bd2402af59 Binary files /dev/null and b/sources/platform/integrations/ai/qoder/images/qwen-work/1-skill-download.webp differ diff --git a/sources/platform/integrations/ai/qoder/index.mdx b/sources/platform/integrations/ai/qoder/index.mdx index 98a9011541..772f258839 100644 --- a/sources/platform/integrations/ai/qoder/index.mdx +++ b/sources/platform/integrations/ai/qoder/index.mdx @@ -1,37 +1,30 @@ --- -title: Qoder -description: Use Apify Actors with Qoder - install the Apify plugin in the Qoder CLI, the Qoder IDE, or QoderWork to discover, run, and build Actors as tools. -sidebar_label: Qoder -slug: /integrations/qoder +title: Alibaba +description: Use Apify Actors with Alibaba's Qoder and Qwen tools - install the Apify plugin in the Qoder CLI, IDE, Desktop app, or QoderWork, in Qwen Code, or in QwenWork. +sidebar_label: Alibaba +slug: /integrations/alibaba --- import Card from '@site/src/components/Card'; import CardGrid from '@site/src/components/CardGrid'; -Apify integrates with [Qoder](https://qoder.com), an agentic coding platform, through the Apify plugin. The same plugin installs in the Qoder CLI, the Qoder IDE, and QoderWork, and gives Qoder a way to call Apify Actors as tools and read their results. +Apify integrates with [Alibaba](https://www.alibabagroup.com)'s two agent families. [Qoder](https://qoder.com) is an agentic coding platform available as the Qoder CLI, IDE, Desktop app, and QoderWork. The Qwen family covers [Qwen Code](https://github.com/QwenLM/qwen-code), an open-source terminal coding agent, and [QwenWork](https://qwenwork.ai), a workplace AI agent for documents and knowledge work. Qoder and Qwen Code install the same Apify plugin, while QwenWork connects to the Apify MCP server and skills directly. Each gives the tool a way to call Apify Actors and read their results. ## What you can build - diff --git a/sources/platform/integrations/ai/qoder/qoder-cli.md b/sources/platform/integrations/ai/qoder/qoder-cli.md deleted file mode 100644 index c8370ea35d..0000000000 --- a/sources/platform/integrations/ai/qoder/qoder-cli.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -title: Qoder CLI integration -sidebar_label: Qoder CLI -description: Learn how to install the Apify plugin for the Qoder CLI to discover, run, and build Actors with the Apify MCP server, skills, and a routing agent. -slug: /integrations/qoder-cli ---- - -import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; - -[Qoder CLI](https://qoder.com) is an agentic coding tool that runs in your terminal. It reads and edits your codebase, runs commands, and completes multi-step development tasks. - -The [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) connects the Qoder CLI to Apify's library of [Actors](https://apify.com/store) and bundles: - -- The [Apify MCP server](/integrations/mcp) for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). -- An `apify` routing agent that picks the right tool or skill from a natural-language request. -- Five built-in skills for common workflows (see [Bundled skills](#bundled-skills) below). - - - -## Prerequisites - -- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one. -- [Qoder CLI](https://qoder.com) - installed and signed in locally. - -## Install the plugin - -You can install the plugin two ways: run the install command from the Qoder Marketplace, or add the plugin repository as a marketplace source in the Qoder CLI. - -### Install from the Qoder Marketplace - -1. Open the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521). Under **Qoder CLI**, copy the install command - it looks like `qodercli plugin install `. - - ![Apify plugin page on the Qoder Marketplace with the Qoder CLI install command](images/qoder-cli/01-marketplace-install.webp) - -1. Run the command in your terminal, then restart the Qoder CLI so the bundled MCP server registers. - -### Install from the plugin repository - -1. In the Qoder CLI, run `/plugins` to open the plugin manager. - -1. Open the **Marketplaces** tab and select **+ Add marketplace**. - -1. Paste the Apify plugin repository URL and press Enter: - - ```text - https://github.com/apify/apify-qoder-plugin - ``` - -1. Open the **Discover** tab. The `apify` plugin appears in the list. Press Enter to view its details. - -1. Review details, choose an install scope such as **Install (user scope)**, and press Enter. - - ![apify plugin detail with the install scope options and a trust warning](images/qoder-cli/02-install-plugin.webp) - -1. Run `/plugins reload` to apply the changes, then restart the Qoder CLI so the bundled MCP server registers. - -1. Open the **Installed** tab to confirm the `apify` plugin is enabled and its MCP server shows as connected. - -:::tip Restart the CLI so the MCP server registers - -The Apify MCP server registers when the Qoder CLI starts, not on `/plugins reload`. Whichever method you used, if `/mcp` shows no Apify server after installing, fully quit and reopen the Qoder CLI. - -::: - -## Authenticate to Apify - -The plugin bundles the Apify MCP server. Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data. - -1. Run `/mcp` to open the MCP server manager and select the **Plugin** tab to list plugin-provided servers. - -1. Select **plugin:apify:apify** to open its details. The status reads **needs authentication**. Select **Authenticate**. - -1. At the consent prompt, select **Yes** to open the Apify authentication page in your browser. - -1. The Qoder CLI waits for the browser callback. If the browser doesn't open automatically, copy and paste the full URL from the terminal into your browser (triple-click to select the whole URL). - - ![Terminal waiting for the browser callback and showing the fallback OAuth URL](images/qoder-cli/03-authenticating.webp) - -1. In the browser, review the permissions and allow access. A confirmation page tells you to close the window and return to the Qoder CLI. - -1. Back in the terminal, the server status changes to **ready** and the Apify tools become available. - -To see what the agent can call, select **View tools** on the server detail. The list shows each tool's annotations, such as read-only, destructive, or open-world. - -:::tip Session persistence - -The connection stays authenticated for future sessions. You can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). - -::: - -## Run your first prompt - -Describe what you want in natural language. The `apify` agent routes the request to the right tool or skill, so you don't need to name tools yourself. - -> List what Apify tools you have available. - -The agent lists the Apify MCP tools and skills it can call, grouped by purpose. - -![Qoder CLI listing the available Apify MCP tools and skills](images/qoder-cli/04-test.webp) - -To go further, ask it to find an Actor for a task: - -> Use Apify to find a good Actor for scraping Google Maps places. Show me the best option, its input requirements, pricing model, and what kind of dataset output it returns. Do not run the Actor yet. - -## Bundled skills - -| Skill | Description | -| --- | --- | -| `apify-ultimate-scraper` | Extraction using existing Actors for multi-step scraping and lead-generation workflows. | -| `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | -| `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | -| `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | - -These prompts route to specific skills. - -To run `apify-ultimate-scraper`: - -> Find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website. - -To run `apify-actor-development`: - -> Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. - -To run `apify-sdk-integration`: - -> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. - -## Troubleshooting - -### The Apify MCP server doesn't appear - -Run `/mcp` and check the **Plugin** list. If no Apify server is shown, the plugin was installed but the server hasn't registered yet. The server registers at startup, so fully quit and reopen the Qoder CLI, then check again. - -### The `apify` plugin is disabled - -Run `/plugins`, open the **Installed** tab, select the `apify` plugin, and enable it. Run `/plugins reload` to apply the change in the current session. - -### The `apify` agent isn't available - -Check which scope you installed the plugin in (user, project, or local) and make sure you're running the CLI from the matching directory. Then run `/plugins reload` or restart the CLI so it picks up the plugin. - -### Browser doesn't open, or OAuth fails - -If the browser doesn't open automatically, copy the OAuth URL from the terminal and open it in your browser. If that doesn't work, use an API token instead: copy your token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations) and set it before starting the Qoder CLI. - -```bash -export APIFY_TOKEN= -``` - -## Limitations - -- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. -- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. - -## Related integrations - -- [Qoder IDE integration](/integrations/qoder-ide) - Install the same plugin in the Qoder IDE -- [QoderWork integration](/integrations/qoder-work) - Upload the plugin in QoderWork -- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients - -## Resources - -- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes -- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs -- [Apify Store](https://apify.com/store) - Browse Actors you can run from the Qoder CLI diff --git a/sources/platform/integrations/ai/qoder/qoder-ide.md b/sources/platform/integrations/ai/qoder/qoder-ide.md deleted file mode 100644 index f82c7cdd14..0000000000 --- a/sources/platform/integrations/ai/qoder/qoder-ide.md +++ /dev/null @@ -1,109 +0,0 @@ ---- -title: Qoder IDE integration -sidebar_label: Qoder IDE -description: Learn how to install the Apify plugin in the Qoder IDE to discover, run, and build Actors with the Apify MCP server, skills, and a routing agent. -slug: /integrations/qoder-ide ---- - -import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; - -[Qoder IDE](https://qoder.com) is an agentic coding editor. It reads and edits your project, runs commands, and completes multi-step development tasks from a built-in chat. - -The [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) connects the Qoder IDE to Apify's library of [Actors](https://apify.com/store) and bundles: - -- The [Apify MCP server](/integrations/mcp) for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). -- An `apify` routing agent that picks the right tool or skill from a natural-language request. -- Five built-in skills for common workflows (see [Bundled skills](#bundled-skills) below). - - - -## Prerequisites - -- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one. -- [Qoder IDE](https://qoder.com) - installed and signed in. - -## Install the plugin - -You can install the plugin two ways: a one-click install from the Qoder Marketplace, or a manual import of the downloaded plugin package. The one-click install requires Qoder IDE v1.23.0 or newer. - -### One-click install - -1. Open the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521) and select **Qoder IDE** to install directly. - - ![Apify plugin page on the Qoder Marketplace with the Qoder IDE install option](images/qoder-ide/1-marketplace.webp) - -1. The Qoder IDE opens an install dialog. Review the plugin details and select **Install Plugin**. - -1. The **Apify** plugin appears under **Installed**. Make sure it's enabled. - -### Manual install - -If you're on an older version or prefer to install from a file: - -1. On the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521), under **For Human**, select the download icon to download the plugin package. - -1. In the Qoder IDE, open the account menu and select **Qoder Settings**. - -1. Select **Plugins**, then under **Custom** select **Import** and choose the plugin package you downloaded. - -1. The **Apify Qoder Plugin** appears under **Custom**. Make sure it's enabled. - -After installing with either method, select **MCP Server** to confirm the `apify` server is registered from the plugin. It connects to `https://mcp.apify.com` and exposes the Apify tools. - -## Authenticate to Apify - -Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data. - -On the first action that needs your account, the Qoder IDE opens a browser tab for the Apify OAuth flow. Review the permissions and allow access to finish signing in. The connection stays authenticated for future sessions, and you can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). - -## Run your first prompt - -Open the chat and describe what you want in natural language. The `apify` agent routes the request to the right tool or skill, so you don't need to name tools yourself. - -> What Apify tools do you have available? - -The agent lists the Apify MCP tools and skills it can call. - -![Qoder IDE chat listing the available Apify tools and skills](images/qoder-ide/2-test.webp) - -## Bundled skills - -| Skill | Description | -| --- | --- | -| `apify-ultimate-scraper` | Extraction using existing Actors for multi-step scraping and lead-generation workflows. | -| `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | -| `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | -| `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | - -## Troubleshooting - -### The Apify server doesn't appear under MCP Server - -Confirm the Apify plugin is enabled on the **Plugins** page, then open the **MCP Server** page again. If the server is still missing, restart the Qoder IDE so the plugin's MCP server registers. - -### Actor runs time out - -Increase the request timeout for the `apify` server on the **MCP Server** page. - -### Browser doesn't open, or OAuth fails - -If the browser doesn't open automatically, copy the OAuth URL shown by the IDE and paste it into your browser manually. If sign-in still fails, authenticate with an API token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). - -## Limitations - -- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. -- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. - -## Related integrations - -- [Qoder CLI integration](/integrations/qoder-cli) - Install the same plugin in the Qoder CLI -- [QoderWork integration](/integrations/qoder-work) - Upload the plugin in QoderWork -- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients - -## Resources - -- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes -- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs -- [Apify Store](https://apify.com/store) - Browse Actors you can run from the Qoder IDE diff --git a/sources/platform/integrations/ai/qoder/qoder-work.md b/sources/platform/integrations/ai/qoder/qoder-work.md deleted file mode 100644 index 644d8cc4ea..0000000000 --- a/sources/platform/integrations/ai/qoder/qoder-work.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: QoderWork integration -sidebar_label: QoderWork -description: Learn how to upload the Apify plugin in QoderWork to discover, run, and build Actors with the Apify MCP server connector, skills, and a routing agent. -slug: /integrations/qoder-work ---- - -import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; - -[QoderWork](https://qoder.com) is a desktop assistant for knowledge work. It runs tasks and chats using role-oriented plugins that bundle MCP connectors, skills, and agents. - -The [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) adds Apify to QoderWork and bundles: - -- The [Apify MCP server](/integrations/mcp) as a connector for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). -- An `apify` routing agent that picks the right tool or skill from a natural-language request. -- Five built-in skills, available as quick commands (see [Bundled skills](#bundled-skills) below). - - - -## Prerequisites - -- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one. -- [QoderWork](https://qoder.com) - installed and signed in. - -## Install the plugin - -QoderWork doesn't list the Apify plugin in its in-app marketplace yet, so you download the plugin package from the web marketplace and upload it. - -1. Open the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521). Under **For Human**, select the download icon to download the plugin package. - - ![Apify plugin page on the Qoder Marketplace with the For Human download option](images/qoder-work/1-marketplace.webp) - -1. In QoderWork, open **Plugins**, select **+ Add**, then select **Upload plugin**. - -1. Select the plugin package you downloaded. The `apify` plugin is installed for local use and appears under your custom plugins. - -## Authenticate the Apify connector - -The plugin adds Apify as a connector. Read-only tools like searching Apify Store and fetching Actor details work without signing in, but you need to authenticate to run Actors and access your account data. - -1. Open the `apify` plugin. Under **Connectors**, the Apify connector shows **Authentication required**. Select **Auth**. - -1. Complete the Apify OAuth flow in your browser and allow access. The connector then reports its available tools. - -The connection stays authenticated for future sessions. You can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations). - -## Enable the plugin in chat - -1. On the plugin page, turn on **Enable in chat**. The plugin's quick commands and connector become available in tasks and chat. - -1. Start a task or chat and describe what you want. The `apify` agent routes the request to the right tool or skill. - - > List available Apify tools. - - ![QoderWork chat listing the available Apify tools](images/qoder-work/2-chat-list-tools.webp) - -## Bundled skills - -Each skill is available as a quick command. Type `/` in a task or chat to run one directly. - -| Quick command | Description | -| --- | --- | -| `/apify-ultimate-scraper` | Extraction using existing Actors for multi-step scraping and lead-generation workflows. | -| `/apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | -| `/apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | -| `/apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `/apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | - -## Widget tools - -In QoderWork, the Apify connector also exposes interactive widget variants of its core tools - `search-actors-widget`, `fetch-actor-details-widget`, `call-actor-widget`, and `get-actor-run-widget`. They render Actor search, details, runs, and run status as interactive UI elements in chat instead of plain text. - -## Troubleshooting - -### The Apify connector stays on "Authentication required" - -Open the `apify` plugin, select **Auth** on the Apify connector, and complete the browser sign-in. If the browser doesn't open automatically, copy the OAuth URL and paste it into your browser manually. - -### Tools don't appear in chat - -Confirm **Enable in chat** is turned on for the `apify` plugin and that the Apify connector is authenticated. Reopen the task or chat after enabling the plugin. - -## Limitations - -- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. -- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. -- Skills that edit files (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. - -## Related integrations - -- [Qoder CLI integration](/integrations/qoder-cli) - Install the same plugin in the Qoder CLI -- [Qoder IDE integration](/integrations/qoder-ide) - Install the plugin in the Qoder IDE -- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients - -## Resources - -- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes -- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs -- [Apify Store](https://apify.com/store) - Browse Actors you can run from QoderWork diff --git a/sources/platform/integrations/ai/qoder/qoder.md b/sources/platform/integrations/ai/qoder/qoder.md new file mode 100644 index 0000000000..2d6e3fbe7d --- /dev/null +++ b/sources/platform/integrations/ai/qoder/qoder.md @@ -0,0 +1,219 @@ +--- +title: Qoder integration +sidebar_label: Qoder +description: Install the Apify plugin in the Qoder CLI, IDE, Desktop app, and QoderWork to run and build Actors with the Apify MCP server, skills, and a routing agent. +slug: /integrations/qoder +--- + +import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; +import ApifyPluginSkills from '@site/sources/_partials/_apify-plugin-skills.mdx'; +import ApifyPluginSkillPrompts from '@site/sources/_partials/_apify-plugin-skill-prompts.mdx'; + +[Qoder](https://qoder.com) is an agentic coding platform from Alibaba. The same [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) installs across its surfaces and connects them to Apify's library of [Actors](https://apify.com/store). The plugin bundles: + +- The [Apify MCP server](/integrations/mcp) for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). +- An `apify` routing agent that picks the right tool or skill from a natural-language request. +- Five built-in skills for common workflows (see [Bundled skills](#bundled-skills) below). + + + +## Supported surfaces + +The plugin installs in the coding and desktop surfaces that support Qoder plugins: + +| Surface | What it is | Install method | +| --- | --- | --- | +| [Qoder CLI](#qoder-cli) | Coding agent in the terminal | Marketplace command | +| [Qoder IDE](#qoder-ide) | Agentic coding editor | Marketplace page or manual import | +| [Qoder Desktop](#qoder-desktop) | Agentic coding desktop app | Manual import | +| [QoderWork](#qoderwork) | Desktop assistant for document, spreadsheet, research, and browser tasks | Manual import | + +The JetBrains plugin and QoderWake don't support Qoder plugins, but both can still use Apify through the [Apify MCP server](/integrations/mcp): + +| Surface | What it is | How Apify connects | +| --- | --- | --- | +| [QoderWake](#qoderwake) | Always-on AI employees (Wakers) | Apify MCP server as a custom connector | +| [JetBrains plugin](#jetbrains-plugin) | Qoder in JetBrains IDEs | Apify MCP server as a remote MCP | + +:::note Marketplace search doesn't list the plugin yet + +In the IDE and Desktop app, the in-app marketplace search does not surface the Apify plugin. Install it from the [Apify plugin's Marketplace page](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521) or by manual import, as described below. + +::: + +## Prerequisites + +- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one +- A Qoder surface installed and signed in - the [CLI, IDE, Desktop app, or QoderWork](https://qoder.com/download) + +## Install the plugin + +There are two install methods. The CLI installs from a Marketplace command; the IDE, Desktop app, and QoderWork install from the downloaded plugin package. The IDE also supports a one-click install from the Marketplace page. + +### Qoder CLI + +You can install from the Marketplace, or add the plugin repository as a marketplace source. + +1. Open the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521). Under **Qoder CLI**, copy the install command - it looks like `qodercli plugin install `. + + ![Apify plugin page on the Qoder Marketplace with the Qoder CLI install command](images/qoder-cli/01-marketplace-install.webp) + +1. Run the command in your terminal, then restart the Qoder CLI so the bundled MCP server registers. + +Alternatively, add the repository as a marketplace source: run `/plugins`, open the **Marketplaces** tab, select **+ Add marketplace**, paste `https://github.com/apify/apify-qoder-plugin`, then install the `apify` plugin from the **Discover** tab. Run `/plugins reload` and restart the CLI. + +![The apify plugin detail in the Qoder CLI with the install scope options and a trust warning](images/qoder-cli/02-install-plugin.webp) + +### Qoder IDE + +Install directly from the Marketplace page, or import the downloaded package. The one-click install requires Qoder IDE version 1.23.0 or newer. + +- **From the Marketplace page:** open the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521), select **Qoder IDE**, and confirm **Install Plugin** in the dialog the IDE opens. + + ![Apify plugin page on the Qoder Marketplace with the Qoder IDE install option](images/qoder-ide/1-marketplace.webp) + +- **Manual import:** on the same page, under **For Human**, download the plugin package. In the IDE, open the account menu, select **Qoder Settings** > **Plugins**, then under **Custom** select **Import** and choose the package. + +The plugin appears under **Installed** or **Custom**. Make sure it's enabled, then open **MCP Server** to confirm the `apify` server is registered. + +### Qoder Desktop + +The Desktop app installs the plugin from the downloaded package. + +1. On the [Apify plugin's Marketplace page](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521), under **For Human**, download the plugin package. + ![Apify plugin page on the Qoder Marketplace with the For Human download option](images/qoder-work/1-marketplace.webp) + +1. In the Desktop app, open **Settings** > **Plugins**, then under **Custom** select **Import** and choose the package. + +1. Make sure the plugin is enabled, then confirm the `apify` server appears under **MCP Server**. + +### QoderWork + +QoderWork imports the plugin package locally and runs it as a connector. + +1. On the [Apify plugin's Marketplace page](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521), under **For Human**, download the plugin package. + +1. In QoderWork, open **Plugins**, select **+ Add**, then **Upload plugin**, and choose the package. + +1. Turn on **Enable in chat** so the plugin's commands and connector are available in tasks and chat. + +:::tip Restart so the MCP server registers + +The Apify MCP server registers when the surface starts. If the Apify tools don't appear after installing, fully quit and reopen the CLI, IDE, Desktop app, or QoderWork. + +::: + +## Authenticate to Apify + +The plugin bundles the Apify MCP server and connects to its default endpoint, so authenticate before your first prompt - without a token the server rejects every tool call, including Actor search. Each surface triggers the same Apify OAuth flow in your browser. + +- **CLI:** run `/mcp` and open the **Plugin** tab, then: + + 1. Select **plugin:apify:apify**. Its status reads **needs authentication**. + 1. Select **Authenticate**, then **Yes** at the consent prompt. + 1. If the browser doesn't open, copy the full URL from the terminal (triple-click to select it) and open it manually. + 1. When sign-in completes, the server status changes to **ready**. + + ![Terminal waiting for the browser callback and showing the fallback OAuth URL](images/qoder-cli/03-authenticating.webp) + +- **IDE and Desktop:** on the first action that needs your account, the app opens a browser tab for the Apify OAuth flow. +- **QoderWork:** open the `apify` plugin, and under **Connectors** select **Auth** on the Apify connector. + +Review the permissions and allow access to finish signing in. The connection stays authenticated for future sessions, and you can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qoder&utm_medium=integrations). + +## Run your first prompt + +Describe what you want in natural language. The `apify` agent routes the request to the right tool or skill, so you don't need to name tools yourself. + +> List what Apify tools you have available. + +To go further, ask it to find an Actor for a task: + +> Use Apify to find a good Actor for scraping Google Maps places. Show me the best option, its input requirements, pricing model, and what kind of dataset output it returns. Do not run the Actor yet. + +## Bundled skills + + + +In the CLI, IDE, and Desktop app, the agent invokes these skills automatically. In QoderWork, each skill is also a quick command - type `/` in a task or chat to run one directly. + + + +## Add the Apify MCP server + +The JetBrains plugin and QoderWake don't support Qoder plugins, so the bundled skills and the `apify` agent aren't available there. You can still give them the Apify tools by connecting the [Apify MCP server](/integrations/mcp) directly. + +### QoderWake + +QoderWake runs digital employees called Wakers. Add the Apify MCP server as a custom connector. + +1. In the QoderWake management console, create a Waker, then open it and select **Edit** to reach its settings. + +1. Open **Connector**, select the **Installed** tab, and under **Custom** select **Add**. + +1. In the **Add MCP Server** dialog, set **Server Type** to **Streamable HTTP**, name the server (for example `apify-mcp`), set the server URL to `https://mcp.apify.com`, then select **Add**. + +1. Restart QoderWake. The connector then appears under **Custom** with the status **Not connected**. + +1. Select **Auth** on the connector and complete the Apify sign-in in your browser. + +1. Restart QoderWake again. The connector status changes to connected, and the Waker can call the Apify tools. + +The Waker gains the Apify MCP tools for searching Apify Store, running Actors, and retrieving datasets. To revoke access later, select **Reset authorization** on the connector, or manage the connection in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qoder&utm_medium=integrations). + +### JetBrains plugin + +The Qoder JetBrains plugin connects to the Apify MCP server as a remote MCP server. + +1. In your JetBrains IDE, select the Qoder icon in the status bar, then select **Advanced Settings**. + +1. Go to **Personal Settings** > **MCP Servers** and select **Add Remote MCP**. + +1. Enter a **Name**, set **Remote MCP URL** to `https://mcp.apify.com` (the **Command** is generated from the URL), then select **OK**. + +1. Complete the Apify sign-in in your browser when prompted. + +The Qoder agent in the IDE can then call the Apify MCP tools. + +## Troubleshooting + +Common issues and how to fix them. + +### The Apify MCP server doesn't appear + +The server registers at startup. Confirm the plugin is enabled, then fully quit and reopen the surface. In the IDE and Desktop app, check the **MCP Server** page; in the CLI, run `/mcp`. + +### The Apify plugin isn't in the marketplace search + +The in-app marketplace does not list the Apify plugin yet. Install it from the [Marketplace page](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521) (CLI command or IDE one-click), or import the downloaded package (IDE, Desktop, QoderWork). + +### Actor runs time out + +Increase the request timeout for the `apify` server. See [Limitations](#limitations) for why long-running Actors can exceed a single tool call. + +### Browser doesn't open, or OAuth fails + +If the browser doesn't open automatically, copy the OAuth URL shown by the surface and open it manually. If sign-in still fails, add an `Authorization` header to the `apify` server with a token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qoder&utm_medium=integrations): + +```json +"headers": { + "Authorization": "Bearer " +} +``` + +## Limitations + +- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. +- Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. + +## Related integrations + +- [Qwen integration](/integrations/qwen) - Use Apify in Qwen Code and QwenWork +- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients + +## Resources + +- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes +- [Qoder documentation](https://docs.qoder.com) - Official Qoder docs +- [Apify Store](https://apify.com/store) - Browse Actors you can run from Qoder diff --git a/sources/platform/integrations/ai/qoder/qwen.md b/sources/platform/integrations/ai/qoder/qwen.md new file mode 100644 index 0000000000..c16d9e0f4c --- /dev/null +++ b/sources/platform/integrations/ai/qoder/qwen.md @@ -0,0 +1,200 @@ +--- +title: Qwen integration +sidebar_label: Qwen +description: Use Apify Actors with Alibaba's Qwen tools - install the Apify plugin in Qwen Code, or add the Apify MCP server and upload the skills in QwenWork. +slug: /integrations/qwen +--- + +import ThirdPartyDisclaimer from '@site/sources/_partials/_third-party-integration.mdx'; +import ApifyPluginSkills from '@site/sources/_partials/_apify-plugin-skills.mdx'; +import ApifyPluginSkillPrompts from '@site/sources/_partials/_apify-plugin-skill-prompts.mdx'; + +Alibaba ships two agent tools under the Qwen name, and both can call Apify [Actors](https://apify.com/store). They connect to Apify in different ways: + +- **[Qwen Code](#qwen-code)** is an open-source agentic coding tool that runs in your terminal. It supports the Qoder plugin format, so it installs the full [Apify plugin built for Qoder](https://github.com/apify/apify-qoder-plugin) - the Apify MCP server, the `apify` routing agent, and five skills - with no separate build. +- **[QwenWork](#qwenwork)** is an all-in-one workplace AI agent for documents, data, and knowledge work, available as desktop and web apps. It is not a plugin host, so you connect the [Apify MCP server](/integrations/mcp) as a custom connector and upload the Apify skills individually. + + + +## Supported surfaces + +| Product | What it is | How Apify connects | +| --- | --- | --- | +| [Qwen Code](#qwen-code) | Agentic coding tool in the terminal | Install the Apify plugin (bundles the MCP server, the `apify` agent, and skills) | +| [QwenWork](#qwenwork) | Workplace AI agent (desktop and web) | Apify MCP server as a custom connector, plus skills uploaded one by one | + +## Prerequisites + +- [An Apify account](https://console.apify.com/sign-up) - sign up for free if you don't have one +- The Qwen tool you want to use - [Qwen Code](https://github.com/QwenLM/qwen-code) installed with a model provider, or [QwenWork](https://qwenwork.ai) installed and signed in + +## Qwen Code + +Qwen Code installs the same plugin as Qoder and keeps everything it bundles: + +- The [Apify MCP server](/integrations/mcp) for searching Apify Store, running Actors, and retrieving datasets through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro). +- An `apify` routing agent that picks the right tool or skill from a natural-language request. +- Five built-in skills for common workflows (see [Bundled skills](#bundled-skills) below). + +### Install the plugin + +Qwen Code installs the Apify plugin from its ZIP archive with the `qwen extensions install` command. Download the ZIP first, then point the installer at the local file. + +1. Open the [Apify plugin on the Qoder Marketplace](https://qoder.com/marketplace/plugin?id=bbbdb1cb-8bad-441e-b42f-ce0e33e3a521). Under **For Human**, select the download icon to download the plugin ZIP. + ![Apify plugin page on the Qoder Marketplace with the For Human download option](images/qwen-code/1-marketplace.webp) + +1. Install the archive, replacing the path with where you saved it: + + ```bash + qwen extensions install ./apify-qoder-plugin-.zip + ``` + + Qwen Code converts the Qoder manifest to its own `qwen-extension.json`. It registers the bundled skills and the `apify` agent, then adds the Apify MCP server from the plugin's root `.mcp.json`. + +1. Restart Qwen Code so the extension and its MCP server load. + +To scope the extension to the current workspace instead of your user account, add `--scope workspace`. + +:::tip One plugin, two transports + +The plugin's `.mcp.json` declares the Apify MCP endpoint under both `url` and `httpUrl`. Qwen Code reads `httpUrl` for streamable HTTP, while the Qoder apps read `url`, so the same artifact connects in every host without editing. + +::: + +### Authenticate to Apify + +The plugin bundles the Apify MCP server and connects to its default endpoint, which requires an Apify account. Authenticate before your first prompt - without a token the server rejects every tool call, including Actor search. + +1. Run `/mcp` to open the MCP management dialog and find the `apify` server. + +1. Select the `apify` server and authenticate. Qwen Code opens the Apify authorization page in your browser. + +1. In the browser, review the permissions and allow access. A confirmation page tells you to close the window and return to Qwen Code. + +1. Back in the terminal, the `apify` server status changes to connected and the Apify tools become available. + +The connection stays authenticated for future sessions. You can revoke access at any time in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). + +### Run your first prompt + +Describe what you want in natural language. The `apify` agent routes the request to the right tool or skill, so you don't need to name tools yourself. + +> List what Apify tools you have available. + +To go further, ask it to find an Actor for a task: + +> Use Apify to find a good Actor for scraping Google Maps places. Show me the best option, its input requirements, pricing model, and what kind of dataset output it returns. Do not run the Actor yet. + +### Manage the extension + +Use the `qwen extensions` commands to manage the plugin after install: + +```bash +qwen extensions disable apify # turn the plugin off +qwen extensions enable apify # turn it back on +qwen extensions uninstall apify # remove it +``` + +Inside a session, run `/extensions list` to see installed extensions or `/extensions` for the interactive manager. + +To move to a newer release, uninstall the current version first, then install the new ZIP: + +```bash +qwen extensions uninstall apify +qwen extensions install ./apify-qoder-plugin-.zip +``` + +## QwenWork + +QwenWork isn't a plugin host, so the bundled `apify` agent isn't available there. You give it Apify in two steps: connect the [Apify MCP server](/integrations/mcp) as a custom connector for the tools, and upload the Apify skills you want as local skills. + +### Add the Apify MCP server + +Add the Apify MCP server under **Extensions > Connectors**. It authenticates through Apify OAuth, so there's no token to paste. + +1. Open **Extensions > Connectors**, then select **+ Add**. + +1. Choose **Streamable HTTP** as the server type and fill in the form: + - **Server Name:** `apify` + - **Server URL:** `https://mcp.apify.com` + +1. Select **Add**. QwenWork opens the Apify authorization page in your browser. + +1. Sign in to Apify and allow access. The browser redirects back to QwenWork, and the connector connects. + +The Apify tools for searching Apify Store, running Actors, and retrieving datasets are then available in tasks and chat. You can also paste a JSON configuration instead of filling in the form. To revoke access later, remove the connector or manage the connection in [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). + +### Add the Apify skills + +QwenWork installs skills one at a time from a local package. Each Apify skill is a `.zip` that contains a `SKILL.md` and its `references/` folder. + +1. Download the Apify skill packages you want. Each skill has its own page on the [Qoder Marketplace](https://qoder.com/marketplace). In the **Install** panel, under **For Human**, select the download icon to save the skill `.zip`. + + ![Qoder Marketplace skill page with the For Human download icon highlighted](images/qwen-work/1-skill-download.webp) + +1. In QwenWork, open **Extensions > Skills**, select **+ Add**, then **Upload skill**. + +1. Drag the `.zip` into the **Install Skill** dialog (or select it), then select **Install**. The skill appears under **Installed > Local install**. + +1. Repeat for each skill you want to add. + +QwenWork uses an installed skill automatically when a task matches the trigger conditions in its `SKILL.md`. See [Bundled skills](#bundled-skills) for the five Apify skills. + +### Run your first prompt + +With the connector added, describe a task in natural language and QwenWork calls the Apify tools: + +> Use Apify to find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website. + +To scope a source directly, name the Actor's target: + +> Use Apify to scrape the latest 50 posts from a public Instagram profile and return them as a table. + +## Bundled skills + + + +In Qwen Code, skills are available through the `/skills` command, and the `apify` agent appears under **Extension Agents** in the subagent manager. In QwenWork, upload the skills you want (see [Add the Apify skills](#add-the-apify-skills)), and it runs them by trigger condition. These prompts route to specific skills: + + + +## Troubleshooting + +Common issues and how to fix them. + +### The Apify MCP server doesn't appear + +In Qwen Code, run `/mcp` to check the server list. In QwenWork, open **Extensions > Connectors** and confirm the `apify` connector is installed. If the server is missing, fully quit and reopen the app, then check again. + +### The MCP server fails with an SSE error + +This affects Qwen Code. An older plugin build declared the MCP endpoint only under `url`, which Qwen Code reads as a legacy SSE transport and rejects with an `SSE error: Non-200 status code (400)`. Reinstall the latest release archive - its `.mcp.json` also sets `httpUrl`, which Qwen Code uses for streamable HTTP. + +### Browser doesn't open, or OAuth fails + +If the sign-in page doesn't open or the server stays disconnected: + +- **Qwen Code:** copy the authorization URL from the terminal and open it manually. If sign-in still fails, add an `Authorization: Bearer ` header to the `apify` server in `~/.qwen/settings.json` under `mcpServers` - see the [Client configuration](/integrations/mcp#client-configuration) for the shape. +- **QwenWork:** remove the connector and add it again. If OAuth still won't complete, re-add it with an `Authorization` header set to `Bearer `. + +Get the token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). Setting `APIFY_TOKEN` in your shell doesn't authenticate the MCP server; it only covers the Apify CLI and `apify-client` used by the Actor development, actorization, and SDK integration skills, so run `apify login` once for those. + +## Limitations + +- In Qwen Code, the plugin's role guide ships as `qoder.md`. Qwen Code auto-loads a root `system-prompt.md` as context, so `qoder.md` is not injected automatically. The `apify` agent and skills still work; invoke the agent to get the routing behavior. +- QwenWork doesn't host the bundled `apify` agent, so it has no automatic routing. Add the skills you need and let their trigger conditions apply, or name the task clearly. +- Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. +- Each Actor run consumes Apify platform usage from your plan in addition to any Qwen usage. See [Billing](/account/billing) for details. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. + +## Related integrations + +- [Qoder integration](/integrations/qoder) - Install the same plugin in the Qoder CLI, IDE, Desktop app, or QoderWork +- [MCP server integration](/integrations/mcp) - Use the Apify MCP server with other clients + +## Resources + +- [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - Source repository and README with advanced setup notes +- [Qwen Code extensions](https://qwenlm.github.io/qwen-code-docs/en/users/extension/introduction/) - Official extension install and management docs +- [QwenWork documentation](https://docs.qwenwork.ai) - Official QwenWork docs for connectors and skills +- [Apify Store](https://apify.com/store) - Browse Actors you can run from Qwen diff --git a/static/img/platform/integrations/qoder-cli.png b/static/img/platform/integrations/qoder-cli.png deleted file mode 100644 index aa0a887044..0000000000 Binary files a/static/img/platform/integrations/qoder-cli.png and /dev/null differ diff --git a/static/img/platform/integrations/qoder-work.png b/static/img/platform/integrations/qoder-work.png deleted file mode 100644 index 5591b5e175..0000000000 Binary files a/static/img/platform/integrations/qoder-work.png and /dev/null differ diff --git a/static/img/platform/integrations/qoder.svg b/static/img/platform/integrations/qoder.svg index 829ec79a35..599212e57a 100644 --- a/static/img/platform/integrations/qoder.svg +++ b/static/img/platform/integrations/qoder.svg @@ -1 +1,5 @@ - \ No newline at end of file + + + + + diff --git a/static/img/platform/integrations/qwen.svg b/static/img/platform/integrations/qwen.svg new file mode 100644 index 0000000000..78a16baf5f --- /dev/null +++ b/static/img/platform/integrations/qwen.svg @@ -0,0 +1,15 @@ + + + + + + + + + + + + + + + \ No newline at end of file