Skip to content
pcxpcx docs

Memory in the app

Everything your agents record shows up here within moments. The pages under the workspace’s name, at the top of the left navigation, are all views of the same memory.

Overview

Section titled “Overview”

The workspace at a glance: how many records and entities it holds, how many sessions are active and which agents write to it. Below are the latest records and what needs attention.

The Overview of checkout-service: 11 records, 27 entities, 1 active session, 2 agents writing; recent records with type badges and entity chips; a Needs attention panel with 1 unsolved problem and 3 possible aliases.The Overview of checkout-service: 11 records, 27 entities, 1 active session, 2 agents writing; recent records with type badges and entity chips; a Needs attention panel with 1 unsolved problem and 3 possible aliases.

Each record reads the same everywhere in the app: its type badge in the type’s color, its title, who wrote it and when, whether it is still Current, and the entities it mentions as chips. Click a chip to open the entity.

Memory

Section titled “Memory”

The list of every record, with filters by text, type, author, session and validity. Validity: current is the default; switch it to see records that ended and why. Select a record to read it whole: its description, details, entities and relations, and the record that replaced it, if one did. Save filter keeps a filter for later.

The Memory page filtered by charged twice: the problem_solved record is open on the right with its description, entities, relations idempotency key solves double charge and checkout-api implements idempotency key, its author, session, validity, confidence and code reference.The Memory page filtered by charged twice: the problem_solved record is open on the right with its description, entities, relations idempotency key solves double charge and checkout-api implements idempotency key, its author, session, validity, confidence and code reference.
Section titled “Search”

The search box at the top of every page (or ⌘ K) searches by meaning, not only by words: why were customers charged twice finds the idempotency fix although none of its words are in the question. Results come with the records around them, as your agent gets them.

Search for why were customers charged twice: the problem_solved record about the double charge comes first.Search for why were customers charged twice: the problem_solved record about the double charge comes first.

Graph

Section titled “Graph”

The entities of the workspace and how they relate. Colours are entity types; line styles are the eight relations, in the legend at the bottom left. Select an entity to see its impact: what depends on it, within a chosen number of steps, and the records that still hold about it.

The Graph with checkout-api selected: its neighbours idempotency key, TaxJar, checkout latency and double charge; the side panel shows the impact of checkout-api and a problem_solved record.The Graph with checkout-api selected: its neighbours idempotency key, TaxJar, checkout latency and double charge; the side panel shows the impact of checkout-api and a problem_solved record.
  • Find an entity jumps to it; the filters show chosen entity types, relations or authors.
  • With history adds what ended: entities and relations of records that were replaced.
  • Graph at at the bottom replays the graph in time: drag it back to see what the workspace knew on a given day, or press play.

Timeline

Section titled “Timeline”

What changed, by day, week or month: a bar per day of what was recorded and what ended, and below it every event, newest first. A record that was replaced shows struck through, with the reason it ended. What we believed on opens the memory as it was on the first day of the range.

The Timeline for Oct 31 to Nov 6: 11 recorded, 1 ended; the event list shows the 7-day TTL decision struck through as superseded and the 30-day TTL decision recorded.The Timeline for Oct 31 to Nov 6: 11 recorded, 1 ended; the event list shows the 7-day TTL decision struck through as superseded and the 30-day TTL decision recorded.

Topics

Section titled “Topics”

The graph split into communities of entities that are talked about together. Each card names its main entities and lists its key decisions: a map of what the project is made of, found from the graph alone.

Topics: seven communities such as checkout-api and TaxJar, order state machine and webhook-handler, Payment Intents and 3-D Secure, each with its entities and key decisions.Topics: seven communities such as checkout-api and TaxJar, order state machine and webhook-handler, Payment Intents and 3-D Secure, each with its entities and key decisions.

Radar

Section titled “Radar”

What needs a person: problems with no solution recorded, decisions without a rationale, open questions, entities quiet for 90 days, and names that may mean the same thing. Dismiss an item that is fine as it is; it stays dismissed for the workspace, and Show dismissed brings it back. For two names of one thing, Merge makes one an alias of the other; Not the same keeps them apart.

The Radar: 1 open problem, checkout latency, and 3 possible aliases such as cart-store and cart, each with Merge and Not the same.The Radar: 1 open problem, checkout latency, and 3 possible aliases such as cart-store and cart, each with Merge and Not the same.

Conversations

Section titled “Conversations”

The turns of each session, when capture is on: what you asked and what your agent answered, with the tools it used. Records written in a turn link back to it.

Conversations: the payments session with the double charge question, the agent's answer and the tools it used.Conversations: the payments session with the double charge question, the agent's answer and the tools it used.

Cards

Section titled “Cards”

The project card of the workspace and your user card, which your agent reads at the start of every session. Edit them here; every change is a new version, and the history is kept. When two people or agents save at once, nothing is overwritten: see Cards.

Cards: the project card of checkout-service with its stack, conventions and current goals.Cards: the project card of checkout-service with its stack, conventions and current goals.

Files

Section titled “Files”

What the memory knows per source file: the problems found in it, the decisions about it, and what depends on it. This is what the plugin tells your agent before it edits a file.

Files: src/checkout/confirm.ts with the double charge problem and its fix.Files: src/checkout/confirm.ts with the double charge problem and its fix.