Skip to content

Quickstart

Five minutes from a new account to an agent that remembers. You need Claude Code, or another agent from the list in step 4.

  1. Create an account

    Open app.pcx.is and choose Create an account. Give your name and email; a password is optional, without one you sign in with a link we email you. Open the confirmation link in the email, then sign in.

  2. Name your organization and first workspace

    An organization holds your workspaces, members and keys. A workspace is one project, usually named after its repository.

    The first onboarding step: an Organization field with Acme Robotics and a First workspace field with checkout-service.The first onboarding step: an Organization field with Acme Robotics and a First workspace field with checkout-service.
  3. Pick a plan

    Free is enough to start, and nothing is charged in this step. Pro is free for the first 2 months while pcx is new. See Plans and limits.

  4. Connect your agent

    The app makes your first API key and fills it into the commands. Copy the key now: it is shown once. You can make more keys in Connections.

    In Claude Code:

    /plugin marketplace add julymetodiev/post-cortex
    /plugin install post-cortex@post-cortex

    Then, once per machine, in a terminal:

    Terminal window
    pcx login --token <your key>

    No pcx yet? Give the key to the plugin instead: /plugin configure post-cortex@post-cortex and paste it as api_key. It is kept in your system keychain. More in Claude Code.

    The Connect your agent step: tabs for Claude Code, pcx CLI, claude.ai, Cursor, Codex, OpenCode, VS Code and Others, the plugin commands with Copy buttons, and Waiting for your first memory.
  5. See your first memory arrive

    Start a session in your project and ask your agent to remember something, for example “remember that we use Stripe Payment Intents for card payments, because they handle 3-D Secure for us”. The app is listening on the workspace and moves on as soon as the record arrives.

From now on your agent searches the memory before it answers and records what it learned after a change. The plugin’s hooks hold it to that: a turn that changed the project but recorded nothing is stopped and asked to record it. How your agent uses memory explains the loop.

Open the Overview to see what the memory holds.