sidecar

a child repo for your repo

your-repo/ ├─ .sidecar# committed config └─ sidecar/# gitignored, shared, auto-synced, no merge conflicts
GitHub Star on GitHub 5 stars

Requires Node.js 20+ and git.

What you get

01

It's just git

The scratchpad is a normal repo you own — clone it, grep it, read it on GitHub, delete it if you want out.

02

Zero merge conflicts

Each machine writes to its own inbox branch; sidecar merges them so a sync never stops you to resolve anything.

03

Let your agents cook

Plans, notes, and context flow freely — no PRs to review, no conflicts to resolve, no history to keep clean.

04

Redacted by default

API keys and tokens are rewritten out of every push — PII too if you opt in. Your local files stay untouched.

Why

Your agents' planning docs, research notes, and context files don't belong in your code's history. They shouldn't reset when you switch branches or worktrees, and the latest version is the only one that matters.

sidecar keeps them in a separate git repo that lives inside your working tree — so agents and tools find them with zero configuration — while a background daemon keeps every clone in sync.

terminalsidecar status
$ sidecar status
main repo:     ~/dev/your-repo
sidecar path:  ~/dev/your-repo/sidecar
remote:        https://github.com/you/your-repo-sidecar.git
main branch:   main
inbox branch:  sidecar-inbox/zack/79ffcdaf92aa
checkout:      present
branch:        sidecar-inbox/zack/79ffcdaf92aa
dirty:         no
daemon:        running
last sync:     4 minutes ago (2026-07-25 11:58)
pending inbox: none

Docs