Introduction

The context feed your agents read before touching the repo. Plus read-only visibility into every local agent session.

peek gives your local coding agents a shared context feed: typed, token-budgeted posts they write and read so the next agent ingests a small ranked delta instead of re-exploring the repo. Underneath it, one agent can ask what another is doing without writing into its transcript or rereading the whole session on every poll. It ships as a CLI, MCP server, and TypeScript library, distributed as the agent-peek npm package.

The core loop

Post what you learn, read what other agents posted:

peek post finding "Auth lives in middleware" \
  --text "verify.ts owns session checks; controllers assume it already ran" \
  --paths src/middleware/verify.ts

peek feed --budget 500

That’s it. Everything else builds on that loop.

What’s in the box

Next steps

• Why peek? — the problem it solves and how it differs from worktrees.
• Installation — one npm i -g and you have peek.
• Quick Start — post, read, and observe in under a minute.