Check token state
Open Library and confirm the access token is active, not revoked, suspended, or expired.
Docs1 2 3 4 1 2 3 4 1 2 3 4
Support
Troubleshooting OlyWork
Operational fixes for install failures, publish validation, token lifecycle issues, runtime calls, and creator package review.
Buyer install recovery
Run doctor
`oly doctor` checks Node, local state, endpoint config, and common install blockers.
Verify package
`oly verify <package>` confirms installed files, checksums, config patches, and missing user secrets.
Update or rollback
Use `oly update <package>` or `oly uninstall <package> --rollback` when config patches need to be restored.
bash
oly doctorCheck local CLI prerequisites and saved endpoint/token config.
bash
oly verify <package>Validate files, checksums, generated config, and missing user secrets.
bash
oly uninstall <package> --rollbackRestore patched config files from the latest OlyWork backup.
Target-specific recovery
bash
oly install <token> --target claude_desktop --dry-runPreview Claude Desktop MCP config changes before writing them.
bash
oly install <token> --target cursor --forceReinstall Cursor config after confirming the backup path in `.oly/backups`.
bash
oly update <package> --version <version>Pin a known-good release when the current version is incompatible.
bash
oly mcp <capability> --setup openclaw --writeRegenerate OpenClaw MCP bridge config when the external client cannot see tools.
Creator publish recovery
Review draft state
Creator Studio autosaves draft fields, GitHub analysis, selected files, media, delivery, and pricing.
Preview files
For GitHub imports, preview included files and remove maintenance files before publishing.
Fix checklist
Complete public metadata, manifest, artifact, media, permission model, and security audit blockers.
Submit again
After rejection or validation errors, return to Drafts/Listings and resubmit without rebuilding from scratch.
Package validation
Publish failures usually mean one of these is missing: title, short description, supported platforms, source content, encrypted artifact, manifest, or type-specific metadata.
Draft recovery
If validation fails, return to the same wizard step. Do not clear browser storage unless support asks; the draft saver stores source, metadata, pricing, and selected GitHub files.
Protected runtime bridge recovery
Confirm entitlement
Hosted/protected runtime calls require an active access token on every request.
Inspect invocation
Check runtime invocation status, duration, safe logs, error code, and client metadata.
Check isolation
Use E2B on normal Cloud Run. Docker mode should only run when the worker has Docker support.
Escalate safely
Never expose creator source, secrets, private repo URLs, or storage paths while debugging.
Entitlement first
Runtime, MCP, Codex, Claude, Cursor, and OpenClaw connectors should fail closed when access is missing, revoked, suspended, expired, or hosted-only delivery is used from the secure install path.
Safe debug boundary
Support may inspect status, public metadata, audit records, and safe logs. Support must not send creator prompts, source bundles, package ciphertext, auth tags, storage keys, or private repo paths to buyers.
Common error codes
invalid_tokenRotate or copy a fresh token from Library.expiredRotate the token or request renewed access.revokedAccess was intentionally revoked. Rotate only if you still own access.suspendedContact support or wait for admin review.missing_entitlementPurchase, free access grant, or beta access is required.hosted_execution_onlyUse the runtime/MCP bridge instead of secure install.version_unavailableChoose a listed package version or update to current.checksum_failureStop install and contact support with package, version, and CLI output.Include package slug, version, CLI version, operating system, target client, and exact error code in support reports.
For install failures, attach `oly doctor` and `oly verify <package>` output after removing local user secrets.
For creator publish failures, include source mode, package type, install target, and which wizard step failed.
For runtime failures, include invocation id, capability slug, client name, and timestamp.
Never paste access tokens, creator secrets, private repo URLs, package ciphertext, auth tags, or storage keys into public channels.
Rule of thumb: if a fix requires private source inspection, move it to an admin-only support path and keep the buyer-facing response limited to status, remediation, and safe logs.