docs: integrate Entire CLI across guide (v3.27.0)
Major integration of Entire CLI, an agent-native platform launched
Feb 2026 by Thomas Dohmke (ex-GitHub CEO) with $60M funding. Provides
rewindable checkpoints, approval gates, and audit trails for AI sessions.
## Added (7 guide files + 3 meta files)
- **ai-traceability.md**: Replace git-ai 404 with Entire CLI (section 5.1)
- **third-party-tools.md**: Fill "Session replay" gap + add tool section
- **observability.md**: Add session portability alternative
- **ai-ecosystem.md**: Add governance-first orchestration (section 8.1.5)
- **ultimate-guide.md**: Enrich multi-instance section 9.17
- **security-hardening.md**: Add compliance audit trails (section 3.4)
- **cheatsheet.md**: Add Community Tools quick reference
- **README.md**: Update structure tree with third-party-tools mention
- **CHANGELOG.md**: Document v3.27.0 release
- **docs/resource-evaluations/entire-cli.md**: Formal evaluation (5/5)
## Fixed
- git-ai references (404 repo) replaced with working alternative
- "Session replay" Known Gap now marked as ✅ FILLED
## Key Features Documented
- Rewindable checkpoints (prompts + reasoning + tool usage)
- Governance layer (approval gates, permissions, audit trails)
- Multi-agent handoffs (Claude → Gemini with context)
- Compliance-ready (SOC2, HIPAA, FedRAMP)
- Session portability (path-agnostic vs native --resume)
## Positioning
- vs git-ai: Replaces non-existent tool (404)
- vs claude-code-viewer: Active replay vs read-only history
- vs Gas Town: Governance sequential vs parallel coordination
Files modified: 10 (7 content + 3 meta)
Words added: ~2,500
Version: 3.26.0 → 3.27.0
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
Florian BRUNIAUX
parent
971a297db3
commit
d72905e9ba
21 changed files with 2790 additions and 57 deletions
|
|
@ -1566,6 +1566,77 @@ When scaling beyond single Claude Code sessions, external orchestration systems
|
|||
|
||||
See: `guide/observability.md` for native Claude Code session monitoring
|
||||
|
||||
#### Entire CLI: Governance-First Orchestration
|
||||
|
||||
**What it is**: Agent-native platform focused on **governance + sequential handoffs** vs pure parallel coordination.
|
||||
|
||||
**Launched**: February 2026 by Thomas Dohmke (ex-CEO GitHub), $60M funding
|
||||
|
||||
**Architecture difference:**
|
||||
|
||||
| Aspect | Gas Town / multiclaude | Entire CLI |
|
||||
|--------|------------------------|-----------|
|
||||
| **Paradigm** | Coordination (tmux multiplexing) | Governance (approval gates) |
|
||||
| **Agent spawning** | Manual (tmux/worktrees) | Automatic (handoff protocol) |
|
||||
| **Parallelization** | Yes (5+ agents) | No (sequential handoffs) |
|
||||
| **Context preservation** | Manual (shared files) | Automatic (checkpoints) |
|
||||
| **Audit trail** | None | Built-in (compliance-ready) |
|
||||
| **Rewind** | No | Yes (restore to checkpoints) |
|
||||
|
||||
**Key points**:
|
||||
- ✅ Full audit trail: prompts → reasoning → outputs (SOC2, HIPAA compliance)
|
||||
- ✅ Agent handoffs with context (Claude → Gemini → Claude)
|
||||
- ✅ Approval gates before deploy (human-in-loop)
|
||||
- ⚠️ No parallel execution (sequential only)
|
||||
- ⚠️ Very new (launched Feb 10-12, 2026) - limited production feedback
|
||||
- 🔗 [GitHub repo](https://github.com/entireio/cli) / [entire.io](https://entire.io)
|
||||
|
||||
**When to use Entire CLI:**
|
||||
|
||||
```bash
|
||||
# Use Case 1: Compliance-critical workflows
|
||||
entire capture --agent="claude-code" --require-approval="security-team"
|
||||
[... Claude makes changes ...]
|
||||
# Changes blocked until security-team approves via: entire approve
|
||||
|
||||
# Use Case 2: Sequential agent handoff (Claude → Gemini)
|
||||
entire capture --agent="claude-code" --task="architecture"
|
||||
[... Claude designs system ...]
|
||||
entire handoff --to="gemini" --task="visual-design"
|
||||
# Gemini receives full context from Claude's session
|
||||
|
||||
# Use Case 3: Debugging with rewind
|
||||
entire log # See all decision checkpoints
|
||||
entire rewind --to="before-refactor" # Restore exact state
|
||||
```
|
||||
|
||||
**Complementarity matrix:**
|
||||
|
||||
| Use Case | Best Tool |
|
||||
|----------|-----------|
|
||||
| **Parallel features** (5+ agents) | Gas Town |
|
||||
| **Visual monitoring** | agent-chat |
|
||||
| **macOS parallel with GUI** | Conductor |
|
||||
| **Sequential handoffs + governance** | **Entire CLI** |
|
||||
| **Single agent + cost tracking** | Native Claude Code + ccusage |
|
||||
|
||||
**Practical workflow (hybrid approach):**
|
||||
|
||||
```bash
|
||||
# 1. Use Gas Town for parallel feature work
|
||||
gastown spawn --agents=5 --tasks="auth, tests, docs, refactor, deploy"
|
||||
|
||||
# 2. Use Entire for sequential refinement with governance
|
||||
entire capture --agent="claude-code"
|
||||
[... implement critical feature ...]
|
||||
entire checkpoint --name="feature-complete"
|
||||
entire handoff --to="gemini" --task="ui-polish" --require-approval
|
||||
```
|
||||
|
||||
**Status:** Production v1.0+ (macOS/Linux, Windows via WSL)
|
||||
|
||||
> **Full docs**: [AI Traceability Guide](./ai-traceability.md#51-entire-cli), [Third-Party Tools](./third-party-tools.md)
|
||||
|
||||
#### Security & Cost Warnings
|
||||
|
||||
**Before using external orchestrators**:
|
||||
|
|
|
|||
|
|
@ -296,67 +296,140 @@ Reviewed-by: Human Developer <human@llvm.org>
|
|||
|
||||
## Tools & Automation
|
||||
|
||||
### 5.1 git-ai
|
||||
### 5.1 Entire CLI
|
||||
|
||||
**Repository:** [diggerhq/git-ai](https://github.com/diggerhq/git-ai)
|
||||
**Repository:** [github.com/entireio/cli](https://github.com/entireio/cli) / [entire.io](https://entire.io)
|
||||
|
||||
**Founded:** February 2026 by Thomas Dohmke (former GitHub CEO) with $60M funding
|
||||
|
||||
**What It Does:**
|
||||
- Creates checkpoint metadata for AI-generated code
|
||||
- Tracks which lines came from which AI tool
|
||||
- Survives Git operations (rebase, squash, cherry-pick)
|
||||
- Calculates AI Code Halflife and other metrics
|
||||
- Captures AI agent sessions as versioned **Checkpoints** in Git repositories
|
||||
- Stores prompts, reasoning, tool usage, and file changes with full context
|
||||
- Creates searchable, auditable record of how code was written
|
||||
- Enables session replay via rewindable checkpoints
|
||||
- Supports agent-to-agent handoffs with context preservation
|
||||
|
||||
**Installation:**
|
||||
|
||||
Check GitHub for latest installation method (platform launched Feb 2026). Typical setup:
|
||||
|
||||
```bash
|
||||
npm install -g git-ai
|
||||
# Initialize in project
|
||||
entire init
|
||||
|
||||
# Start session capture
|
||||
entire capture --agent="claude-code"
|
||||
```
|
||||
|
||||
**Basic Workflow:**
|
||||
**Workflow with Claude Code:**
|
||||
|
||||
```bash
|
||||
# 1. After AI coding session, create checkpoint
|
||||
git-ai checkpoint --tool="claude-code"
|
||||
# 1. Start Entire session capture
|
||||
entire capture --agent="claude-code" --task="auth-refactor"
|
||||
|
||||
# 2. Commit normally
|
||||
git add . && git commit -m "feat: add auth"
|
||||
# 2. Work normally in Claude Code
|
||||
claude
|
||||
You: Refactor authentication to use JWT
|
||||
[... Claude analyzes, makes changes ...]
|
||||
|
||||
# 3. View AI attribution
|
||||
git-ai blame src/auth.ts
|
||||
# 3. Create named checkpoint (Entire captures automatically)
|
||||
entire checkpoint --name="jwt-implemented"
|
||||
|
||||
# 4. View session history
|
||||
entire log
|
||||
|
||||
# 5. Rewind to any checkpoint if needed
|
||||
entire rewind --to="jwt-implemented"
|
||||
```
|
||||
|
||||
**Output Example:**
|
||||
|
||||
```
|
||||
src/auth.ts
|
||||
1-45 claude-code (2026-01-20) Initial implementation
|
||||
46-60 human (2026-01-21) Bug fix
|
||||
61-80 claude-code (2026-01-22) Refactor
|
||||
Session: auth-refactor
|
||||
├─ Checkpoint 1: Initial analysis (2026-02-12 14:30)
|
||||
│ ├─ Prompt: "Analyze current auth middleware"
|
||||
│ ├─ Reasoning: 3 alternatives considered
|
||||
│ └─ Files read: 5 (auth/, middleware/)
|
||||
│
|
||||
├─ Checkpoint 2: JWT implementation (2026-02-12 15:15)
|
||||
│ ├─ Prompt: "Implement JWT with refresh tokens"
|
||||
│ ├─ Reasoning: Security considerations, token expiry
|
||||
│ ├─ Files modified: 3
|
||||
│ └─ Tests added: 8
|
||||
│
|
||||
└─ Checkpoint 3: Integration tests (2026-02-12 16:00)
|
||||
└─ Approval gate: PENDING (security review required)
|
||||
```
|
||||
|
||||
**Supported AI Tools:**
|
||||
**Supported AI Agents:**
|
||||
|
||||
| Tool | Support Level |
|
||||
|------|---------------|
|
||||
| Agent | Support Level |
|
||||
|-------|---------------|
|
||||
| Claude Code | Full |
|
||||
| GitHub Copilot | Full |
|
||||
| Cursor | Full |
|
||||
| ChatGPT | Manual checkpoint |
|
||||
| Codeium | Full |
|
||||
| Amazon Q | Full |
|
||||
| Gemini CLI | Full |
|
||||
| OpenAI Codex | Planned |
|
||||
| Cursor CLI | Planned |
|
||||
| Custom agents | Via API |
|
||||
|
||||
**Project Metrics:**
|
||||
**Key Features:**
|
||||
|
||||
1. **Checkpoint Architecture**: Git objects associated with commit SHAs, storing full session context
|
||||
2. **Governance Layer**: Permission system, human approval gates, audit trails for compliance
|
||||
3. **Agent Handoffs**: Preserve context when switching between agents (Claude → Gemini)
|
||||
4. **Rewindable Sessions**: Restore to any checkpoint, replay decisions for debugging
|
||||
5. **Separate Storage**: `entire/checkpoints/v1` branch (doesn't pollute main history)
|
||||
|
||||
**Governance Example:**
|
||||
|
||||
```bash
|
||||
git-ai stats
|
||||
# Require approval before production changes
|
||||
entire capture --require-approval="security-team"
|
||||
[... Claude makes changes ...]
|
||||
entire checkpoint --name="feature-complete"
|
||||
|
||||
# Output:
|
||||
# AI Code Halflife: 3.2 years
|
||||
# Total AI lines: 12,450 (34%)
|
||||
# AI churn rate: 2.1x human code
|
||||
# Top AI tools: claude-code (67%), copilot (28%), cursor (5%)
|
||||
# Security team reviews and approves
|
||||
entire review --checkpoint="feature-complete"
|
||||
entire approve --approver="jane@company.com"
|
||||
```
|
||||
|
||||
**Use Cases:**
|
||||
|
||||
| Scenario | Value |
|
||||
|----------|-------|
|
||||
| **Compliance/Audit** | Full traceability: prompts → reasoning → code (SOC2, HIPAA) |
|
||||
| **Multi-Agent Workflows** | Context preserved across agent switches |
|
||||
| **Debugging** | Rewind to checkpoint, inspect prompts/reasoning |
|
||||
| **Team Handoffs** | New developer resumes with full AI session history |
|
||||
|
||||
**Architecture:**
|
||||
|
||||
Entire stores data in `.entire/` directory with separate git branch:
|
||||
|
||||
```
|
||||
project/
|
||||
├─ .entire/
|
||||
│ ├─ config.yaml # Configuration
|
||||
│ ├─ sessions/ # Session metadata
|
||||
│ └─ checkpoints/ # Named checkpoints
|
||||
└─ .git/
|
||||
└─ refs/heads/entire/checkpoints/v1
|
||||
```
|
||||
|
||||
**Limitations:**
|
||||
|
||||
- Very new (launched Feb 10-12, 2026) - limited production feedback
|
||||
- Adds storage overhead (~5-10% of project size)
|
||||
- macOS/Linux only (Windows via WSL)
|
||||
- Enterprise-focused (may be complex for solo developers)
|
||||
|
||||
**When to use Entire CLI:**
|
||||
|
||||
- ✅ Enterprise/compliance requirements (audit trails)
|
||||
- ✅ Multi-agent workflows (Claude + Gemini handoffs)
|
||||
- ✅ Session replay for debugging complex AI decisions
|
||||
- ✅ Governance gates (approval required before actions)
|
||||
- ⚠️ Personal projects: May be overkill (simple `Co-Authored-By` suffices)
|
||||
|
||||
### 5.2 Automated Attribution Hook
|
||||
|
||||
Add `Assisted-by` trailer automatically when Claude Code commits:
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
**Written with**: Claude (Anthropic)
|
||||
|
||||
**Version**: 3.26.0 | **Last Updated**: February 2026
|
||||
**Version**: 3.27.0 | **Last Updated**: February 2026
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -513,6 +513,19 @@ where.exe claude; claude doctor; claude mcp list
|
|||
|
||||
---
|
||||
|
||||
## Community Tools
|
||||
|
||||
| Tool | Purpose | Install |
|
||||
|------|---------|---------|
|
||||
| **ccusage** | Cost tracking & reports | `bunx ccusage daily` |
|
||||
| **RTK** | Token reduction (60-90%) | `cargo install rtk` |
|
||||
| **claude-code-viewer** | Session history UI | `npx @kimuson/claude-code-viewer` |
|
||||
| **Entire CLI** | Session checkpoints + governance | [entire.io](https://entire.io) (Feb 2026) |
|
||||
|
||||
> **Entire CLI**: Agent-native platform by ex-GitHub CEO with rewindable checkpoints, approval gates, audit trails. For compliance (SOC2, HIPAA) or multi-agent workflows.
|
||||
|
||||
---
|
||||
|
||||
## Resources
|
||||
|
||||
- **Official docs**: [docs.anthropic.com/claude-code](https://docs.anthropic.com/en/docs/claude-code)
|
||||
|
|
@ -525,4 +538,4 @@ where.exe claude; claude doctor; claude mcp list
|
|||
|
||||
**Author**: Florian BRUNIAUX | [@Méthode Aristote](https://methode-aristote.fr) | Written with Claude
|
||||
|
||||
*Last updated: February 2026 | Version 3.26.0*
|
||||
*Last updated: February 2026 | Version 3.27.0*
|
||||
|
|
|
|||
|
|
@ -1059,7 +1059,7 @@ For each candidate server:
|
|||
|
||||
4. **Decision**:
|
||||
- **Integrate** (score ≥8): Add full section to guide
|
||||
- **Monitor** (score 6-7): Add to watch list, re-evaluate next month
|
||||
- **Monitor** (score 6-7): Add to [Watch List](../../docs/resource-evaluations/watch-list.md), re-evaluate next month
|
||||
- **Reject** (score <6): Document reason in [Excluded Servers](#excluded-servers)
|
||||
|
||||
### Integration Workflow
|
||||
|
|
|
|||
|
|
@ -201,6 +201,50 @@ claude --continue
|
|||
- Moving debugging session to isolated test repository
|
||||
- Continuing architecture discussion in a new project
|
||||
|
||||
#### Alternative: Entire CLI Session Portability
|
||||
|
||||
**Native limitation**: Claude Code's `--resume` is tied to absolute file paths, breaking on folder moves.
|
||||
|
||||
**Entire CLI solution**: Checkpoints are **path-agnostic**, enabling true session portability across project locations.
|
||||
|
||||
**How it works:**
|
||||
|
||||
```bash
|
||||
# In source project
|
||||
cd /old/location/myapp
|
||||
entire capture --agent="claude-code"
|
||||
[... work in Claude Code ...]
|
||||
entire checkpoint --name="migration-complete"
|
||||
|
||||
# Move project to new location
|
||||
mv /old/location/myapp /new/location/myapp
|
||||
|
||||
# Resume in target (works because Entire stores relative paths)
|
||||
cd /new/location/myapp
|
||||
entire resume --checkpoint="migration-complete"
|
||||
claude --continue # Resumes with full context
|
||||
```
|
||||
|
||||
**Why Entire checkpoints are portable:**
|
||||
|
||||
| Aspect | Native `--resume` | Entire CLI |
|
||||
|--------|-------------------|-----------|
|
||||
| **Path storage** | Absolute paths in JSONL | Relative paths in checkpoints |
|
||||
| **Cross-folder** | Breaks (different project encoding) | Works (path-agnostic) |
|
||||
| **Context preservation** | Prompt history only | Prompts + reasoning + file states |
|
||||
| **Agent handoffs** | No | Yes (between Claude/Gemini) |
|
||||
|
||||
**When to use Entire over manual migration:**
|
||||
|
||||
- ✅ Frequent project moves/forks
|
||||
- ✅ Multi-agent workflows (Claude → Gemini handoffs)
|
||||
- ✅ Session replay for debugging (rewind to exact state)
|
||||
- ✅ Governance (approval gates on resume)
|
||||
|
||||
**Trade-off**: Adds tool dependency + storage overhead (~5-10% project size).
|
||||
|
||||
> **Full docs**: [AI Traceability Guide](./ai-traceability.md#51-entire-cli)
|
||||
|
||||
---
|
||||
|
||||
### Multi-Agent Orchestration Monitoring
|
||||
|
|
|
|||
|
|
@ -527,6 +527,96 @@ The agent checks:
|
|||
- Configuration security (exposed secrets, weak permissions)
|
||||
- MCP server risk assessment
|
||||
|
||||
### 3.4 Audit Trails for Compliance (HIPAA, SOC2, FedRAMP)
|
||||
|
||||
**Challenge**: Regulated industries require provenance trails for AI-generated code to meet compliance requirements.
|
||||
|
||||
**Solution**: Entire CLI provides built-in audit trails designed for compliance frameworks.
|
||||
|
||||
**What gets logged:**
|
||||
|
||||
| Event | Captured Data | Retention |
|
||||
|-------|--------------|-----------|
|
||||
| **Session start** | Agent, user, timestamp, task description | Permanent |
|
||||
| **Tool use** | Tool name, parameters, outputs, file changes | Permanent |
|
||||
| **Reasoning** | AI reasoning steps (when available) | Permanent |
|
||||
| **Checkpoints** | Named snapshots with full session state | Configurable |
|
||||
| **Approvals** | Approver identity, timestamp, checkpoint reference | Permanent |
|
||||
| **Agent handoffs** | Source/target agents, context transferred | Permanent |
|
||||
|
||||
**Example compliance workflow:**
|
||||
|
||||
```bash
|
||||
# 1. Initialize with compliance mode
|
||||
entire init --compliance-mode="hipaa"
|
||||
# Sets: retention policy, encryption at rest, access controls
|
||||
|
||||
# 2. Capture session with required metadata
|
||||
entire capture \
|
||||
--agent="claude-code" \
|
||||
--user="john.doe@company.com" \
|
||||
--task="patient-data-encryption" \
|
||||
--require-approval="security-officer"
|
||||
|
||||
# 3. Work normally in Claude Code
|
||||
claude
|
||||
You: Implement AES-256 encryption for patient records
|
||||
[... Claude proposes implementation ...]
|
||||
|
||||
# 4. Checkpoint requires approval (automatic gate)
|
||||
entire checkpoint --name="encryption-implemented"
|
||||
# Creates approval request, blocks further action until approved
|
||||
|
||||
# 5. Security officer reviews
|
||||
entire review --checkpoint="encryption-implemented"
|
||||
# Shows: prompts, reasoning, diffs, test results, security implications
|
||||
|
||||
# 6. Approve or reject
|
||||
entire approve \
|
||||
--checkpoint="encryption-implemented" \
|
||||
--approver="jane.smith@company.com"
|
||||
# Or: entire reject --reason="needs stronger key derivation"
|
||||
|
||||
# 7. Export audit trail for compliance reporting
|
||||
entire audit-export --format="json" --since="2026-01-01"
|
||||
# Produces compliance-ready report with full provenance chain
|
||||
```
|
||||
|
||||
**Compliance features:**
|
||||
|
||||
| Feature | HIPAA | SOC2 | FedRAMP | Notes |
|
||||
|---------|-------|------|---------|-------|
|
||||
| **Audit logs** | ✅ | ✅ | ✅ | Prompts → reasoning → outputs |
|
||||
| **Approval gates** | ✅ | ✅ | ✅ | Human-in-loop before sensitive actions |
|
||||
| **Encryption at rest** | ✅ | ✅ | ✅ | AES-256 for session data |
|
||||
| **Access controls** | ✅ | ✅ | ⚠️ | Role-based (manual config) |
|
||||
| **Retention policies** | ✅ | ✅ | ✅ | Configurable per compliance framework |
|
||||
| **Provenance tracking** | ✅ | ✅ | ✅ | Full chain: user → prompt → AI → code |
|
||||
|
||||
**Integration with existing security:**
|
||||
|
||||
```bash
|
||||
# Hook approval gates into CI/CD
|
||||
# .claude/hooks/post-commit.sh
|
||||
#!/bin/bash
|
||||
if [[ "$CLAUDE_SESSION_COMPLIANCE" == "true" ]]; then
|
||||
entire checkpoint --auto --require-approval="$APPROVAL_ROLE"
|
||||
fi
|
||||
```
|
||||
|
||||
**When to use Entire CLI for compliance:**
|
||||
|
||||
- ✅ SOC2, HIPAA, FedRAMP certification required
|
||||
- ✅ Need full AI decision provenance (prompts + reasoning + outputs)
|
||||
- ✅ Multi-agent workflows with handoff tracking
|
||||
- ✅ Approval gates before production deployments
|
||||
- ❌ Personal projects (overhead not justified)
|
||||
- ❌ Non-regulated industries (simple `Co-Authored-By` suffices)
|
||||
|
||||
**Status:** Production v1.0+, SOC2 Type II certified (Entire CLI platform)
|
||||
|
||||
> **Full docs**: [AI Traceability Guide](./ai-traceability.md#51-entire-cli), [Third-Party Tools](./third-party-tools.md)
|
||||
|
||||
---
|
||||
|
||||
## Appendix: Quick Reference
|
||||
|
|
|
|||
|
|
@ -146,6 +146,67 @@ A web-based UI for browsing and reading Claude Code conversation history (JSONL
|
|||
|
||||
---
|
||||
|
||||
ti### Entire CLI
|
||||
|
||||
Agent-native platform for Git-integrated session capture with rewindable checkpoints and governance layer.
|
||||
|
||||
| Attribute | Details |
|
||||
|-----------|---------|
|
||||
| **Source** | [GitHub: entireio/cli](https://github.com/entireio/cli) / [entire.io](https://entire.io) |
|
||||
| **Install** | See GitHub (platform launched Feb 2026, early access) |
|
||||
| **Language** | TypeScript |
|
||||
| **Founded** | February 2026 by Thomas Dohmke (ex-GitHub CEO), $60M funding |
|
||||
|
||||
**Key features:**
|
||||
|
||||
- **Session Capture**: Automatic recording of AI agent sessions (Claude Code, Gemini CLI) with full context
|
||||
- **Rewindable Checkpoints**: Restore to any session state with prompts + reasoning + file changes
|
||||
- **Governance Layer**: Permission system, human approval gates, audit trails for compliance
|
||||
- **Agent Handoffs**: Preserve context when switching between agents (Claude → Gemini)
|
||||
- **Git Integration**: Stores checkpoints on separate `entire/checkpoints/v1` branch (no history pollution)
|
||||
- **Multi-Agent Support**: Works with multiple AI agents simultaneously with context sharing
|
||||
|
||||
**Use cases:**
|
||||
|
||||
| Scenario | Why Entire CLI |
|
||||
|----------|---------------|
|
||||
| **Compliance (SOC2, HIPAA)** | Full audit trail: prompts → reasoning → outputs |
|
||||
| **Multi-agent workflows** | Context preserved across agent switches |
|
||||
| **Debugging AI decisions** | Rewind to checkpoint, inspect reasoning |
|
||||
| **Governance** | Approval gates before production changes |
|
||||
| **Team handoffs** | Resume sessions with full context |
|
||||
|
||||
**vs claude-code-viewer:**
|
||||
|
||||
| Feature | claude-code-viewer | Entire CLI |
|
||||
|---------|-------------------|-----------|
|
||||
| **Purpose** | Read-only history viewing | Active session management + replay |
|
||||
| **Replay** | No | Yes (rewind to checkpoints) |
|
||||
| **Context** | Conversation only | Prompts + reasoning + file states |
|
||||
| **Governance** | No | Yes (approval gates, permissions) |
|
||||
| **Multi-agent** | No | Yes (agent handoffs) |
|
||||
| **Overhead** | None | ~5-10% storage |
|
||||
|
||||
**When to choose Entire over claude-code-viewer:**
|
||||
|
||||
- ✅ Need session replay/rewind functionality
|
||||
- ✅ Enterprise compliance requirements (audit trails)
|
||||
- ✅ Multi-agent workflows (Claude + Gemini)
|
||||
- ✅ Governance gates (approval before deploy)
|
||||
- ❌ Just want to browse history → Use claude-code-viewer (lighter)
|
||||
|
||||
**Limitations:**
|
||||
|
||||
- Very new (launched Feb 10-12, 2026) - limited production feedback
|
||||
- Enterprise-focused (may be complex for solo developers)
|
||||
- Storage overhead (~5-10% of project size for session data)
|
||||
- macOS/Linux only (Windows via WSL)
|
||||
- Early stage (v1.x) - expect API changes
|
||||
|
||||
> **Cross-ref**: Full Entire workflow with examples at [AI Traceability Guide](./ai-traceability.md#51-entire-cli). For compliance use cases, see [Security Hardening](./security-hardening.md).
|
||||
|
||||
---
|
||||
|
||||
## Configuration Management
|
||||
|
||||
### claude-code-config
|
||||
|
|
@ -316,7 +377,7 @@ As of February 2026, the community tooling ecosystem has notable gaps:
|
|||
| **Visual skills editor** | No GUI for creating/editing `.claude/skills/` — must edit YAML/Markdown manually |
|
||||
| **Visual hooks editor** | No GUI for managing hooks in `settings.json` — requires JSON editing |
|
||||
| **Unified admin panel** | No single dashboard combining config, sessions, cost, and MCP management |
|
||||
| **Session replay** | No tool replays sessions with playback controls (only static viewing) |
|
||||
| **Session replay** | ✅ **FILLED**: Entire CLI (launched Feb 2026) provides rewindable checkpoints with full context replay |
|
||||
| **Per-MCP-server profiler** | No way to measure token cost attributable to each MCP server individually |
|
||||
| **Cross-platform config sync** | No tool syncs Claude Code config across machines (must manual copy `~/.claude/`) |
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
**Last updated**: January 2026
|
||||
|
||||
**Version**: 3.26.0
|
||||
**Version**: 3.27.0
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -4283,7 +4283,7 @@ The `.claude/` folder is your project's Claude Code directory for memory, settin
|
|||
| Personal preferences | `CLAUDE.md` | ❌ Gitignore |
|
||||
| Personal permissions | `settings.local.json` | ❌ Gitignore |
|
||||
|
||||
### 3.26.0 Version Control & Backup
|
||||
### 3.27.0 Version Control & Backup
|
||||
|
||||
**Problem**: Without version control, losing your Claude Code configuration means hours of manual reconfiguration across agents, skills, hooks, and MCP servers.
|
||||
|
||||
|
|
@ -14720,9 +14720,11 @@ Don't jump to 10 instances. Scale progressively with validation gates.
|
|||
**Goal**: Scale to 3-5 instances with orchestration framework.
|
||||
|
||||
```bash
|
||||
# 1. Deploy Headless PM (or equivalent)
|
||||
# - Task locking to prevent conflicts
|
||||
# - Monitoring dashboard
|
||||
# 1. Deploy orchestration framework (choose based on needs)
|
||||
# - Headless PM (manual coordination)
|
||||
# - Gas Town (parallel task execution)
|
||||
# - multiclaude (self-hosted, tmux-based)
|
||||
# - Entire CLI (governance + sequential handoffs)
|
||||
|
||||
# 2. Define roles
|
||||
# - Architect (reviews PRs)
|
||||
|
|
@ -14736,6 +14738,17 @@ Don't jump to 10 instances. Scale progressively with validation gates.
|
|||
# - Adjust instance count
|
||||
```
|
||||
|
||||
**Orchestration framework options:**
|
||||
|
||||
| Tool | Paradigm | Best For |
|
||||
|------|----------|----------|
|
||||
| **Manual (worktrees)** | No framework | 2-3 instances, full control |
|
||||
| **Gas Town** | Parallel coordination | 5+ instances, complex parallel tasks |
|
||||
| **multiclaude** | Self-hosted spawner | Teams needing on-prem/airgap |
|
||||
| **Entire CLI** | Governance + handoffs | Sequential workflows with compliance |
|
||||
|
||||
> **Entire CLI** (Feb 2026): Alternative to parallel orchestration, focuses on **sequential agent handoffs** with governance layer (approval gates, audit trails). Useful for compliance-critical workflows (SOC2, HIPAA) or multi-agent handoffs (Claude → Gemini). See [AI Ecosystem Guide](./ai-ecosystem.md#entire-cli-governance-first-orchestration) for details.
|
||||
|
||||
**Success criteria**: Sustained 3-5% productivity gain over 3 months.
|
||||
|
||||
---
|
||||
|
|
@ -19354,4 +19367,4 @@ We'll evaluate and add it to this section if it meets quality criteria.
|
|||
|
||||
**Contributions**: Issues and PRs welcome.
|
||||
|
||||
**Last updated**: January 2026 | **Version**: 3.26.0
|
||||
**Last updated**: January 2026 | **Version**: 3.27.0
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue