Fix a connection problem
Find the failing step
Section titled “Find the failing step”| What you see | What to check | Avoid |
|---|---|---|
| Thegram is not in the client’s tools | Complete the selected client’s installation and restart it when required. A connector and a memory skill are distinct. | Repeatedly installing unrelated plugins |
| OAuth sign-in or consent is incomplete | Use your intended provider/Thegram account and review the provider’s prompts and organization restrictions yourself. | Having an agent accept consent for you |
HTTP 401 or E_AUTH |
Confirm your own key is configured, unexpired and unrevoked; reconnect at the hidden terminal prompt if you replace it. | Pasting the key into chat or reusing another person’s credentials |
AGENT_SCOPE_DENIED, E_FORBIDDEN or read-only error |
Review resource scopes, membership and policy. Read-only access may continue to read. | Treating a denial as an empty result, or widening access without approval |
E_PROJECT_IDENTITY, no repository project or multiple matches |
Check the repository origin and the exact existing project association. Follow project association. | Guessing a document path, selecting another vault or automatically creating a replacement |
| Empty vault listing | The connection can be valid but contain no readable documents. Confirm the intended account and grants. | Creating test records to claim success |
| Direct read succeeds but search misses | Confirm the authorized folder and indexing state. Read exact saved paths directly; search quality is a separate check. | Claiming data was lost solely because search returned nothing |
E_CONNECT or key_service_unavailable |
Check the configured endpoint and network/service readiness. | Falling back to a desktop socket or a different destination |
OMP updates
Section titled “OMP updates”Use the full marketplace ID shown in coding-agent setup. The canonical upgrade target is thegram-memory@thegram-memory. Start a new agent session afterward; upgrading does not restart the current session.
Ask for help without exposing data
Section titled “Ask for help without exposing data”Contact support. Include the client, failed step, exact error code and this page’s URL. Do not send passwords, API keys, private document text or unredacted account screenshots. The page tools menu can open an email draft for a Docs issue; it does not send automatically.
For low-level errors, see MCP errors and write recovery.
Sources for this guide
Something different from this guide? Report a docs issue · Troubleshooting
Review and send the email yourself. Do not include API keys or private document content.