← Series Blueprint/STAGE 1: UNIVERSAL CAPTURE

Part 1: Universal Capture — Establishing the Zero-Friction Ingestion Layer

How enterprise engineering organizations capture multi-agent developer workflows across Gemini CLI, Antigravity, Claude Code, Cursor, Codex, and API proxies with zero code changes and pre-execution endpoint DLP secret masking.

Stage 1 Principle: You Cannot Govern What You Cannot Observe

Before an organization can monitor spend or enforce security governance, it must capture every developer AI interaction across all execution surfaces without introducing developer friction.

1. The Shadow AI Crisis in Modern Engineering

Developers today use a diverse spectrum of AI tools: Gemini CLI and Claude Code for terminal debugging, Antigravity and Cursor for IDE refactoring, Codex for automated loops, and custom internal scripts via LiteLLM proxies.

Without a unified capture plane, organizations face severe data risks: proprietary source code, internal schemas, and .env credentials leak to external LLMs, while high-value debugging breakthroughs disappear when terminal windows close.

2. Why Traditional Tracing SDKs Fail for CLI Coding Agents

Standard API proxies only see HTTP JSON strings. They miss three critical elements of developer AI workflows:

Local Tool Execution Outputs: HTTP proxies cannot see terminal stdout/stderr, command exit codes, or shell error states.
Line-Level Git File Diffs: Unstructured loggers cannot construct structured file diffs showing what code actually changed.
Developer Friction: Requiring developers to wrap their local scripts with SDKs causes widespread adoption failure.

3. The 4-Path Unified Capture Surface

01 / NATIVE CLI HOOKS (rclm-hooks)Direct event hooks for Gemini CLI, Antigravity, Claude Code, Cursor, and Codex.pip install rclm && rclm-hooks-install

02 / LOCAL API PROXYDrop-in LiteLLM proxy capture for internal tools and scripts.export OPENAI_BASE_URL="http://localhost:8000/v1"

03 / BROWSER ASSISTANT EXTENSIONCaptures ChatGPT, Claude.ai, and Gemini web research chats into the same timeline.

04 / HISTORICAL BACKFILL (rclm-sync)Backfills past local CLI transcripts so org history is complete from day one.rclm-sync --all

4. Pre-Execution Local Endpoint DLP Secret Masking

ReclaimLLM native hooks recursively inspect files matching .env, *.env, and .envrc on the developer laptop. Credentials and API keys are redacted locally and replaced with [REDACTED:API_KEY] before prompts or tool results ever touch the network.

5. RCLM MCP Server & Live Context Statusline

ReclaimLLM provides an official RCLM MCP Server (10 native tools including search_sessions, handoff, transfer_session, and file_brief) to query captured organizational memory directly from inside any coding assistant.

RCLM Claude Code Statusline: [context: 42% | 5-hr limit: 18% | model: claude-3-7-sonnet | branch: main]

← Series Blueprint Continue to Stage 2: Monitor & Observe →