DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to move your MemoraX setup to a second device with Memorax Code

Connect a new machine to your MemoraX account by entering the saved username and API key locally.

Credentials. The API key in config.toml grants access to your MemoraX account, so keep it private and never paste it into chats, public issues, or project files.

Who it is forA developer who uses MemoraX Code on one machine and wants the same memory on a laptop or workstation.

The problemA second device has no MemoraX Code configuration, so its coding agent cannot read or write the same memory.

The outcomeThe new device is connected to your account and reports the local integration status without exposing the API key.

What you need first

  • Node.js 20+ (Node.js 24 LTS recommended)
  • At least one supported coding agent installed, such as Codex, Claude Code, or Cursor
  • A normal interactive terminal for setup, or a caller-provided API key for stdin setup
  • Network access for MemoraX search and writeback
  • On Linux, /usr/bin/secret-tool from libsecret and an available Secret Service for guest credentials

Steps

  1. On the configured device, open ~/.memorax-code/config.toml and copy the username and API key into your password manager, without pasting them into chats or project files.
  2. On the new device, run npm install -g @memorax/memorax-code to install the package.
  3. In a normal interactive terminal on the new device, run memorax-code setup --existing-account and enter the username and API key locally.
  4. Restart or refresh each detected coding agent on the new device.
  5. Run memorax-code status from the project directory to check the local Backend and client integrations.

Prompt for your agent

On this machine, run `memorax-code status` from the <project path> directory and report the status of each detected client integration. Do not print, copy, or move the API key. Verify that the output shows whether each Hook runtime is observed or unverified.

Caveat. The README asks you to enter credentials in a local terminal on the new device, and non-interactive setup should only receive the key through stdin from a caller that already holds it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page