Context as Code

Universal. Portable. Yours.

Your codebase tells the story of WHAT changed.
Your context tells the story of WHY.

Every AI coding agent can read it.
Every teammate who clones your repo gets the full story.
Every decision, discussion, and diagram — versioned in GitHub.

Join Early Access WaitlistView on GitHub
Universal Access
C
Claude
Cx
Codex
Cr
Cursor
↓
Context in GitHub
.context/ directory
↓
Accessible by any tool
No lock-in. Standard git repos.

The Cost of Context Fragmentation

Every AI coding session starts fresh. Every decision gets lost. Every teammate starts blind.

Starting Over, Every Time

Claude Code, Codex, Cursor — every agent, every session starts blind. "What did we decide about authentication?" → You explain. Again.

Lost Decisions

"Why Firebase over Supabase?" Buried in a chat from three weeks ago. Or was it a PR comment? Maybe Slack? Nobody remembers.

Scattered Knowledge

Architecture in Miro. Decisions in GitHub PRs. Discussions in AI chats. Code in repos. Nothing connects. Context lives nowhere.

Teams Without Context

New teammate clones the repo. Gets code. Misses everything else. Six months of decisions, discussions, and "why we built it this way" — gone.

It's not just inefficient. It's unsustainable.

Context That Lives With Your Code

Store context in GitHub. Version it like code. Access it from any tool.

Capture

As you work, context accumulates:

  • •Git commits: what changed
  • •Chat links: where decisions happened
  • •Architecture diagrams: how it fits together
  • •Meeting notes: who decided what
  • •ADRs: why this approach

Tools to capture:

  • → MCP server (Claude Code, etc.)
  • → CLI commands (any agent)
  • → Git hooks (automatic)

Store in GitHub

Context commits to your repo:

myproject/
  src/           ← Your code
  .context/      ← Your context
    sessions/
      2025-12-12-oauth.json
    architecture/
      auth-flow.mermaid
      api-structure.md
    decisions/
      adr-001-firebase.md
  • •Version controlled
  • •Team accessible
  • •Fork, branch, merge
  • •No proprietary formats

Universal Access

ANY agent or tool reads it:

AI Agents:

  • • Claude Code (via MCP)
  • • GitHub Codex (via CLI)
  • • Cursor (via files)
  • • Windsurf (via CLI)
  • • [Future agents]

Humans:

  • • Browse on GitHub
  • • PR reviews with context
  • • Onboarding docs
  • • Team knowledge base

One source. Infinite access.

Three Ways to Capture Context

MCP Server

Recommended for Claude

Model Context Protocol

Claude automatically captures and queries context:

"Let me save what we just did"

→ Context captured with chat link, commits, summary

"What did we decide about authentication?"

→ Retrieves past sessions automatically

Works with:

Claude Code, Claude Desktop

Setup:

{
  "mcpServers": {
    "wundr-context": {
      "command": "npx",
      "args": [
        "@wundr/context-mcp"
      ]
    }
  }
}
MCP Setup Guide →

Git Hooks

Automatic

Capture on Commit

Prompt for context on significant commits:

$ git commit -m "feat: add OAuth"
Capture context? (y/N) y
Session: OAuth implementation
Chat URL: [paste]
✓ Context saved & committed

Works with:

Any workflow, any agent

Setup:

wundr-context init
# Installs git hooks
Git Hooks Guide →

CLI Tool

Universal

Manual Control

Use from any terminal, any agent:

# Add context
wundr-context add \
--title "OAuth implementation" \
--commits abc123,def456
# Query context
wundr-context query "auth decisions"
# Timeline view
wundr-context timeline --since "1 week"

Works with:

Everything (Codex, Cursor, any shell)

Setup:

npm install -g @wundr/context-cli
CLI Documentation →

One Context Source. Every Agent.

Not locked to Claude. Not locked to any tool. If it can read git, it can read your context.

C

Claude Code

Cx

GitHub Codex

Cr

Cursor

W

Windsurf

Cl

Cline

Co

Copilot

?

Your Agent Here

All reading from the same GitHub repo.

No more explaining your project differently to each agent.
Switch tools freely. Context travels with you.

Why GitHub? Because Git is Universal.

Git is the language of collaboration in tech. Your context should speak it too.

Zero Lock-in

Standard git repos. No proprietary formats. Don't like our tools? Fork the repo. Build your own.

Team Collaboration

Clone → instant context for all teammates. New dev onboarding: git clone gives code AND context.

Version History

Context evolves with your codebase. See why decisions were made when they were made.

Git Workflows

Branch context for experimental features. PR reviews include context changes. Merge strategies for team consensus.

Platform Agnostic

Works with GitHub, GitLab, Bitbucket, self-hosted. Any git remote, any tool.

Beyond Coding

Same pattern extends to docs, design, operations. Anywhere teams use git.

Git workflow with context

Feature branch:

├── src/ (code changes)
└── .context/ (context changes)
└── sessions/
└── new-feature-exploration.json

PR Review shows:

  • •Code diff
  • •Context diff (why this approach?)

Merge to main:

  • •Code + Context together
  • •Full story preserved

Starting With Developers. Extending Everywhere.

Anywhere teams use git, context can travel. We're starting where the pain is acute.

Phase 1

Development

WE ARE HERE

AI-assisted coding with Claude, Codex, Cursor

  • •Architecture decisions
  • •Technical trade-offs
  • •Implementation notes
  • •Code review context

Status: In development

Beta access via waitlist

Phase 2

Documentation

Technical writing & knowledge bases

  • •Doc decisions & evolution
  • •Style guide choices
  • •Content strategy
  • •Writer collaboration

Status: Planned Q1 2026

Express interest

Phase 3

Design Systems

Component libraries & brand guidelines

  • •Design decisions
  • •Component evolution
  • •Brand rationale
  • •Cross-functional context

Status: Planned Q2 2026

Express interest

Phase 4

Operations

Runbooks, incidents, infrastructure

  • •Incident learnings
  • •Process decisions
  • •Infrastructure choices
  • •On-call context

Status: Planned Q3 2026

Express interest

Git isn't just for code anymore. It's for knowledge that matters.

Built on Principles That Matter

Universal Access

Works with any AI agent or tool. Not locked to any platform.

Team Collaboration

Git-native sharing. Clone once, context forever.

GitHub-Native

Lives where your code lives. Familiar workflows.

Branchable & Mergeable

Fork, branch, PR your context. Just like code.

Open Format

JSON anyone can read. No proprietary lock-in.

Extensible

Start with code. Extend to docs, design, ops.

The Path Forward

Phase 1: Local MCP Server

We are here

Week 1 (December 2025)

  • MCP server built
  • Core tools: add_context, query_context, timeline
  • GitHub repo storage
  • Testing on real projects (Orphai, Ground Control)

Next: Landing page, public launch

Phase 2: Public Beta

Week 2-3 (December 2025)

  • Public GitHub repo
  • Comprehensive documentation
  • Demo video
  • Waitlist beta invites
  • CLI tool published to npm
  • Community feedback loop

Success metric: 50+ active beta users

Phase 3: Cloud Sync (Optional)

Weeks 4-6 (January 2026)

  • Web dashboard for context exploration
  • Optional cloud backup/sync
  • Team collaboration features
  • GitHub OAuth integration
  • Context sharing beyond git

Model: Free local, paid cloud features

Phase 4: Beyond Coding

Q1-Q2 2026

  • Documentation workflows
  • Design system context
  • Operations runbooks
  • Enterprise features
  • Advanced search & analytics

Vision: Universal context infrastructure

Get Early Access

Be among the first to experience AI coding with perfect memory.

Data handled by Wundr Space Ltd (Company No. 15698755).
Privacy Policy