An r/perplexity_ai post asked how to use Perplexity Pro across an entire codebase like Claude Code or Codex. This walks the realistic recipe.
Prerequisites
- Perplexity Pro subscription ($20/mo)
- Comet desktop installed
- Scavio API key
- Editor of choice
Walkthrough
Step 1: Open Comet on the repo folder
Comet's local file access lets you reference code in chat.
// File → Open Folder → /path/to/repoStep 2: Attach Scavio MCP via Perplexity Pro+ MCP support
March 2026 feature: Settings → Connectors → Add MCP server.
// URL: https://mcp.scavio.dev/mcp
// Auth: API key (x-api-key)Step 3: Q&A questions referencing repo files
Comet handles file context; Scavio handles web context.
// 'In src/auth.ts on line 42, why does the JWT validation fail when the role claim is missing? Search for current best practices via scavio.'Step 4: Apply diffs manually in your editor
Honest tradeoff: Q&A-shaped, not seamless agent loop.
// Copy the suggested diff from Comet → paste into Cursor → review → save.Step 5: Re-run iteratively
Fastest with explicit file references in each query.
// 'Now show me the same fix applied to src/auth.test.ts.'Step 6: Bridge to Codex/Claude Code via Comet Skill (optional)
If you want delegated deep research from those agents.
# Per github.com/ammarshah1n/comet-skill READMEPython Example
# Total tool spend: $50/mo (Pro $20 + Scavio $30). Cheaper than Claude Max for non-Opus-heavy users.JavaScript Example
// Config-only setup; no application code.Expected Output
Perplexity Pro answering repo-aware Q&A with live web search via Scavio MCP; manual paste-back for actual edits.