Getting Started
Panel & Chrome extension
The CLI is all you need. These are two optional, additive ways to see the same local state without a terminal open — a browser tab, and a Chrome extension.
Panel: the browser-tab cockpit
Run the developer cockpit as a live browser tab, auto-refreshing while you work:
codeledger panel serve
Open the printed URL (http://localhost:7420 by default). It shows current task context, selected files, next actions, session value, and merge memory. No account, no login — the page is served entirely by the CLI process running on your own machine.
Chrome extension: CodeLedger Panel
A small browser extension that shows the same local status as an always-available toolbar badge, plus a local review signal on GitHub pull request pages — without a browser tab you have to remember to keep open.
Setup
- Install “CodeLedger Panel” from the Chrome Web Store.
- Run
codeledger panel servein your project (same command as above). - Copy the pairing code it prints — or the same code shown on the Panel page itself — and paste it into the extension's popup, once.
- The toolbar badge and popup now reflect your project's live status. Pin the extension icon so it's always visible.
What it shows
- A colored toolbar badge (green / yellow / red) reflecting whether your context is healthy, needs attention, or is high-risk — glanceable without opening anything.
- A popup with a plain-language status line, your project name, and how fresh the data is (“Checked 2 minutes ago”).
- On
github.com/*/pull/*pages, a small banner showing CodeLedger's own locally-computed review signal for that PR — silent when there's nothing local to say.
codeledger panel serve process on your machine that the browser-tab Panel talks to. Full detail: extension privacy policy.Choosing a surface
| If you... | Use |
|---|---|
| Just want the fastest, most scriptable workflow | CLI |
| Want a fuller cockpit view (merge memory, session value, search) while coding | Panel (browser tab) |
| Want an always-visible status without a dedicated tab, or want local PR signal on GitHub | Chrome extension |
They are not mutually exclusive — a common pattern is CLI for the actual activate/verify workflow, the Chrome extension pinned for ambient status, and the full Panel tab opened only when you want to dig into merge memory or session history.
Value by audience
Individuals
The Chrome extension turns “did I remember to run CodeLedger for this repo” into something you glance at, not something you have to remember. On a GitHub PR you're reviewing, the local risk signal shows up right where you're already looking.
Teams
Everyone sees the same plain-language status — no internal jargon — which lowers the bar for teammates who don't use the CLI daily to still benefit from its signal during review. Because it's read-only and local-only, rollout carries none of the usual new-tool, new-account friction.
Organizations
Nothing about the extension changes CodeLedger's data-handling posture: no new hosted service, no new account system, no new place data can leak to. Rollout is opt-in per developer, so one team can evaluate it before it's considered more broadly.