Skip to content
Support

Get back to what you’re building.

Start with the common fixes below. If you need a person, email ani@odstdio.com with your account email and workspace name. Leave tokens, passwords, and private memory out of the message.

Invite code or sign-in trouble?

Open your single-use invite link, enter your email, and verify that inbox to claim it. An email-bound invitation must use its invited address. New friend access lasts 60 days after verification, with unlimited core knowledge transfers; Jev is separate. Your workspace shows the exact end date and a link to ask for an extension. Unused links expire after seven days. Existing members sign in with email instead of reusing an invitation.

Open email sign-in

Check an agent connection.

Check that the agent is using your selected workspace’s key and the canonical MCP URL. Restart or refresh the MCP connection after setup. A saved key alone does not prove the agent has contacted Engram.

Follow the connection guide

Missing a memory or task?

Check the selected workspace. Look for the page in Memory and confirm the agent’s save succeeded. External work appears only when reported through Engram; connecting an agent does not capture everything it does.

Understand what gets recorded

Need an export or erasure?

Export readable memory and activity from Workspace settings. For account or workspace erasure, contact the operator. Page deletion is recoverable soft deletion, and ending a subscription does not erase data.

Read the request process

Run a read-only connection check.

npx @ani-hq/engram-mcp doctor codex

Replace the agent choice as described in the wiring guide. Doctor checks identity and the tool catalog without changing configuration. If the tool list loads but recall fails, check the workspace, connection permissions, and the actual error shown by your agent.

A self-hosted client needs its own configured URL. A hosted client should use https://engram.ani.computer/mcp. Do not send your access token in a support message.

Share the useful slice with your team.

Personal and team workspaces are separate. Team members can read the memory in their team workspace; connect your agents to a personal workspace for context you want to keep there.

Open Sharing in your personal workspace. Describe the topics and exclusions, choose a team or isolated agent, and review the exact excerpts before approving. Suggestions require your review. Existing full-workspace connections keep their prior access; disconnect or revoke those if an agent should read only the approved slice. Read how the model works, or ask for setup help. Do not send the private memory itself.

If the sign-in message hasn’t arrived.

Check spam and confirm the email address. Hosted access does not expose a raw login link when delivery fails. An existing member can request a new email sign-in link; an invitation must still be valid when its verification link is opened.

For a self-hosted installation without email, use the operator’s owner recovery path. The hosted console accepts verified email sessions, not agent keys.

Billing belongs to the workspace owner.

Owners manage subscriptions in Plan & billing. After a failed payment or ended paid period, reading, export, credential revocation, and privacy controls remain available. Complimentary access does not automatically cancel a separate subscription.

Compare hosting and plan details, or email us for billing help. Do not send payment-card information.

A human, at the other end.

ani@odstdio.com is the hosted support contact. Engram is operated by Outcome Driven Holdings LLC. We aim to acknowledge requests within two business days; this is a manual service target, not an incident-resolution SLA.

Include your account email, workspace name, the agent or browser you use, and the steps that led to the problem. A short error message is useful. Credentials, private memory, and another person’s data are not.

Found something that should stay private?

Send a private security report. Describe the issue and a minimal reproduction without live credentials or private user data. Please avoid putting sensitive details in a public repository issue.

For ordinary source bugs and local setup, see the repository and documentation. Self-hosted infrastructure is operated by its own administrator.