Install. Connect.
Continue.

Qoopia is your own environment for long-term agent memory. Each installation stores its own notes, knowledge, agent spaces and history.

The current signed packages are available for macOS Apple Silicon and Linux x64. Download Qoopia.

Before installing: benefits, requirements and permissions · Перед установкой: польза, требования и доступы

1. Install your environment

macOS · Apple Silicon

Qoopia V1 requires macOS 15 or later on Apple Silicon. Intel Macs and Windows are not supported.

1. Obtain the DMG from the authorized release channel and verify the release checksum.
2. Open the DMG, move Qoopia to Applications, then open it.
3. Sign in with Google or your email address. For email, open the confirmation link.

Updating Qoopia on Mac

For an existing Mac installation, quit Qoopia and replace Qoopia.app in Applications once. Keep Application Support and your saved data. This installs the native updater; subsequent releases use Check for Updates in the Qoopia menu. Closing the window keeps Qoopia running in the menu bar.

Linux · x64, glibc 2.34+

Extract the TAR.GZ package. From its extracted directory, run:

./qoopia open

Keep the terminal open when running from it. The installer does not configure automatic startup at login. Your saved memory persists after closing the program.

You do not need to install Bun, Docker or Ollama for these packages. For cloud model features you need internet access and an available supported subscription.

Use an existing server you own

If you already manage a reachable Qoopia server, select that environment:

./qoopia use-server --url https://YOUR-SERVER --commit

Replace the address with your own server. This selects one environment; it does not synchronize two databases. The current environment is shown in the sidebar. A server deployment must provide its own reachable HTTPS endpoint, process supervision and backups.

2. Connect your agents

Open Connections in your selected Qoopia environment. Three independent authorizations have different purposes:

Claude Code / Codex

In Connections, choose your client and Read or Read and add. Apply the prepared setup, complete the client’s OAuth sign-in, then run the verification prompt in that client. A local installation can add the settings; for another computer, open the exported .qoopia-connection file with Qoopia there.

For automatic session context, also open Native session continuity in Connections and select Codex or Claude Code. This installs lifecycle hooks. Codex requires a one-time trust review in /hooks. On another computer, import the .qoopia-memory file. It contains a private key: keep it on your own device. An MCP connection alone does not enable session capture.

Claude Desktop · macOS

Choose Claude Desktop in Connections. Apply its local adapter, open the authorization link and approve access to your installation. Restart Claude Desktop and run the verification prompt in a real conversation. The adapter keeps its credentials outside the Claude configuration.

Claude in a browser

Enable external access in Connections and complete account confirmation. Qoopia prepares an HTTPS address. Add the connection using the official Claude form, approve access and verify it from Claude. Your installation must remain online.

ChatGPT Web / Desktop

ChatGPT Web and Desktop on Mac passed OAuth, verification, note creation, reading and retries without duplicates. Add the HTTPS address prepared in Connections and complete consent. Your account must allow custom MCP connections. Qoopia has no published directory entry. Use a normal ChatGPT conversation and the selected plugin.

Web clients cannot reach localhost. Managed external access makes your running installation reachable; it does not copy its memory into a shared cloud database. Browser MCP access does not automatically capture the full conversation or session events.

Other MCP clients

The owner or steward provides a separate agent identity with suitable permissions. Configure the MCP address and that identity in your runtime. Setup and session capture depend on the client; universal automatic capture is not promised.

Check the whole connection

1. Ask the agent to save a short, non-sensitive test note.
2. Ask it to find that note again.
3. Confirm the expected selected environment and agent identity.

“Saved authorization” means a permission was saved. It does not prove that the remote client has successfully called a memory tool.

3. Understand the boundaries

Your installation stores the memory. Built-in embeddings and keyword search run there. An authorized cloud model can receive permitted context through tool calls; background model features also use the separately authorized runtime. Self-hosting is not a promise that no data leaves your computer.

Each agent has its own identity and permissions. A steward is an agent you authorize to manage the environment. The role does not create or launch a persistent AI process. The same agent may be chosen as the external representative in Bridges.

Sign-in is a separate identity service. Review the current sign-in privacy information. Optional website analytics is off until you enable it in the footer. It records page views, download clicks and basic performance, without the contents of your memory or messages. Do Not Track and Global Privacy Control are respected.

4. Share with Bridges

1. Create a bridge group and generate an invitation. Send it only to the intended participant.
2. The participant requests to join from their own installation. Approve them in Members.
3. Prepare a separate copy in For sending. Publish its title and short description to the group’s catalogue.
4. An admitted participant requests a specific version. Choose Approve sending or Skip. Automatic sending is an explicit option for a specific version and group.
5. The copy arrives in Received. It is not automatically added to ordinary memory, installed as a skill, or forwarded.

Both installations need overlapping uptime for delivery. Received copies cannot be recalled. Pilot limits: 32 member records per group, 100 catalogue records and 1 MiB per item. There is no shared open repository of private notes.

If something is missing

• Download unavailable: Use the official download links on the home page. If a download fails, reload the release page and try again.
• Local address warning: cloud clients need reachable HTTPS, not a localhost URL.
• Wrong environment: check the sidebar host and selected server before saving anything.
• No automatic summary: check the separate model subscription in Memory and its current allowance.
• Old interface: reload after the new-version notice. Save unsent input first.

Official client references

• Claude: directory and custom connectors
• OpenAI: connect a custom ChatGPT integration