Perplexity CLI Codebase Walk

Overview

Workflow for solo developers using Perplexity Pro as a coding helper without a separate Claude Code or Codex subscription. Comet for repo-aware Q&A, Scavio MCP for typed web search, manual paste-back for edits.

Trigger

Per developer Q&A turn

Schedule

Per developer Q&A turn

Workflow Steps

Open Comet on the repo folder

Comet's local file access lets you reference code in the chat.

Attach Scavio MCP via Perplexity Pro+ MCP support

Settings → Connectors → Add MCP server (March 2026 feature).

Ask Q&A questions referencing repo files

Comet handles the file context; Scavio handles the web context.

Apply diffs manually in your editor

Honest tradeoff: Q&A-shaped, not seamless agent loop.

Re-run Q&A iteratively

Fastest with explicit file references in each query.

Python Implementation

Python

# Setup is config; example Scavio MCP add via Perplexity UI:
# Settings → Connectors → Add Custom MCP Server
# URL: https://mcp.scavio.dev/mcp
# Auth: API key (x-api-key)

JavaScript Implementation

JavaScript

// Config-only; no application code.

Platforms Used

Google

Web search with knowledge graph, PAA, and AI overviews

Frequently Asked Questions

This workflow uses a per developer q&a turn. Per developer Q&A turn.

This workflow uses the following Scavio platforms: google. Each platform is called via the same unified API endpoint.

Yes. Scavio's free tier includes 500 credits per month with no credit card required. That is enough to test and validate this workflow before scaling it.

Perplexity CLI Codebase Walk Workflow