Getting Started

Overview

Intraview lets you create living code tours with your AI agent. Your agent builds the tour, you refine it visually, and your team onboards faster. Tours are stored as JSON files in your repo, versioned with git, and work with any MCP-compatible AI.

Install

Install from the VS Code Marketplace. Works with VS Code, Cursor, Windsurf, and Roo Code.

Install from Marketplace

Intraview Works With Your Agent

Intraview doesn't have built-in AI. Instead, it provides prompts you share with your agent (Claude, Cursor, Copilot, etc.) to create tours collaboratively. Your agent creates and updates tours you can edit, navigate, and share.

How it works: Copy prompts from the sidebar or write your own. Your agent uses Intraview's MCP tools to build the tour.

MCP Connection

Tour creation requires your agent to be connected via MCP (Model Context Protocol). This connection lets your agent navigate code, create steps, and build tours within VS Code.

Check your connection: Look for the connection status in the Intraview sidebar. If not connected, run onboarding setup again or check your agent's MCP configuration.

Tour Workflow

Understanding how tours move from idea to sharing:

Draft All new tours start as drafts in .intraview/. Edit freely until you're satisfied.
Edit & Refine Click any tour to view it. Use the edit button to modify steps, titles, and descriptions.
Publish When ready, publish to move the tour to your docs folder for sharing with your team.

Managing Tours

The sidebar organizes tours into three sections:

Suggestions

Your agent analyzes your codebase and recommends tours. Click the copy icon next to any suggestion to get a prompt for your agent. Use "Request More Suggestions" to discover additional tour ideas.

Drafts

New tours start as drafts in .intraview/.cache/tours/. Incomplete drafts can be resumed by clicking "Complete Tour" to copy a prompt for your agent. Deleted drafts can be restored for 30 days.

Publishing

Publishing moves a complete draft to docs/tours/ (configurable in Settings). Published tours are regular JSON files you can commit to git and share with your team.

Important: Ensure your publish directory is not gitignored. You can unpublish a tour to move it back to drafts.

Editing Tours

Click the Edit button (pencil icon) on any tour to enter edit mode.

Step Cards

Each step appears as a collapsible card. You can:

Edit the title and subtitle directly
Drag steps to reorder
Delete steps or add new ones

Updating Line Ranges

Select the desired code range in the editor, then click "Use Selection" to update the step's file path and line numbers.

Rich Text Descriptions

The description editor supports bold, italic, lists, blockquotes, code blocks, and images from your workspace or web URLs.

Saving

Changes auto-save after 1 second of inactivity. You can also press Cmd+S / Ctrl+S. Click "Done" to exit edit mode.

Giving Feedback to Agents

Capture feedback with full context (file, line, code snippet) for review sessions or team alignment.

Inline Tour Feedback During a tour, click the feedback button on any step. Your feedback is automatically linked to the current file and line. Select additional code and use CMD+H / CTRL+H to add more context.
Standalone Feedback Select any code and use CMD+H / CTRL+H to open the feedback panel. You can also right-click and select "Intraview: Add Feedback".

Pro tip: Use standalone feedback for code review sessions or architectural discussions where you need to capture thoughts across many files.

Key Commands

Access via the Command Palette (CMD+Shift+P / CTRL+Shift+P):

Intraview: Re-open Onboarding -- Reconfigure MCP connections or see the welcome experience.
Intraview: Load Tour -- Quickly load and start a tour without opening the sidebar.
Intraview: Uninstall from Workspace -- Remove Intraview configuration. Does not delete tours or feedback in .intraview/.

Use Cases

Tours work best when you need to explain code in context:

Onboarding

Help new team members understand your codebase faster.

Feature Tours

Document how new features work end-to-end.

Complex PRs

Walk reviewers through large refactors or changes.

Agent Feedback

Give your agent inline feedback on its changes. It refines, you approve -- tight inner loop.