DocPro Cloud

A persistent AI development team for VS Code.

DocPro Cloud is not autocomplete. It is not a generic chatbot. It is not a silent repository uploader.

It is a memory-backed development system: four named AI specialists who remember your architecture decisions, your review history, your preferences, and where you left off — across every session.

Carl, Diana, Anthony, and Abish are named AI specialists — persistent behavioral contexts with role-specific memory. They are not human employees, contractors, or people behind the product.

The Team

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 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 — Junior Engineer, MIT CS '27. Full scholarship from Hyderabad, top of his class, competitive programming medals. Carl's apprentice. The one in the lab at midnight not because he has to be, but because he forgot to eat.

What the Team Does

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

Each session, the team loads your project memory, reads the prior review history, and starts smarter than the last session ended. Build Mode runs entire milestone queues autonomously and reports back.

Session Types

Install

1. Install the Extension — search "DocPro" in VS Code extensions (publisher docpro.docpro-app) or click Install above
2. Set up the MCP Server — the DocPro MCP server connects Claude Code to your team and runs in user space. On first run, the extension guides you through setup. On Windows, a signed PowerShell installer is provided — download it, verify the Authenticode signature and SHA-256 hash, then run it.
3. Configure — open the DocPro sidebar and paste your API key
4. Go — pick a session type and let the team work

Full install guide: docpro.cloud/getting-started For IT and security teams: docpro.cloud/for-it

Requires a DocPro account and IDE API key. docpro.cloud

Security

DocPro documents what is stored, what is encrypted, what remains searchable, what leaves the machine, and how deletion works.

• No default repo scan. Source code is not scanned or uploaded unless you paste it, attach it, or enable Workspace Indexing.
• Workspace Indexing is opt-in and off by default.
• Field-encrypted at rest. Text session content, team memory, and project context are stored as Fernet ciphertext with the key held outside the database.
• Plaintext call transcripts. Phone-call transcripts are stored as plaintext for memory synthesis — disclosed and documented on the Security page.
• Your control. Reset one team member, delete a project, or erase your account — deletion is in your hands.

Full security documentation: docpro.cloud/security

Proof

DocPro publishes inspectable evidence, not just claims:

• Proof Packet — redacted but inspectable artifacts: review ledger, remediation pass, audit pass, memory, Build Mode log, call record, and a security-claim map. docpro.cloud/proof-packet
• The Proof — the architecture, code patterns, and production metrics behind the memory and review claims. docpro.cloud/proof
• For IT — deployment model, data flow, and the controls a security reviewer needs. docpro.cloud/for-it

Requirements

• VS Code 1.93 or later
• Claude Code installed and authenticated
• DocPro MCP server (set up via the install guide)
• DocPro account and IDE API key

How It Works

DocPro requires two components: the sidebar extension (what you're looking at) and the DocPro MCP server (the bridge that connects Claude Code to your team). Both are required. The install guide on docpro.cloud walks through the full setup.

DocPro is built on Anthropic's Claude and requires Claude Code to run. No fallback model, no model switcher, no abstraction layer.

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

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

docpro.cloud

God speed.