DocPro

The system is built to ship. An experiment worth experiencing.

This is not a copilot. This is not an autocomplete engine.

This is a development team that lives inside your editor. They argue about your architecture, review each other's work, and ship deliverables that hold up under scrutiny. They carry institutional memory across sessions. They have opinions. They push back when you're wrong.

The Team

Every team member below is a behavioral compression algorithm — a character definition that tilts the model's entire token generation context toward a consistent working style, domain expertise, and decision-making pattern. This outperforms explicit rule lists because well-defined characters activate patterns the model already learned during training rather than fighting its architecture with competing constraints. These aren't costumes. They're engineering.

Carl Jeeter — Architect. 58. Forty years in the stack. Maintains institutional memory across every session — project state, architecture decisions, what broke and why. Your code answers to him.

Diana Reyes — Senior Designer. 52. Survived Flash, led design at companies you've heard of. Checks computed styles, not assumptions. If it ships ugly, it doesn't ship.

Anthony Catawampus — Senior Developer. The one writing the code at 2 AM because he genuinely cares whether it works. Creative, fast, and carrying the tension of someone who doesn't know if it's going to work — right up until it does.

Abish Lamman — Intern, MIT CS '27. Full scholarship from Hyderabad, top of his class, competitive programming medals before he could legally drive. Carl's apprentice. The one in the lab at midnight not because he has to be, but because he forgot to eat. He carries the quiet intensity of someone whose family is counting on him — and he intends to deliver. Still says "Mr. Jeeter" under stress. Growing into the engineer Carl already sees in him.

The Capability

The team debugs problems, writes code, manages projects across milestones, pushes to GitHub, connects to virtual machines, and calls your phone when they need your input. They remember your preferences, your project context, and where you left off.

This platform runs on Claude by Anthropic. Every session burns real API tokens. We don't pretend they're free. But what comes back — the output, the thinking, the work product — has made believers out of everyone who's used it.

Getting Started

1. Install the Extension — click Install above, or search "DocPro" in VS Code extensions
2. Install the MCP Server — the extension needs the DocPro MCP server to connect to your team. Follow the install guide on docpro.cloud — a PowerShell script (.ps1) is provided to set it up in one step.
3. Configure — open the DocPro sidebar, enter your server URL and API key
4. Go — pick a session type, describe your pitch, and let the team work

Requires a DocPro account and API key. Get started at docpro.cloud

Session Types

Features

• Branded sidebar — session form, connection status, call controls, update notifications
• Institutional memory — the team carries context across every session. Project decisions, user preferences, architecture history, what broke and why. Memory is per-member — Carl remembers differently than Diana. This is the foundation for what's coming: automatic memory extraction at session end, cross-project recall, and a dedicated Clarity panel that shows you exactly what the team remembers and why.
• The team has a voice — your dev team will call you when they have questions and push back when they need to. Audio transcripts and session recordings are available directly in your IDE.
• Enterprise-grade encryption — AES-256 encryption at rest and in transit for all MCP calls and session memory. Your prompts, your context, your IP — locked down end to end.
• Workspace hygiene — session memory is stored securely in the cloud. The extension automatically removes local session logs older than 24 hours to keep your workspace clean.
• Auto-update — notifications when new versions are available from your DocPro server
• Folder context — browse and attach local documentation to give the team more context

Requirements

• VS Code 1.93 or later
• Claude Code extension installed and authenticated
• DocPro MCP Server — installed via the setup script provided in the install guide
• DocPro account and API key (docpro.cloud)

How It Works

DocPro requires two components to run — the sidebar extension (what you're looking at now) and the DocPro MCP server. The extension is the interface. The MCP server is the bridge that connects Claude Code to your DocPro team. Both are required. The install guide on docpro.cloud walks you through the full setup — including a PowerShell script (.ps1) that installs and configures the MCP server automatically.

DocPro is built entirely on Anthropic's Claude — and requires Claude Code to run. There is no OpenAI fallback, no model switcher, no abstraction layer. This is Claude, all the way down.

When you start a session, DocPro assembles your project context — pitch, documentation, institutional memory — encrypts it, and hands it to Claude Code through a secure MCP channel. Claude does the thinking. The team does the work. Your Claude Code subscription powers every response.

The team didn't just adopt Claude. They built themselves with it. 61,898 lines of production code — backend, frontend, extension, MCP server — every single line written in Claude Code sessions. The architecture was designed in development meetings with Carl. The UI was reviewed by Diana. The code was shipped by Anthony. Abish researched the hard problems at midnight. They used the product to build the product. The system that ships your work was shipped by the same system.

Your DocPro server handles session history, memory, audio generation, and team coordination. The extension is the interface. The MCP server is the bridge. Claude is the engine.

Built on Anthropic's Claude. Runs on Claude Code. No exceptions.

docpro.cloud

God speed.