Cortex by Arc

Context infrastructure for agents

Bring that agent back.

Not another agent that remembers a few things about you. The one you worked with.

How?
agent~/payments-service
agentLedger writer is moved and the tests pass. Refunds next.
SamGood night. Same time tomorrow.
session ended
Sep 2 · Sam
This is a big move. Payments has lived on that box for six years.
Sep 9 · Sam
Don't touch the refund path without telling Priya. She owns reconciliation.
Sep 10 · Sam
Card numbers never go in our logs. It's the first thing the auditors check.
Sep 10 · agent
Tokenisation is live for new cards. Stored cards are still under the old key.
Sep 12 · Sam
No, not Redis. If the primary fails over we lose every in-flight key. Keep them in Postgres with the payment row.
Sep 12 · Sam
Drill passed on the first try. I won the bet. You're calling me Captain from now on 😄
Sep 14 · agent
Ledger writer is moved and the tests pass. Refunds still go through the old service; that's next.
Sep 14 · Sam
Open question for tomorrow: do partial refunds need their own idempotency key?
Sep 15 · Sam
Half joking: we could just put the keys in Redis and be done.
Sep 16 · agent
Starting the stored-card key rotation now.
agent = cx.boot()

Same model. Same repo. A stranger.

Too much, or too little.

Same model. Your history. That agent.

And it knows where the work is.

Nothing here was summarised. Every line points back to what you actually said.

Behind what you said: what it means now.

Same agent. Different work. Different context.

You say it's wrong. It's taken back.

Or it checks the repo, sees the mismatch, and asks.

Switch tools. Keep the agent.

Between sessions it keeps itself in order, and tells you what changed.

The window was one way in. Build on the primitives.

Sessions end. That agent doesn't have to.

  1. 1Add the Cortex skill to your agent.
  2. 2Type /cortex-onboarding. Your agent takes it from there.
Why this isn't magic: how it works →