PearAI

Overview

PearAI is an open-source AI code editor from PearAI (Pear Creations / PearAI Inc.), founded by Duke Pan and Nang Ang and backed by Y Combinator (F24). It ships as a desktop app built as a fork of Visual Studio Code, with AI chat and inventory features grounded in a fork of Continue plus integrated tools such as aider (Creator), Roo Code / Cline (Coding Agent), and third-party search/memory/apply helpers. The product pitch is not “one proprietary model UI,” but an inventory: curate strong open tools for each AI-coding layer and wire them into one VS Code–familiar shell.

Official site: trypear.ai. GitHub org trypear hosts the master monorepo, app, submodule, docs, landing page, and agent integrations. Positioning on the homepage emphasizes makers who currently paste code into ChatGPT/Claude, multi-model routing (“PearAI Model” / PearAI Router), and optional hosted inference so users do not have to manage API keys.

Key features

• VS Code–fork editor — Familiar layout, extensions ecosystem caveats of forks, command palette, and themes. Master repo notes TypeScript/Electron client; releases have tracked VS Code bases (e.g. 1.96.2 in v1.7.0).
• PearAI Chat (Continue lineage) — Sidebar chat with codebase awareness. Core shortcuts documented as CMD/CTRL+L (new chat / selection), CMD/CTRL+SHIFT+L (append), and CMD/CTRL+I for inline edits with diffs.
• @ context providers — Built-ins include @files, @codebase, @folder, @code, @docs, @terminal, @diff, @problems. Codebase retrieval uses local embeddings (all-MiniLM-L6-v2) stored under ~/.pearai/index; honor .gitignore and optional .pearaiignore.
• Slash commands — Examples from docs: /edit, /comment, /test, /commit, /cmd, plus product experiments like /sensei and /leetcode. Custom commands via ~/.pearai/config.json or config.ts.
• PearAI Inventory — Architecture overhaul (late 2024) introduced multi-webview inventory: Creator, Search, Chat, and later Agent as first-class surfaces rather than a single chat panel.
• PearAI Creator — Multi-file feature/bug/app generation. Launched powered by aider (high SWE-bench scores cited by PearAI); later messaging and changelog point at Roo Code / Cline for agentic creation. Config can BYOK Anthropic/OpenAI for Creator.
• PearAI Coding Agent — v1.8.0 (Feb 2025) introduced an agent that, with permission, accesses the development environment for feedback-loop coding; powered by Roo Code / Cline (updated through RooCode v3.10.2 in v1.8.6).
• PearAI Router / “PearAI Model” — Marketing claims automatic routing to strong coding models under one subscription so users do not juggle multiple frontier plans. Homepage scorecards compare “PearAI Model” vs GPT-4o / Llama / Claude snapshots (treat as marketing benchmarks, not independent lab results).
• PearAI Search & Memory — Search integrated Perplexity for web context; Memory integrated Mem0 (Dec 2024). Fast Apply via Relace (v1.6.0) speeds accurate code-block application.
• Tab autocomplete — Docs recommend installing Supermaven as an extension, or configuring Mistral Codestral as tabAutocompleteModel in config. PearAI has stated work on a hosted completion model; until then autocomplete is largely third-party.
• BYOK & local models — Documented providers include OpenAI, Anthropic Claude, Gemini, Azure OpenAI, Mistral, Ollama, Cohere, Groq, DeepSeek, Together, LM Studio, llamafile, Replicate, llama.cpp, WatsonX, and OpenAI-compatible endpoints.
• PearAI Server (optional) — Hosted convenience path so users can use frontier models without pasting keys; usage metered in credits. Server is semi-private; public issues live in a separate repo.
• Open source surface — Public GitHub org, bounties program, Discord-driven support. Continue fork permanently Apache 2.0; VS Code fork retains MIT. Telemetry stack historically includes Axiom (and PostHog mentioned in master README).

Pricing

PearAI is freemium. The editor itself is free to download and use. AI cost is either (1) your own API keys / local models or (2) a PearAI Server subscription marketed around $15 per month with early-bird “forever” discounts (site copy has advertised 20–30% off forever for early birds). Exact credit packs and current list prices should be confirmed on trypear.ai/pricing before purchase—UI sometimes emphasizes “try free” without spelling every meter rate on the marketing page.

Plan	Price	AI access	Notes
Free / open-source editor	$0	BYOK + local (Ollama, LM Studio, etc.)	Full editor; you pay model providers directly or run local weights
PearAI Server	~$15/mo (early-bird grandfathering advertised)	Monthly credit refill for frontier models via PearAI	Docs: Claude 3.5 Sonnet, GPT-4o, o1-mini/preview, Gemini 1.5 Pro; Haiku unlimited after credits exhaust; top-ups never expire

Credits reality: Official docs state cost depends on prompt size, output length, model, and which inventory tool you use (Chat, Search, Creator, etc.). Long threads re-send history as context and burn credits faster—docs recommend starting new chats often and attaching only relevant files. Top-up credits (when offered) are described as non-expiring; monthly plan credits refill on the subscription cycle.

Install: Download builds from the website (macOS/Windows/Linux coverage advertised; Linux has a dedicated blog guide). Optional: add pearai to PATH for pearai.. Authenticate with PearAI Server via in-app login (Command Palette → “Login to PearAI” if redirects fail). First Creator run may install aider/agent dependencies.

Limits & gotchas

• Not a clean-room IDE — Core AI UX descends from Continue; Creator/Agent from aider and Roo/Cline. PearAI’s disclaimer states integrations may be modified and branded under PearAI names for replaceability. Feature quality tracks those ecosystems as much as PearAI’s own UI glue.
• VS Code fork constraints — HN and marketplace discussions note Microsoft Marketplace and some official extensions (e.g. WSL) are licensed for Visual Studio products, not arbitrary forks. Expect extension gaps versus stock VS Code; import/state migration is improved but not magic.
• Credit burn & Haiku fallback — After monthly Server credits, docs say Claude 3.5 Haiku remains unlimited as a downgrade path. Agent/Creator quality may drop when you leave Sonnet/GPT-class models.
• Local index, not full-repo omniscience — Embeddings help high-level questions; docs warn @codebase is a poor fit for exhaustive “find every call site” or global refactors that need literal full-file coverage.
• Auth / protocol friction — Users have reported manual approval of pearai:// deep links on first login; Discord is the primary support channel rather than enterprise SLAs.
• Product velocity & “coming soon” — Homepage still lists Launch (Netlify), some Creator/Agent angles, and V2 messaging as evolving; changelog last major public entries cluster through early–mid 2025. Verify live build features after update.
• Telemetry & privacy — Local indexing stores embeddings on disk; Server/BYOK paths send prompts to third-party model hosts. Review current privacy policy and disable unnecessary telemetry if policy-sensitive. Prefer BYOK/local for regulated codebases.
• Trust history — September 2024 launch used a Continue-based product with a ChatGPT-generated proprietary license and weak fork attribution; founders publicly apologized and rebuilt true forks under Apache 2.0/MIT. That episode still shapes HN/Reddit reputation.
• Team/enterprise readiness — Public materials emphasize individual makers and Discord, not mature SSO/SCIM/audit packages comparable to Copilot Business or Cursor enterprise. Evaluate carefully for org-wide rollout.

Community sentiment

Sentiment is polarized and historically loud:

• Launch backlash (Sep–Oct 2024) — Hacker News threads (“We made two big mistakes,” YC “correcting the record,” fork mass-replace posts) and TechCrunch coverage focused on Continue cloning, Apache license mishandling, and YC due diligence optics. Reddit r/programming and ProgrammerHumor amplified the VC-funded-fork-of-a-fork meme.
• Remediation narrative — PearAI’s “Open Source Fixes” blog (true GitHub forks, Apache 2.0 permanence, zero-star repo reset) and YC’s clarifying post partially cooled legal concerns; trust recovery is incomplete among OSS purists.
• Product users — Product Hunt and testimonials on the homepage praise contextual chat vs copy-paste ChatGPT and cost consolidation of multiple AI subs. r/Codeium threads treat PearAI as a cheaper supplemental experiment versus Windsurf. YouTube reviews frame it as a free/open Cursor-class option with BYOK.
• Funding arc — TechCrunch (Dec 2024) reported the team raised about $1.25M seed including YC capital after surviving “cancellation,” while shifting product story toward inventory and creator tooling.

Community consensus in plain language: interesting open inventory idea and real free/BYOK path—but the 2024 license fiasco is part of the brand, and agent quality largely rides upstream Continue/Roo/aider rather than a unique closed model moat.

Who should use it

• Makers and indie builders who want a VS Code–like AI IDE without locking into a single closed editor, and who are comfortable living on Discord + changelogs.
• Privacy- or cost-sensitive developers who prefer free shell + Ollama/LM Studio/local embeddings, or BYOK with their own spend caps.
• Users who like “best tool per layer” — chat (Continue lineage), multi-file edits (aider era), agent loops (Roo/Cline), search/memory plugs—inside one app rather than five CLIs.
• Open-source contributors willing to file issues, claim bounties, and accept early-product roughness.
• Not ideal for enterprises needing polished compliance, teams that require Microsoft-only Marketplace extensions, or buyers who only want a polished proprietary agent and are fine paying Cursor/Windsurf rates without OSS drama.

Alternatives

• Cursor — Polished proprietary AI IDE; stronger mainstream traction and agent UX if you do not need OSS inventory.
• Windsurf — Agentic IDE lineage (Codeium / later Devin Desktop story); compare credit pricing and multi-file Cascade-style flows.
• Continue — Upstream open-source assistant PearAI Chat forked; use if you want pure Continue in stock VS Code/JetBrains without a full editor fork.
• GitHub Copilot — Best fit inside Microsoft/GitHub enterprise workflows and stock VS Code.
• Claude Code — Anthropic agentic coding in terminal/IDE; pair with any editor if you mainly want Claude’s agent loop.
• Cline / Aider — Use the agents PearAI wraps, directly in VS Code or the terminal, for maximum control and fewer middlemen.
• VS Code + extensions — Stay on official VS Code if Marketplace compatibility and stability matter more than PearAI’s inventory shell.
• Tabnine — Privacy-oriented completion-focused alternative when autocomplete is the main need.

Verdict

PearAI is a real, downloadable, open-source-leaning AI IDE with a clear freemium bargain: free editor + BYOK/local, or about $15/month Server credits for multi-model convenience, inventory tools (Chat, Creator, Agent, Search, Memory, Fast Apply), and VS Code familiarity. Its differentiation is packaging—an inventory of strong OSS/agent tools—not a single secret model.

Choose it if you value openness, key control, and experimentation. Choose Cursor, Windsurf, or Copilot if you want maximum polish, extension compatibility, or enterprise packaging. Factor the 2024 Continue/licensing controversy into trust decisions, verify current credits on the pricing page, and run a week of real projects (especially Creator/Agent) before committing a team budget.