Docs Tab for Claude Desktop: A Code Tab Reskin for Knowledge Workers

A detailed product feedback post on r/ClaudeAI proposes a new 'Docs' tab for Claude Desktop, targeting non-developer knowledge workers who manage structured documents under docs-as-code workflows. The core insight: Claude's existing Code tab infrastructure — repo-backed files, stateful agent loop, git operations, MCP integrations — is the exact stack needed, but the UI and vocabulary are too developer-oriented for compliance, legal, and policy teams.

The Problem

Knowledge workers currently face a trilemma:

• Word/Google Docs: friendly UI, but opaque binary formats, weak diffs, painful bulk edits, and AI struggles to edit cleanly.
• Notion/Confluence: nice editing, but proprietary storage — doesn't integrate with compliance platforms (Drata, Vanta, SecureFrame) that increasingly expect markdown-in-git as source of truth.
• VS Code + git + extensions: technically the right tool, but the UI is aggressively developer-branded. Asking a SOC 2 program manager to learn git commit is a non-starter.

The Opportunity

Claude already has two capabilities that, combined, solve this:

• Best-in-class long-form writing — widely acknowledged advantage over competing models for policy, legal, and prose work.
• The Code tab's agent loop — stateful file editing, git operations, worktree isolation, MCP integrations.

A Docs tab would be the Code tab with three changes: a markdown-first editor with live mermaid preview, a vocabulary swap that hides git, and document-workflow features (review, approval, PDF export, compliance-platform integrations).

What the Docs Tab Looks Like

It inherits from Code tab (no new infrastructure):

• Repo-backed file editing
• Claude agent loop with file read/write
• Git operations under the hood
• MCP integrations (Drata, Vanta, SharePoint connectors)

New for Docs:

• Split-pane markdown editor + live preview, mermaid renders as you type
• Vocabulary swap: Save (commit), Draft (branch), Send for Review (PR), Publish (merge), Workspace (repo), Document (file)
• Hidden developer chrome: no terminal, no debug, no file extensions in the tree
• Document templates: Policy, Procedure, BRD, RFC, Runbook, ADR, Meeting Notes
• "Insert Diagram" button with Claude-generated mermaid starters
• Review/approval UI for non-developers (GitHub PR review reskinned)
• One-click PDF/DOCX export with version hash in footer (auditor evidence)
• Native connectors for compliance platforms

Concrete Use Case

The poster describes a company using Drata for SOC 2 compliance. Drata supports markdown policies stored in git with built-in auditor renderers. The blocker is the editor — compliance and InfoSec teams won't adopt VS Code because it looks like a developer tool and the vocabulary is foreign. The poster states they'd pay for a Claude Desktop seat per compliance staffer if the Docs tab existed. This applies to every company running SOC 2, ISO 27001, HIPAA, PCI, or FedRAMP compliance — tens of thousands of companies using Drata, Vanta, or SecureFrame, all trending toward docs-as-code for audit version history.

Why Anthropic Specifically

Three arguments:

• Differentiation from ChatGPT Desktop: Claude's writing quality is the moat; ChatGPT's file/repo workflow is weaker.
• Broadens commercial base: opens compliance, legal, ops, consultancies, law firms, healthcare, financial services — segments willing to pay enterprise prices for audit-grade tooling.
• Reuses existing infrastructure: this is a UI/UX layer on top of already-shipped capabilities.