Asking questions

Once a repo is ready, asking is the easy part — but a little scoping and phrasing goes a long way.

Scope the question

Tick one or more repositories in the sidebar before you ask. peek treats the selected repos as a single corpus: ask one question and the team researches across all of them, stitching the findings into one answer with per-repo citations. Narrow the selection when you want a focused answer; widen it for cross-service questions.

Ask real questions

peek is built for the questions a teammate would answer, not keyword lookups. It shines on things like:

• "Where does authentication happen, and where's the session stored?"
• "What would it take to move billing onto Stripe?"
• "Draft an onboarding doc for the indexer service."
• "What breaks if I change the shape of this API response?"

Reading the answer

Answers stream in as they're written and cite the source files they're built from, so you can jump straight to the code instead of taking the model's word for it. Each chat is saved — reopen it later, or keep the thread going with a follow-up that builds on the same context.

Stopping a turn

Changed your mind mid-answer? Hit Stop. peek cancels the in-flight turn and keeps your question along with whatever was written so far — nothing is lost, and you only pay for the work that ran.

Prefer to ask from your editor or terminal? The same engine is available over MCP.