← GoodMemCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to GoodMem
Snapshot Sep 30, 2026 · 23:09 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "goodmem-troubleshooting",
"description": "Verify and troubleshoot the hosted GoodMem Cloud connection, authorization, model setup, processing failures, and retrieval problems. Use when GoodMem is unavailable or the user asks how to connect or repair it.",
"included_files": [],
"skill_md_contents": "---\nname: goodmem-troubleshooting\ndescription: Verify and troubleshoot the hosted GoodMem Cloud connection, authorization, model setup, processing failures, and retrieval problems. Use when GoodMem is unavailable or the user asks how to connect or repair it.\n---\n\n# Troubleshoot GoodMem Cloud\n\nGoodMem connects only through its hosted OAuth gateway to the user's selected\nGoodMem Cloud instance. Never request an API key, instance URL, or local server\nconfiguration for this plugin.\n\n## Verify the connection\n\nCall `goodmem_users_me` first. Success confirms the selected account and instance;\nreport the connected identity and continue with the original task.\n\n## Diagnose failures\n\n| Symptom | Likely cause | Action |\n|---|---|---|\n| Connection is unauthorized after previously working | The instance key or grant changed | Reconnect GoodMem through the current host |\n| Sign-in rejects the account | Organization access is not enabled | Ask the GoodMem administrator |\n| Instance is absent from the picker | Wrong team, provisioning, or paused instance | Select the correct team and check the GoodMem Cloud console |\n| Space creation returns a setup link | No embedder is configured | Relay the Quick Start link exactly; afterward list spaces and reuse the first space before attempting another create |\n| Memory status is `FAILED` | Embedding pipeline or provider configuration failed | Read `processing_error` and direct the user to repair it in the cloud console |\n| Agent transcribes a PDF into separate text memories | Outdated instructions or an unavailable upload tool | Check that `goodmem_memories_upload` is available and refresh the plugin instructions and tool list; do not repeat the text saves |\n| Upload tool or native file object is unavailable | Outdated tool discovery or the host did not provide a usable attachment | Refresh available tools or request a fresh attachment; explain the limitation without silently transcribing |\n| Retrieval with synthesis times out | Large search or answer-generation workload | Reduce the result scope or retrieve without synthesis |\n\nDo not retry authorization failures blindly.\n\n## Reconnect through the current host\n\nDisconnect and reconnect the GoodMem app through the current host's connection\nsettings. This restarts OAuth against the same hosted gateway and cloud instance.\n\nWhen the user asks to create or add an embedder, reranker, or LLM, follow the\nmodel-setup steps in `using-goodmem-memory`: call `goodmem_console_setup` with\nthe matching `kind` and relay the one-time console link verbatim — never write\ncode or collect provider keys in chat for this.\n"
}SHA-256: e1ee0d825324eb0d749b2f76f7a634124f3b4961ca989ec9b3f733deda368b77