feat: qoder plugin docs - #2808
Conversation
marcel-rbro
left a comment
marcel-rbro
left a comment
There was a problem hiding this comment.
Content review of the three Qoder pages. The structure follows the Cursor and Claude Code plugin template closely, and markdownlint, Vale, and the frontmatter description lengths all pass. Comments below are mostly small edits, plus a few questions for @daveomri.
Not merging yet: the plugin isn't listed on the Qoder marketplace, so the install steps and screenshots may still change. The branch also needs a master merge to clear the conflict, and the PR title should be docs: rather than feat: for a docs-only change.
|
|
||
| 1. Back in the terminal, the server status changes to **ready** and the Apify tools become available. | ||
|
|
||
|  |
There was a problem hiding this comment.
The tool count changes with the MCP server's configuration, so it's better left out of alt text.
|  | |
|  |
|
|
||
|  | ||
|
|
||
| To see what the agent can call, select **View tools** on the server detail. The Apify MCP server exposes 11 tools, each labeled read-only, destructive, or open-world. |
There was a problem hiding this comment.
The count will go stale, and the screenshot below shows report-problem without a label, so "each labeled" isn't accurate.
| To see what the agent can call, select **View tools** on the server detail. The Apify MCP server exposes 11 tools, each labeled read-only, destructive, or open-world. | |
| 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. |
|
|
||
| To see what the agent can call, select **View tools** on the server detail. The Apify MCP server exposes 11 tools, each labeled read-only, destructive, or open-world. | ||
|
|
||
|  |
There was a problem hiding this comment.
Same reason as above - drop the count from the alt text.
|  | |
|  |
| Example prompts that route to specific skills: | ||
|
|
||
| _Ultimate scraper:_ | ||
|
|
||
| > Find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website. | ||
|
|
||
| _Actor development:_ | ||
|
|
||
| > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. | ||
|
|
||
| _SDK integration:_ | ||
|
|
||
| > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. |
There was a problem hiding this comment.
Naming the skills directly ties each prompt to the table above and avoids italic labels.
| Example prompts that route to specific skills: | |
| _Ultimate scraper:_ | |
| > Find 10 highly rated coffee shops in Seattle with name, address, rating, phone, and website. | |
| _Actor development:_ | |
| > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. | |
| _SDK integration:_ | |
| > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. | |
| Example prompts that 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. |
|
|
||
| If the browser doesn't open automatically, copy the OAuth URL shown in the terminal and paste it into your browser manually. | ||
|
|
||
| If you're running the Qoder CLI in a headless environment (SSH, remote container) or the OAuth flow still fails, authenticate with 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: |
There was a problem hiding this comment.
The two examples need a conjunction to read as a list.
| If you're running the Qoder CLI in a headless environment (SSH, remote container) or the OAuth flow still fails, authenticate with 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: | |
| If you're running the Qoder CLI in a headless environment (SSH or a remote container) or the OAuth flow still fails, authenticate with 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: |
| ### Actor runs time out | ||
|
|
||
| Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. | ||
|
|
There was a problem hiding this comment.
This entry repeats the first Limitations bullet word for word without adding a QoderWork-specific fix, so it can go.
| ### Actor runs time out | |
| Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. |
|
|
||
|  | ||
|
|
||
| 1. Select the Apify plugin bundle from your local copy. The `apify` plugin is installed for local use and appears under your custom plugins. |
There was a problem hiding this comment.
@daveomri does Upload plugin expect the release zip or an unpacked folder? If it's the zip, linking the release makes the step self-contained:
| 1. Select the Apify plugin bundle from your local copy. The `apify` plugin is installed for local use and appears under your custom plugins. | |
| 1. Select the plugin zip from the [latest plugin release](https://github.com/apify/apify-qoder-plugin/releases/latest). The `apify` plugin is installed for local use and appears under your custom plugins. |
|
|
||
| ## 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. |
There was a problem hiding this comment.
@daveomri can you confirm these four widget tool names are current, and that they're QoderWork-only? I can't check them against the plugin.
|
|
||
| - [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. | ||
| - A local copy of the [Apify plugin for Qoder](https://github.com/apify/apify-qoder-plugin) - clone or download the repository so you can import it. |
There was a problem hiding this comment.
@daveomri once the plugin is on the Qoder marketplace, will the IDE and QoderWork install from there instead of a local copy? If so, this prerequisite and the install steps on both pages need a rewrite before merge (the Cursor page documents the marketplace flow).
| <Card | ||
| title="Qoder" | ||
| desc="Install the Apify plugin in the Qoder CLI, IDE, or QoderWork to discover, run, and build Actors." | ||
| to="/integrations/qoder" | ||
| imageUrl="/img/platform/integrations/qoder.png" | ||
| smallImage | ||
| /> |
There was a problem hiding this comment.
The other multi-page hubs (Claude, OpenAI) appear only in the "By provider" text, which this PR also adds below - I'd drop this card and keep just the paragraph. Also, sibling logos are SVG with an imageUrlDarkTheme variant; is an SVG Qoder logo available, or has the PNG been checked on the dark theme?
3 participants
It documents the Apify plugin for Qoder CLI / Qoder IDE / QoderWork