Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

e-comet-doctor

Use when e-Comet installation, local MCP startup, browser extension routing, storage, report creation, upload, or host hook behavior fails or remains uncertain, and when the user says e-Comet tools are missing, not answering, asking to sign in, or "worked before".

e-comet · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add e-comet/skills --skill e-comet-doctor

About this skill


name: e-comet-doctor description: Use when e-Comet installation, local MCP startup, browser extension routing, storage, report creation, upload, or host hook behavior fails or remains uncertain, and when the user says e-Comet tools are missing, not answering, asking to sign in, or "worked before".

e-Comet doctor

Base every conclusion on an observed typed result. Absence of a local tool can be a valid remote-only installation and does not prove a broken full installation.

Triage before any conclusion

Both hosts load tools on demand. Search the host tool catalog for e-comet with a large result limit, or search by exact tool name. A fresh task's start list proves nothing. A truncated search result does not prove absence; use the host's supported bounded search again or search for the exact capability before calling it unavailable.

Observed after searchMeaningNext step
No e-Comet toolsInstallation or enablement is uncertain; in Cowork the remote connector may also be disconnectedCowork: call host ListConnectors filtered for e-Comet. If ListConnectors shows the connector connected, verify in Customize → Plugins → Yours that e-Comet MCP Tools is installed and enabled, answer any local MCP permission prompt with Continue, and start a new task. Codex: use the README fallback to check marketplace, plugin installation and enablement, then start a new task. No local probe is available.
Local tools present, remote tools absentRemote authorization, chat enablement, or connection is uncertainCodex: call installation e_comet_diagnose with safe_probes and codex_mcp_auth. Cowork: call ListConnectors. Apply the connector rules below.
Both presentTools are visible in this taskContinue with the numbered steps below.

The extension connects through the local MCP. When the local MCP is absent, first resolve that host route; extension checks cannot explain the missing local tools.

Typed-result cases

The host-neutral cases (BRIDGE_* causes, extension not installed, disabled or not activated, account mismatch, WB_NOT_AUTHENTICATED, SELLER_LOGIN_REQUIRED, BROWSER_JOB_HANDOFF_REQUIRED, OZON_ROUTE_NOT_READY), the extension rules, the answer order, plain examples and common mistakes are in TROUBLESHOOTING.md: read it before concluding, and give its action when a row matches. Its owner rule decides the report: a cause owned by the user or an administrator ends with the action and no report unless the action did not help; one owned by e-Comet gets a report. The rows below add the actions only this host has. A user prerequisite is not a bug report; retryDisposition governs repeats.

Only for BRIDGE_HOST_START_FAILED whose message does not name ComSpec, or for BRIDGE_HOST_NOT_STARTED after the e-Comet icon click did not help while the runtime extension_log check could not read the log, read guided steps and follow them; nothing else sends you there.

Host cases

ObservedMeaningUser action
BROWSER_JOB_HANDOFF_REQUIRED, or Ozon OZON_AUTHORIZATION_REJECTED with "The trusted browser-job hook did not provide Ozon authorization."The host hook did not provide the authorization: plugin hooks not trusted, disabled, changed after an update, or not run by the host in this taskNever repeat browser_job automatically. Codex: run installation hook_permissions; on disabled or review_required send the user to Settings → Plugins → Personal → e-Comet MCP Tools → Hooks to enable and trust all e-Comet handlers at once; on ready or not_checked say the cause is not established and offer a retry on the user's decision or a report. Cowork (local tools named mcp__remote-devices__...): the call lacked triggerUrl; pass trigger_url from the same browser_job result, unchanged, as triggerUrl and call the local tool once more, without a new browser_job. «Плагин не смог передать разрешение браузеру. Проверю настройки хуков e-Comet в Codex и скажу, что сделать.» Then, for a disabled or review-required handler: «Откройте Settings → Plugins → Personal → e-Comet MCP Tools → Hooks и разрешите сразу все хуки e-Comet, потом повторим.»
Remote tools absent after search; Codex codex_mcp_auth not_logged_in, or Cowork installState other than connectedCodex configuration shows sign-in not completed; Cowork reports the connector not connected; firm wording only after a host authorization errorCodex: Settings → Plugins → e-Comet MCP Tools → server E-comet → Connect. «По настройкам Codex вход в e-Comet не выполнен: откройте настройки плагина и нажмите Connect у сервера E-comet.» Cowork: plugin card → Connectors → Connect. «Коннектор e-Comet не подключён: нажмите Connect в карточке плагина.»
Cowork installState:"connected", enabledInChat:falseConnector connected but disabled for this chatAsk the user to enable e-Comet for this chat; the exact control is an unverified UI detail, describe the action and name no control. «Коннектор e-Comet подключён, но выключен для этого чата: включите его в этом чате.»
Only remote tools after searchBasic installation, or a full one whose local MCP did not startAsk which installation was intended (README: Базовая / Полная); for a full one use the README fallback.
Hook denial HANDOFF_MISSING or HANDOFF_TOOL_MISMATCHNo authorization waited for this tool in this conversationAfter a HANDOFF_MISSING from a local call made in the same parallel step as browser_job, retry the local tool alone once. Otherwise call browser_job once for the intended tool, then the local tool without authorization fields.
Hook error HANDOFF_TOKEN_NOT_FOUND beside the browser_job result, then HANDOFF_MISSINGThe hook found no authorization in the result the host handed itDo not repeat browser_job
Read the complete source ↗