Scope
Docs
Back to site

Quick Start

Get up and running with Scope in minutes.

Prerequisites

To use Scope, you need a codebase — either a GitHub repository or local files. Scope works with any language and framework — Ruby, Python, TypeScript, Go, Rust, and more.

1. Create your account

Sign up at within-scope.com/sign-up. You get a free tier with 200K tokens to explore everything Scope offers — codebase analysis, ticket generation, and MCP integration.

2. Create a project

From the dashboard, click New Project. Give it a name and an optional description. This is where all your feature specs, tickets, and codebase context will live.

3. Sync your codebase

There are two ways to get your codebase into Scope:

  • GitHub — Connect a repo from your project settings. Scope fetches and analyzes automatically.
  • Local sync — Call scope_sync via MCP to send file contents directly. Works with any local codebase.

Either way, Scope will:

  • Map entities, endpoints, relationships, and dependencies
  • Detect your tech stack, frameworks, and conventions
  • Build a searchable model of your project — without storing any source code

Privacy note: Scope processes your source code in memory and discards it. Only structured metadata (entity names, properties, relationships, conventions) is stored. See Sync Your Codebase for details.

4. Describe a feature

Use the project wizard or the Ask feature to describe what you want to build in plain English. Scope maps your description to existing code, asks clarifying questions, and identifies gaps.

5. Generate tickets

Once requirements are clear, generate implementation-ready tickets. Each ticket includes:

  • Real file paths to create or modify
  • Data models with complete structure
  • Acceptance criteria
  • Dependency ordering
  • Database changes when needed

6. Generate features from your IDE

With MCP connected, you can describe new features in natural language directly from Claude Code or Cursor — no need to leave your terminal:

analyze(type: "generate_feature", description: "Add user profile avatars")

Scope generates a preview of proposed tickets grounded in your codebase, detects the right milestone, and identifies impact on existing tickets. You review before anything is created. See Autonomous Workflow for the full flow.

7. Cross-repo context

If your project spans multiple repositories (e.g. frontend + backend), sync each repo as a separate Scope project. Your AI agent can query any project by passing project_id:

get_context(project_id: "backend_proj", scope: "entities:User+Order,api_design")

Your frontend agent understands the backend's entities and API contracts without reading a single backend file.

Next steps