The real answers to the questions people actually run into while setting up or using Contexara. If your issue isn't here, contact us directly.
For account, billing, installation, recall, export, or deletion help, write to howdy@contexara.com with a safe description of the problem and any request ID. Do not include passwords, API keys, or another person's private content. We do not state a response-time guarantee here.
Generate an API key from your Keys page, then run the init command for your tool from a terminal:
npx contexara init --platform claude-code --api-key ctx_live_...
npx contexara init --platform codex --api-key ctx_live_...
npx contexara init --platform cursor --api-key ctx_live_...The installer writes the selected tool configuration. Confirm its result and follow the full quickstart guide for the browser-only Claude.ai path, which needs no terminal at all.
Your dashboard shows a setup card with a live status check until your first real message is captured and confirmed, no guesswork needed. If you want to check from the terminal directly:
npx contexara statusThis reports the local installer and queue state. It is useful diagnostic evidence, but it does not by itself prove that a memory has processed or that recall works in another tool.
MCP-capable tools (Claude Code, Claude Desktop, Cursor, Codex, and any MCP host) connect directly. See MCP setup for the connector URL and header format.
Run this first, it tells you exactly what's wrong:
npx contexara statusThree real causes this usually points to:
contexara init again with it.contexara init --platform <your tool> only after reviewing the proposed configuration.That's expected, a revoked key stops all future capture immediately. Your existing memory is completely safe and unaffected. Generate a new key and reconnect to pick up right where you left off, nothing is lost.
Recall can only surface content that has been captured and processed in the same account and permitted scope. A fresh setup may have little to return. If it still seems wrong, contact support with the prompt, approximate time, tool, and whether the expected source appears in Memory; do not paste confidential source material.
Still stuck? Contact us and we'll help directly.
Manage your plan from Pricing or your Billing page. Check the current plan terms before making a payment or requesting a change; support can review a payment reference when the account state is unclear.
The account should show the applicable limit and usage state. If the displayed state is unclear or appears incorrect, do not repeatedly retry a paid action; contact support with the account email and safe reference. See the Pricing FAQ for current plan information.
From your Account page, use Delete Account. The request blocks future use and starts removal of the declared account data. If a service reports a partial failure, retry only as instructed or contact support; do not assume a completed-looking screen proves every downstream cleanup has finished.
You can request an export before deleting from the Account page. Keep the export private: it may contain sensitive material. If export preparation fails, do not delete first if you need a copy; contact support with the safe error or request ID.
Do not pay again. Use the payment-status option if shown, then contact us with the payment reference. Support can investigate activation and review any refund request; neither outcome is guaranteed automatically.
Still stuck? Contact us and we'll help directly.