pentimento (n.) — an earlier layer of a painting, visible beneath the surface; the artist’s revision, preserved.

Take your agent work with you.

The real work happens inside your coding agents now: the prompts, the decisions, the dead ends. Pentimo turns those sessions and native memories into one durable project history, searchable and ready to start the next agent warm.

Join the macOS beta

Portable project memoryStarts local · Continues in Cloud

An ultraviolet-style painting showing a finished portrait with an earlier face visible beneath it. — Visible surfaceThe earlier composition remains.

Claude CodeCodexPiOpenCodeOne archive

projectpentimo

sourceclaude-code · main

YouAgent

fix oauth refresh loop

pentimo · claude-code · main · this machine

Create continuation pack

You · 14:22

Tokens expire mid-session. Where is the refresh loop, and why can both requests race it?

Claude Code · 14:39

Root cause

The refresh call and expiry check read the same stale token state. Both requests enter the branch before either one writes the replacement.

serialize refresh work behind one in-flight promise
re-check token state after acquiring the lock

const token = await refreshOnce()
return retry(request, token)

21 auth tests now pass. The source-native transcript remains available beneath this rendered view.

pnpm test auth → 21 passed

Illustrative Desktop view · based on the current Pentimo interface

The work behind the code, already together.

Open Pentimo and see the sessions, memories, evidence, and decisions your coding agents left across projects.

Every agent, one project history

Browse work by project across Claude Code, Codex, Pi, and OpenCode.

Evidence, not summaries

Read the conversation, commands, file changes, and test results, exactly as they happened.

Native memories included

Keep Codex and Claude Code memory files searchable beside the sessions that produced them.

Ready to continue

Hand the next coding agent a focused continuation pack instead of a cold start.

The portability layer for AI-agent work

The agent can change. The project memory remains.

No vendor will index its competitors’ sessions. Project memory needs a neutral layer whose incentive is portability, not lock-in. And you’ll never re-read a thousand transcripts yourself: your next agent will, pulling the exact moment it needs, right when it needs it.

Preserve

Sessions and native memories become one durable history.

Every session is captured with its project, agent, account, machine, timestamps, and evidence intact. One archive that outlives any single tool.

Local

Retrieve

Find the exact evidence behind a decision.

Search by project, agent, date, command, or file, and land on the exact messages, not a summary of them.

Local + MCP

Continue

Give the next agent the context of the last one.

Create a token-budgeted continuation pack, or let the next agent pull what it needs through Pentimo MCP.

Cross-agent

Own

Your archive, readable without us.

Everything lives on your disk and exports to Markdown, JSONL, or SQLite. Move it, back it up, or delete it. No lock-in.

User-owned

The code is the output. The session is the work.

The pull request no longer tells the story. How you prompted it, which approaches you rejected, what the tests proved. That reasoning belongs to the project, but today it sits in folders your tools treat as disposable cache.

Fragmented

Every tool keeps its own history. Nothing keeps the project’s.

Claude Code fixed the auth bug this morning. An hour later, Codex refactored the same module without knowing that. Each agent logs to its own folder, in its own format, blind to the others.

Unfindable

An agent already solved this. The session is in there somewhere.

The one you need is buried in thousands of files named by timestamp and UUID. You cannot tell what happened inside without opening each one, and the only search you have is grep.

Temporary

And one day it’s just gone.

Some tools delete sessions after thirty days. A dead laptop, a returned client machine, or a clean install takes everything at once. Months of working context disappear without a warning.

Pentimo Cloud

Laptops are temporary. The archive isn’t.

Pentimo Cloud keeps one archive alive across every machine you work on. Enable sync and your history follows you to the new laptop, the browser, and hosted search that understands meaning, not just keywords. You decide what syncs, project by project: client work can stay local forever. Desktop works without an account, and sign-in alone uploads nothing.

Desktop beta: Capture, text search, session reading, continuation packs, MCP, and exports, all on your machine. No account required.
Cloud beta: Sync across machines, browser access, and hosted search for approved testers. Upload begins only after an explicit review-and-enable step.
Coming next: Public sharing and team memory: the exact excerpt a teammate can open, the reasoning attached to a PR, the why that outlasts any laptop. Hosted introspection and safe environment restoration follow.

Keep the work. Join the beta.

Join the macOS beta

WorkOS manages beta access. Joining does not upload agent work or enable Cloud sync.