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

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.

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

Install — click Install above, or search "DocPro" in VS Code extensions
Configure — open the DocPro sidebar, enter your server URL and API key
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

Type	What It Does
Development Meeting	Scoping and planning — feasibility analysis, architecture decisions, milestone planning
Milestone	Execution — the team builds, tests, and delivers against a defined scope
Troubleshooting	Diagnosis — the team investigates issues, traces root causes, and fixes problems

Features

Branded sidebar — session form, connection status, audio trigger, update notifications
Institutional memory — the team remembers your project context across sessions
Audio transcripts — generate audio dramatizations of your sessions
Prompt protection — AES-256-GCM encryption at rest for all session prompts
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 account and API key (docpro.cloud)

How It Works

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. Every line of DocPro — backend, frontend, extension, MCP server — was 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. They used the product to build the product.

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

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

docpro.cloud

God speed.