← ParallelCONTENT HISTORY
WHAT CHANGED
Update to Parallel
Snapshot Nov 6, 2026 · 00:10 UTC · version 1.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Parallel and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Troubleshoot the Parallel connection or sign in when Research requires it.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 122
}
],
"name": "parallel-search-setup",
"skill_md_contents": "---\nname: parallel-search-setup\ndescription: Troubleshoot the Parallel connection or sign in when Research requires it.\n---\n\n# Parallel connection help\n\nUse the registered Parallel connection supplied by this plugin. Search, Fetch,\nand Decisions work without an account, subject to anonymous usage limits. Research\nrequires a Parallel account. Do not require sign-in before using public tools.\n\nFor Research, use the protected tool and let the client's native account-linking\nflow prompt when needed. Complete browser authorization with the intended\nParallel account and organization, then let the client resume. Retry the pending\nrequest only when the client explicitly says authentication succeeded and asks\nfor a retry. Do not ask for secrets, authorization codes, or callback URLs in chat.\n\nIf the user declines sign-in, Research stays unavailable. Search, Fetch, and\nDecisions remain usable through the same anonymous connection. Do not create a\nsecond connection or switch endpoints. Do not keep asking the user to sign in.\n\nInspect this plugin's status in the client's plugin settings when tools are\nmissing. Use Connect or Reconnect only when needed. Do not silently substitute\nanother provider or Parallel integration. An anonymous Search success does not\nprove account linking; do not run billable Research solely to test authentication.\n\nA rejected credential may require Reconnect. Do not silently discard it to\nbypass authentication. Report actual permission, billing, and rate-limit errors\nwithout turning them into sign-in requests. Respect Retry-After.\n\nResearch is synchronous and billable. After a timeout or interruption, report\nthe uncertain outcome and do not automatically repeat the request. A follow-up\nuses the returned response ID as previous_response_id.\n"
}SHA-256 of public snapshot: dafa0be3fe148ef8018183e45e019b4353ff53d68965b1a57ea3cb0fa3612fa0