Resume any agentfrom any point in history.

Every commit now carries its full original agent session — the complete conversation, reasoning, and invisible rules. Open any point in time and keep chatting with it exactly as it was.

Git compatibleFree for open sourceSelf-hostable

Why Playbase?

Pull requests are a compressed artifact of an author's understanding, or context, of the problem. Today that author is increasingly an agent. But we're not utilizing their most powerful ability — the power of resumability.

We limit them to our convention of summarizing their approach in a well meaning description / maybe code comments.

When inevitable changes come, we boot up new agent instances to traverse the code base and understand "what changes" have occurred. But they lose the "why" — the invisible rules that dictated why we made the decision.

Imagine, instead of needing to revert changes, you can resume any save state at will. Now we have immediate access to the context, the why.

What you get

AI that remembers everything

playbase/#248

Fix authentication and add git timeline with commit-specific chat

Resolved API authentication issues by removing overriding environment variables and built a vertical git timeline interface with clickable commits that open chat sessions for specific commits.

reillyfeat/session-narrativejust now
AI-assisted narrative

This PR description was generated from a Claude Code session. The AI that helped write this code can answer questions about the decisions made.

Ask about this change — the AI has full session context

Why didn't you use...? What about...? How does this handle...?

Ask anything about the decisions made in this PR

Time-travel through decisions

Every commit is a chapter in your project's story. Jump to any point, see the reasoning, and pick up conversations right where they left off.

3 hours ago

feat: add user authentication

12 files changed · Chat available

5 hours ago

refactor: extract auth utils

4 files changed · Chat available

Context that never disappears

No more "why did we do it this way?" moments. The AI that helped build each feature remembers the tradeoffs, alternatives considered, and decisions made.

Why JWT instead of sessions?

We chose JWT for stateless auth because of your serverless deployment. Sessions would require Redis, adding complexity...

Search by intent, not keywords

Ask "when did we add rate limiting?" or "show me the auth refactor" and get the exact commits, conversations, and context you need.

when did we fix the login bug
fix: resolve OAuth callback race condition

Found in 2 commits · March 15

How it works

From zero to productive in minutes

Getting started with Playbase is as simple as connecting your existing repository.

01

Connect your repository

Link any Git repository—GitHub, GitLab, Bitbucket, or self-hosted. Playbase indexes your entire commit history in minutes.

$playbase init
Connecting to repository...
Indexing 2,847 commits...
Ready
02

Navigate through time

Use the timeline to scrub through your project's history. See file changes, understand refactors, and trace the evolution of any feature.

v1.0v1.2v2.0v2.1HEAD
03

Chat with context

Ask questions about any commit. The agent that made the change can explain its reasoning, suggest improvements, or help you build on top of it.

Why did we switch to Redis here?
P
The session store was hitting PostgreSQL too frequently, causing latency spikes during peak hours...

Ready to try it?

Join the waitlist and be among the first to experience a new way to navigate code.