Use the symptom below to choose a safe next step. Replace durmem.ai with your durmem server's address (for durmem, durmem.ai). If you share an error, redact sign-in codes, links, store keys, and the contents of stores.toml; issue reports may be visible beyond your team. For a first connection, see Install and set up durmem.
durmem command is not found#Follow the installer's PATH instructions, then open a new terminal. Check the installation with durmem --version. See Install the durmem command.
durmem setup finds no supported harness#Install and sign in to Claude Code, Codex, or OpenCode, then run durmem setup again (for a private server, durmem setup --base https://durmem.ai). Setup needs a supported harness to configure. If the computer only needs store access and has no coding agent to set up, use durmem login instead (for a private server, durmem login --base https://durmem.ai). See Install and set up durmem.
Setup may have completed for some selected harnesses and failed for another. Read the failed row, correct that harness's issue, and rerun setup for the intended harnesses (for a private server, add --base https://durmem.ai). A partial result is not the same as a successful setup.
| Symptom | Next step |
|---|---|
| A plugin or marketplace belongs to another server | Do not switch it silently. Choose the intended HTTPS server with --base, then follow the harness's removal and setup instructions. |
| Certificate verification fails for a private server | Ask the administrator for the right certificate and hostname. Use the scoped --ca-file option or install the certificate in the operating-system trust store; never disable verification. |
--base or a saved server address is rejected | Use the server's HTTPS origin, without a page path. Ask the administrator to confirm it if needed. |
| Setup asks for a restart | Start a new session in that harness so it reloads the connection. |
See Trusting a private server's certificate.
Use the same email when the command says it is safe to retry, and enter only the newest code at the hidden prompt. Do not put codes in command arguments. If hosted sign-in is not available, check the current account guidance. On a private server, ask its administrator about access and any email-free code procedure.
| Symptom | Next step |
|---|---|
| No sign-in email arrives | Check spam and wait before requesting again. Follow any retry guidance printed by the command. |
| A code is rejected | Request a new code and use only the latest one. |
| Provisioning is still pending or its result is unclear | Follow the command's retry instruction. For a store operation that may have changed server data, check the server before repeating it. |
| Consent was declined | Review the displayed policy and decide whether to try again. |
no input available | Run setup or login from an interactive terminal. |
loom_demo is not listed | durmem list_stores shows local connections, not server inventory. Run durmem login to refresh your connections (for a private server, durmem login --base https://durmem.ai), or ask the administrator which practice store to use. |
Run durmem list_stores to inspect this computer's configured connections. It does not prove a store still exists on the server. If the harness still uses old context after setup or login, start a fresh harness session and tell it which configured store and project to use. For a persistent project choice, see the workspace mapping.
Check the HTTPS address, network, VPN, and certificate trust with the server administrator. If a request may have reached the server before an error, check its outcome before retrying a create, delete, or other write. An error message alone does not prove that no change occurred.
Start a fresh harness session and check that its hooks are enabled and trusted. Claude Code's /hooks shows registered hooks; Codex must trust hooks from loom@loom. A working MCP connection does not prove hooks ran. See the harness-specific checks in Install and set up durmem.
The installer may need a fresh terminal before PATH changes take effect. If command output is garbled, check the terminal's display and encoding settings. If a step on this page does not match what you see on Windows, follow the installer's messages and ask your administrator, or use the support contact below.
For hosted installs, contact info@durmem.ai until public issue reporting opens. For private installs, contact your administrator first; for a software issue, open an issue in the private distribution repository. Report security vulnerabilities privately to info@durmem.ai. Redact credentials and personal data, and assume issue content can be visible beyond your team. Include your operating system, harness, durmem --version, and the exact redacted error.