Troubleshooting
Check authorization, configuration and knowledge availability separately.
Setup opens sign-in again
enkeon connect validates the saved account session before reusing it. A missing or expired session requires authorization. Complete the browser flow, return to the terminal and let setup finish.
The client does not show Enkeon
Run npx enkeon doctor. Confirm that setup wrote configuration for the client you actually use. Restart that client if it loads MCP configuration only at startup. Do not publish diagnostic output containing credentials.
Connected, but recall returns nothing
Check these in order:
- Project: the client is connected to the project containing your knowledge.
- Processing: the source finished processing successfully.
- Scope: the requested branch and permissions include that source.
- Question: try a specific phrase or decision you can see in the retained records.
An empty result means no matching context was returned for that request. It does not prove that a statement is false or that the entire project is empty.
A result contains an old decision
Inspect its source and revision history. Record an explicit correction linked to the previous memory instead of adding an unrelated competing statement. Ask again within the same project scope.
Enkeon-E tools are missing
Availability depends on feature access, project configuration and client support. Reconnecting a client does not grant access to an unavailable feature. Check the tools exposed to that client before using an Enkeon-E workflow.
Report a reproducible issue
Include the client and CLI versions, the command used, the processing status and a redacted example. Share source identifiers only through an appropriate support channel; never include project keys or session tokens.