Skip to content
Slipstream agent · Code

Repo Guide

A repository onboarding guide agent for Claude Code, Codex and Cursor

Repo Guide writes an onboarding guide for an indexed repository, citing the files it describes. A run costs 500 credits, charged only when the run succeeds.

Or use it on slipstream.contextstream.io, signed in with your ContextStream account. Version 0.1.0 · Updated

What does Repo Guide do?

Writes an onboarding guide for an indexed repository: architecture, where things live, how to build, run and test it, with file:line citations and a diagram.

What it declines

A task like one of these is declined with a reason, and a declined run is free:

  • Changing code, writing tests or opening pull requests.
  • Reviewing a diff or a pull request.
  • Checking whether the docs are out of date (Docs Drift does that).
  • Answering questions that are not about how the repository is organised or used.

What does a real run of Repo Guide look like?

The input, the result (shortened where it is long), how long it took, what it cost and where it ran. Live runs used public or demo material only; a run marked as from the eval suite is not a live run.

Live run on ContextStream

An onboarding guide to the search tool of a public MCP server

Version
0.1.0
Outcome
succeeded
Ran
2026-10-27 17:19 UTC
Took
16.1 s
Cost
500 credits

ContextStream's Demos workspace (demo material only), in a project that indexes the public repository github.com/contextstream/mcp-server at v1.0.34.

Input
{
  "project_id": "6aad1065-8086-4114-931e-1b16c1d9b234",
  "focus": "the search tool"
}

Result

Summary

This is the ContextStream MCP server: a Rust workspace that exposes MCP domain tools (search, project, session and more) over stdio and HTTP, acting as a client of ContextStream's hosted API. For the search tool, start with the SearchTool struct and its ToolHandler impl in crates/mcp-tools/src/domains/search.rs, remembering that the public search surface is exactly four tools: search, search_semantic, search_hybrid and search_keyword.

Overview

The search tool is one domain module inside the mcp-tools crate. crates/mcp-tools/src/domains/search.rs holds the SearchTool struct (client, session manager, index keeper and an AtlasLayer for premium Atlas-backed modes) plus its ToolHandler implementation, which runs every request through a guided-search timeout path. The file is large and heavily sectioned: guided budget, degradation and recovery helpers sit alongside the execution code. Requests reach it through two doors. The mcp-server crate registers the tool and serves it over stdio and HTTP; crates/mcp-server/src/transport/http.rs contains the tool_search_response handler that validates the query and category arguments. Separately, the tool_search meta tool in crates/mcp-server/src/server.rs lets callers discover capabilities, and crates/mcp-tools/src/registry.rs scores candidates via search_candidate over name, title, description and discovery hints. Around the core sit the supporting pieces: crates/mcp-tools/src/domains/search_tests.rs pins the expected tool count, crates/mcp-tools/src/domains/session.rs adds SessionSmartSearchTool for session-scoped search, and crates/mcp-server/src/hook_handlers/pre_tool_use.rs maps the search tool name per editor format. docs/architecture.md states the boundary: this repository is a client of the hosted API and does not contain the backend, credentials or premium provider code.

Where things live

AreaCited atWhat it is
Search tool corecrates/mcp-tools/src/domains/search.rs:10363SearchTool struct, its constructor, the ToolHandler impl and the guided-search budget/degradation helpers.
Search execution entrycrates/mcp-tools/src/domains/search.rs:14000The ToolHandler impl that routes execute through execute_with_guided_timeout and declares the search metadata.
Search tool testscrates/mcp-tools/src/domains/search_tests.rs:5957Tests that pin the search surface to four tools and cover the unified search modes.
Tool registry and discoverycrates/mcp-tools/src/registry.rs:1245search_candidate scores registered tools by category, name, title, description and discovery hints.
tool_search meta toolcrates/mcp-server/src/server.rs:605Defines the tool_search meta tool schema used to find tools and hidden operations.
HTTP tool_search handlercrates/mcp-server/src/transport/http.rs:1821Validates query and category arguments and produces the tool_search response with telemetry.

Commands, each copied from the file it cites

  • scripts/release/gate.sh rust (test, scripts/release/gate.sh:4)
  • scripts/release/gate.sh checks (lint, scripts/release/gate.sh:4)

Diagram (Mermaid)

flowchart TD
  Client[MCP client] --> Server[mcp-server main]
  Server --> MetaTool[tool_search meta tool]
  Server --> HttpTransport[HTTP tool_search_response]
  MetaTool --> Registry[ToolRegistry search_candidate]
  HttpTransport --> Registry
  Registry --> SearchTool[SearchTool in domains search.rs]
  SearchTool --> ApiClient[ContextStreamClient]
  SearchTool --> SessionMgr[SessionManager]
  SearchTool --> IndexKeeper[IndexKeeper]
  SearchTool --> AtlasLayer[AtlasLayer]
  SessionMgr --> SmartSearch[SessionSmartSearchTool]

Where to start

  • crates/mcp-tools/src/domains/search.rs:10363: The SearchTool struct and every dependency it holds.
  • crates/mcp-tools/src/domains/search.rs:14000: How a search request actually executes, including the guided timeout.
  • crates/mcp-tools/src/domains/search_tests.rs:5957: Names the four search tools the surface must expose.
  • crates/mcp-server/src/server.rs:605: The tool_search meta tool schema callers use to discover tools.
  • docs/architecture.md:1: Sets the boundary of what this repository does and does not contain.
Checks: 4 of 4 passed
  • index_read: 14 of 14 lookups answered; 40 items found.
  • citations: Every reference is to an item found in the index or the workspace.
  • commands: 2 command(s), each written in a cited file.
  • workspace_context: 0 context items from ContextStream for this job, about 245 tokens.
  • 5 more areas are left out here.
Task
f40c0fbd-473b-4461-ada8-1e4b0f5d834e
Charged
0: it ran on ContextStream’s own account, which is not billed; a customer pays the price shown

What does Repo Guide cost?

Repo Guide costs 500 ContextStream credits a run, charged only when the run succeeds; a declined, failed, cancelled or timed-out run costs nothing. Credits come with every plan: Starter is free with 10,000 a month (20 runs of Repo Guide, if spent on nothing else), and Pro is $19 a month with 25,000.

Which tools does Repo Guide work with?

Claude Code, Codex, Cursor and other MCP clients: ContextStream's MCP gives them a slipstream tool that finds, runs and follows Repo Guide. It also runs from a terminal or an agent's shell with ss run guide, and from the ContextStream web app.

  • Claude Code, Codex, Cursor and other MCP clients: connect ContextStream's MCP once (setup for each editor), then ask your agent to hand the job to Repo Guide.
  • A terminal or an agent's shell: ss run guide, installed with ContextStream's command line.
  • The web app: the workspace's specialist library, where each run shows its price before it starts.

What access does Repo Guide need?

Repo Guide gets a short-lived token for one workspace, limited to 6 scopes: Searches code, Reads memory, Can save a note, Reads context, Marks cited context and Models via ContextStream. It works in one project, and only for that run.

Model agent. A program on ContextStream's model proxy, with a short-lived token that acts for you in one workspace. It is stopped after 2 min.

ScopeWhat it lets a run do
search.readSearch the workspace’s code, by keyword and by meaning.
memory.readSearch memory, and read decisions and lessons.
memory.write.noteSave one note per run.
context.readRead the run’s context pack from the workspace.
context.feedbackMark the context items a result cited as helpful.
model.invokeCall models through ContextStream’s model proxy, under the run’s credit cap.

How do I turn Repo Guide on?

An owner or admin of your ContextStream workspace turns Repo Guide on in the specialist library of the web app. Specialist agents are opening workspace by workspace; if yours is not open yet, the library says so.

  1. Sign in to ContextStream: the button below opens the specialist library on Repo Guide.
  2. An owner or admin switches Repo Guide on for the workspace.
  3. Pick the project it works in, and run it from the library, from your coding agent or with ss run.

How do I call Repo Guide from Claude Code or Codex?

Ask your coding agent to hand the job to Repo Guide, or call it yourself: ss run guide in a terminal, or slipstream(action="run", agent="guide", input={...}) over MCP. A priced run starts only once its price is accepted.

Connect ContextStream's MCP (it also writes each editor's connection):

curl -fsSL https://contextstream.io/scripts/mcp.sh | bash

A guide to the whole repository: its parts, its commands and where to start reading. Over MCP:

slipstream(action="run", agent="guide", input={"project_id":"00000000-0000-4000-8000-0000000000a1"}, accepted_price_credits=500)

In a terminal (curl -fsSL https://contextstream.io/cs/install.sh | sh installs ss):

ss run guide project_id=00000000-0000-4000-8000-0000000000a1

Over MCP, a call without accepted_price_credits returns the quote first; ss asks on a terminal, and scripts pass --yes.

Input

FieldTypeWhat it is
project_idstring, requiredThe indexed project (repository) to explain.
focusstringA part of the repository to go deeper on, for example "the billing service".
save_notebooleanSave the guide as a note in the project.
Code

Docs Drift

documentation drift agent

Docs Drift finds statements in a repository's docs that its code no longer matches and proposes the edits as a diff.

800 credits a runEvals 7/7v0.1.0
Code

Code Oracle

code search agent

Code Oracle answers one question about where code is, what calls it, how it flows or where to change it, from the workspace's code index.

FreeEvals 202/212v0.2.0
Code

PR Reviewer

pull request review agent

PR Reviewer reviews one pull request's diff for bugs and for breaches of the workspace's decisions, lessons and preferences, citing the line and the constraint for each finding.

1,200 credits a runEvals 13/13v0.1.0

Every Slipstream agent