docs: add Session Teleportation documentation (v3.9.4)

- Add Section 9.16 Session Teleportation in ultimate-guide.md (~105 lines)
  - Evolution timeline (2.0.24 → 2.1.0)
  - Commands: %, &, --teleport, /teleport, /tasks, /remote-env, Ctrl+B
  - Prerequisites, limitations, environment support matrix
- Update cheatsheet.md with new commands and shortcuts
- Update reference.yaml with new entries and line numbers
- Add cowork.md (collaboration guidance)
- Bump version to 3.9.4

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Florian BRUNIAUX 2026-01-19 15:35:24 +01:00
parent dd833bcc07
commit 3bc38ef982
9 changed files with 869 additions and 52 deletions

View file

@ -6,6 +6,70 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
## [Unreleased]
## [3.9.4] - 2026-01-19
### Added
- **Session Teleportation documentation** — New Section 9.16 in Ultimate Guide (~105 lines)
- Evolution timeline (2.0.24 → 2.1.0)
- Commands reference (`%`, `--teleport`, `/teleport`, `/tasks`, `/remote-env`, `Ctrl+B`)
- Prerequisites (GitHub App, clean git state, same account)
- Workflow example with step-by-step
- Environment support table (CLI, VS Code, Cursor, Web, iOS)
- Current limitations (research preview, unidirectional, GitHub only)
- Troubleshooting table
- Best practices
- Environment variables (`CLAUDE_CODE_DISABLE_BACKGROUND_TASKS`)
- Updated Section 9 Recap with "Advanced Workflows" category
- Updated `guide/cheatsheet.md` with teleportation commands
- Essential Commands: `/teleport`, `/tasks`, `/remote-env`
- Keyboard Shortcuts: `Ctrl+B`
- CLI Flags: `--teleport`
- Updated `machine-readable/reference.yaml`
- New `session_teleportation` deep_dive entry
- Commands: `/teleport`, `/tasks`, `/remote-env`
- Shortcuts: `Ctrl+B`
- CLI: `--teleport`
- Line numbers updated for sections after 9.15
## [3.9.3] - 2026-01-19
### Added
- **Claude Cowork documentation** — Complete guide for the new agentic desktop feature
- `guide/cowork.md` (NEW, ~460 lines) — Full documentation
- Architecture overview (local-first, sub-agents, no code execution)
- Comparison: Claude Code vs Cowork vs Projects
- 5 detailed use cases (file org, expenses, reports, travel, meetings)
- Security best practices (no official docs exist yet)
- Developer ↔ Non-Developer workflow patterns
- Known issues & troubleshooting
- Availability & roadmap
- `guide/ai-ecosystem.md` Section 9 (~90 lines) — Condensed integration guide
- Quick comparison table
- When to use what decision flow
- Security considerations summary
- Cross-reference to full guide
- `guide/ultimate-guide.md` — Cowork subsection in Section 11
- Comparison table and collaboration pattern
- Table of Contents updated
- `machine-readable/reference.yaml` — 8 new deep_dive entries for Cowork
- Updated `guide/README.md` navigation table
- Updated main `README.md` AI Ecosystem entry
## [3.9.2] - 2026-01-19
### Added
- **Alternative Providers section** in `guide/ai-ecosystem.md` (~55 lines)
- Documents existence of community workarounds (ANTHROPIC_BASE_URL, etc.)
- Clear disclaimer: not tested, not recommended, not supported
- Reasons to avoid: feature degradation, ToS risks, no support
- Better alternatives table: Aider for local models, Continue.dev for multi-provider
- External reading pointers (no step-by-step instructions intentionally)
- Updated Table of Contents
- Added `ai_ecosystem_alternative_providers` reference in `reference.yaml`
## [3.9.1] - 2026-01-19
### Added

View file

@ -6,8 +6,8 @@
<p align="center">
<a href="https://github.com/FlorianBruniaux/claude-code-ultimate-guide/stargazers"><img src="https://img.shields.io/github/stars/FlorianBruniaux/claude-code-ultimate-guide?style=for-the-badge" alt="Stars"/></a>
<a href="#"><img src="https://img.shields.io/badge/Lines-10,500+-blueviolet?style=for-the-badge" alt="Lines"/></a>
<a href="./examples/"><img src="https://img.shields.io/badge/Templates-63-green?style=for-the-badge" alt="Templates"/></a>
<a href="#"><img src="https://img.shields.io/badge/Lines-10,900+-blueviolet?style=for-the-badge" alt="Lines"/></a>
<a href="./examples/"><img src="https://img.shields.io/badge/Templates-61-green?style=for-the-badge" alt="Templates"/></a>
<a href="./quiz/"><img src="https://img.shields.io/badge/Quiz-227_questions-orange?style=for-the-badge" alt="Quiz"/></a>
</p>
@ -185,7 +185,8 @@ curl -sL https://raw.githubusercontent.com/FlorianBruniaux/claude-code-ultimate-
**What's inside**: Decision trees, command reference, context zones, MCP servers, agent templates, troubleshooting—optimized for machine consumption. Points to line numbers in the [full guide](./guide/ultimate-guide.md) for deep dives.
### 🔬 Deep Audit (Personalized Recommendations)
<details>
<summary><strong>🔬 Deep Audit (Personalized Recommendations)</strong></summary>
Get a comprehensive, **context-aware** audit that analyzes your project's README, CLAUDE.md files, and business domain to provide tailored recommendations:
@ -242,6 +243,8 @@ Based on ALL this context, provide:
**Want maximum depth?** Use [tools/audit-prompt.md](./tools/audit-prompt.md) (thinking is enabled by default with Opus 4.5)
</details>
### 🧠 Knowledge Quiz
Test your Claude Code knowledge with an interactive CLI quiz. **227 curated questions** covering all 14 guide sections, with immediate feedback and documentation links.
@ -397,28 +400,11 @@ Weak Areas (< 75%):
| **[Data Privacy](./guide/data-privacy.md)** | Data retention and privacy guide | ~10 minutes |
| **[Security Hardening](./guide/security-hardening.md)** | MCP vetting, injection defense, CVEs | ~25 minutes |
| **[Observability](./guide/observability.md)** | Session monitoring and cost tracking | ~15 minutes |
| **[AI Ecosystem](./guide/ai-ecosystem.md)** | Complementary tools (Perplexity, Gemini, Kimi) | ~25 minutes |
| **[AI Ecosystem](./guide/ai-ecosystem.md)** | Complementary tools (Perplexity, Gemini, Kimi, Cowork) | ~25 minutes |
| **[LLM Reference](./machine-readable/reference.yaml)** | Machine-optimized index (~2K tokens) | For Claude/AI assistants |
| **[Setup Audit](./tools/audit-prompt.md)** | Optimize your configuration | ~10 minutes |
| **[Examples Library](./examples/)** | Production-ready templates | Browse as needed |
### 🇫🇷 Whitepapers (French)
8 standalone documents covering Claude Code from zero to production (~185 pages total):
| # | Title | Audience | Pages |
|---|-------|----------|-------|
| **[#0](./whitepapers/00-introduction-serie.qmd)** | De Zéro à Productif | Everyone | ~8 |
| **[#1](./whitepapers/01-prompts-efficaces.qmd)** | Prompts qui Marchent | Dev Junior/Senior | ~12 |
| **[#2](./whitepapers/02-personnalisation.qmd)** | Personnaliser Claude | Senior/Power | ~15 |
| **[#3](./whitepapers/03-securite.qmd)** | Sécurité en Production | DevSecOps/TechLead | ~15 |
| **[#4](./whitepapers/04-architecture.qmd)** | L'Architecture Démystifiée | Architects | ~12 |
| **[#5](./whitepapers/05-equipe.qmd)** | Déployer en Équipe | TechLead/PM | ~12 |
| **[#6](./whitepapers/06-privacy.qmd)** | Privacy & Compliance | Compliance/Legal | ~10 |
| **[#7](./whitepapers/07-guide-reference.qmd)** | Guide de Référence Complet | Everyone | ~100 |
> **Reading paths by profile**: Junior (WP #0#1, 25 min) | Senior (#0#1#2#3, 1h15) | Tech Lead (#0#5#3#2, 1h15)
<details>
<summary><strong>Alternative Formats</strong> (Interactive AI, PDFs)</summary>
@ -433,7 +419,7 @@ Weak Areas (< 75%):
```
claude-code-ultimate-guide/
├── guide/ # 📖 Core documentation
│ ├── ultimate-guide.md # Complete reference (~10300 lines)
│ ├── ultimate-guide.md # Complete reference (~10900 lines)
│ ├── cheatsheet.md # 1-page printable reference
│ ├── architecture.md # How Claude Code works internally
│ ├── adoption-approaches.md # Team implementation strategies
@ -469,15 +455,10 @@ claude-code-ultimate-guide/
│ ├── github-actions/ # CI/CD workflows
│ ├── config/ # Configuration templates
│ ├── memory/ # CLAUDE.md templates
│ ├── mcp-configs/ # MCP server configurations
│ ├── modes/ # Behavioral modes (SuperClaude)
│ └── workflows/ # Advanced workflow guides
├── whitepapers/ # 🇫🇷 French whitepaper series (8 docs, ~185 pages)
│ ├── 00-introduction-serie.qmd
│ ├── 01-prompts-efficaces.qmd
│ ├── ...
│ └── 07-guide-reference.qmd
└── quiz/ # 🧠 Interactive knowledge quiz (227 questions)
```
@ -487,7 +468,8 @@ claude-code-ultimate-guide/
Copy-paste templates from [`examples/`](./examples/) for immediate use:
### Slash Commands
<details>
<summary><strong>Slash Commands</strong> (15 commands)</summary>
| Command | Purpose | Highlights |
|---------|---------|------------|
@ -507,6 +489,8 @@ Copy-paste templates from [`examples/`](./examples/) for immediate use:
| [/optimize](./examples/commands/optimize.md) | Performance analysis | Runtime, memory, bundle |
| [/ship](./examples/commands/ship.md) | Pre-deploy checklist | Tests, security, migrations |
</details>
### Utility Scripts
| Script | Purpose | Performance |
@ -515,7 +499,8 @@ Copy-paste templates from [`examples/`](./examples/) for immediate use:
| [audit-scan.sh](./examples/scripts/audit-scan.sh) | Setup audit scanner | ~2s |
| [update-cc-releases.sh](./scripts/update-cc-releases.sh) | Check for new Claude Code releases | ~1s |
### Security & Automation Hooks
<details>
<summary><strong>Security & Automation Hooks</strong> (8 highlighted, 15 total)</summary>
| Hook | Event | Purpose |
|------|-------|---------|
@ -528,7 +513,9 @@ Copy-paste templates from [`examples/`](./examples/) for immediate use:
| [notification.sh](./examples/hooks/bash/notification.sh) | Notification | macOS sound alerts |
| [auto-format.sh](./examples/hooks/bash/auto-format.sh) | PostToolUse | Auto-format with Prettier |
**[See All 14 Hooks](./examples/hooks/)** — Includes session-logger, security-check, claudemd-scanner, and more
**[See All 15 Hooks](./examples/hooks/)** — Includes session-logger, security-check, claudemd-scanner, and more
</details>
### GitHub Actions (CI/CD)
@ -630,7 +617,8 @@ Found an error? Have a suggestion? See [CONTRIBUTING.md](./CONTRIBUTING.md) for
---
## 📚 Related Resources
<details>
<summary><strong>📚 Related Resources</strong></summary>
### Complementary Guides
@ -655,6 +643,8 @@ Found an error? Have a suggestion? See [CONTRIBUTING.md](./CONTRIBUTING.md) for
- [Claude Code Docs](https://docs.anthropic.com/en/docs/claude-code) — Anthropic official reference
</details>
---
## 🌐 Ecosystem & Positioning
@ -743,7 +733,7 @@ Get notified about major updates, new templates, and Claude Code best practices:
---
*Version 3.9.1 | January 2026 | Crafted with Claude*
*Version 3.9.4 | January 2026 | Crafted with Claude*
<!-- SEO Keywords -->
<!-- claude code, claude code tutorial, anthropic cli, ai coding assistant, claude code mcp,

View file

@ -1 +1 @@
3.9.1
3.9.4

View file

@ -17,6 +17,7 @@ Core documentation for mastering Claude Code.
| [methodologies.md](./methodologies.md) | 15 development methodologies reference (TDD, SDD, BDD, etc.) | 20 min |
| [security-hardening.md](./security-hardening.md) | Security threats, MCP vetting, injection defense | 25 min |
| [ai-ecosystem.md](./ai-ecosystem.md) | Complementary AI tools (Perplexity, Gemini, Kimi, NotebookLM) | 25 min |
| [cowork.md](./cowork.md) | Claude Cowork: Agentic Desktop for Knowledge Workers | 15 min |
| [workflows/](./workflows/) | Practical workflow guides for Claude Code | 30 min |
### Workflows

View file

@ -17,7 +17,9 @@
- [6. UI Prototypers (v0, Bolt, Lovable)](#6-ui-prototypers-v0-bolt-lovable)
- [7. Workflow Orchestration](#7-workflow-orchestration)
- [8. Cost & Subscription Strategy](#8-cost--subscription-strategy)
- [Ready-to-Use Prompts](#appendix-ready-to-use-prompts)
- [9. Claude Cowork (Research Preview)](#9-claude-cowork-research-preview)
- [Appendix: Ready-to-Use Prompts](#appendix-ready-to-use-prompts)
- [Alternative Providers (Community Workarounds)](#alternative-providers-community-workarounds)
---
@ -696,6 +698,96 @@ claude
---
## 9. Claude Cowork (Research Preview)
> **Research Preview** (January 2026) — Limited documentation, expect bugs, local-only access. No production use recommended yet.
Cowork extends Claude's agentic capabilities to non-technical users via the Claude Desktop app. Instead of terminal commands, it accesses local folders to manipulate files.
**Official source**: [claude.com/blog/cowork-research-preview](https://claude.com/blog/cowork-research-preview)
### Quick Comparison
| Aspect | Claude Code | Cowork | Projects |
|--------|-------------|--------|----------|
| **Target** | Developers | Knowledge workers | Everyone |
| **Interface** | Terminal/CLI | Desktop app | Chat |
| **Access** | Shell + code | Folder sandbox | Documents |
| **Execute code** | Yes | **No** | No |
| **Outputs** | Code, scripts | Excel, PPT, docs | Conversations |
| **Maturity** | Production | **Preview** | Production |
| **Connectors** | MCP servers | **Local only** | Integrations |
| **Platform** | All | macOS only | All |
| **Subscription** | Usage-based | Max only (~$200/mo) | All tiers |
### When to Use What
```
Need code execution? → Claude Code
File/doc manipulation? → Cowork (if local files)
Cloud files/collaboration? → Wait (no connectors yet)
Ideation/planning? → Projects
```
### Key Use Cases
| Use Case | Input | Output |
|----------|-------|--------|
| **File organization** | Messy Downloads folder | Structured folders by type/date |
| **Expense tracking** | Receipt screenshots | Excel with formulas + totals |
| **Report synthesis** | Scattered notes + PDFs | Formatted Word/PDF document |
| **Meeting prep** | Company docs + LinkedIn | Briefing document |
### Security Considerations
> **No official security documentation exists yet.**
**Best practices**:
1. Create dedicated `~/Cowork-Workspace/` folder — never grant access to Documents/Desktop
2. Review task plans before execution (especially file deletions/moves)
3. Avoid files with instruction-like text from unknown sources
4. No credentials, API keys, or sensitive data in workspace
5. Backup before destructive operations
**Risk matrix**:
| Risk | Level | Mitigation |
|------|-------|------------|
| Prompt injection via files | HIGH | Dedicated folder, no untrusted content |
| Browser action abuse | HIGH | Review each web action |
| Local file exposure | MEDIUM | Minimal permission scope |
### Developer ↔ Non-Developer Workflows
**Pattern**: Dev specs in Claude Code → PM review in Cowork
```
┌─────────────────────────────────────────────────────────────┐
│ DEVELOPER (Claude Code) │
│ > "Generate a technical spec. Output to ~/Shared/specs/" │
└──────────────────────────────┬──────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ PROJECT MANAGER (Cowork) │
│ > "Create stakeholder summary from ~/Shared/specs/. │
│ Output as Word doc with timeline and risks." │
└─────────────────────────────────────────────────────────────┘
```
Shared context via `~/Shared/CLAUDE.md` file.
### Availability
| Aspect | Status |
|--------|--------|
| Subscription | Max only (~$200/month) |
| Platform | macOS only (Windows/Linux announced) |
| Waitlist | Available for Pro/Team plans |
| Stability | Research preview |
> **Deep Dive**: For complete security practices, troubleshooting, and detailed use cases, see [guide/cowork.md](./cowork.md).
---
## Appendix: Ready-to-Use Prompts
### Perplexity: Technical Spec Research
@ -806,4 +898,61 @@ Docs → Understanding: NotebookLM → Claude Code
---
## Alternative Providers (Community Workarounds)
> ⚠️ **Disclaimer**: This section documents techniques that exist in the community
> for **completeness only**. These methods are:
> - **Not tested** by the guide author
> - **Not recommended** for production use
> - **Not supported** by Anthropic
> - Subject to **ToS restrictions** from various providers
>
> **Our recommendation**: Use Claude Code with Claude models as intended,
> or use tools designed for multi-provider support (Aider, Continue.dev).
### What Exists
Claude Code reads `ANTHROPIC_BASE_URL` from environment variables, following
Anthropic SDK conventions. This is intended for enterprise gateways but can
technically point to any Anthropic-compatible API proxy.
### Known Environment Variables
| Variable | Purpose | Status |
|----------|---------|--------|
| `ANTHROPIC_BASE_URL` | API endpoint override | Undocumented for CC |
| `ANTHROPIC_MODEL` | Default model name | Semi-documented |
| `ANTHROPIC_AUTH_TOKEN` | API authentication | Official |
### Why We Recommend Against This
1. **Feature degradation**: WebSearch, MCP, extended thinking modes are
optimized for Claude and degrade with other models
2. **ToS risks**: Reverse-engineering proxies (e.g., for GitHub Copilot)
explicitly violate provider terms
3. **No support**: Anthropic cannot help debug non-Claude setups
4. **Maintenance burden**: Proxies break when providers change APIs
5. **Misleading outputs**: Non-Claude responses may not match expected behavior
### Better Alternatives
If you need local models or multi-provider flexibility:
| Need | Recommended Tool |
|------|------------------|
| Local models (Ollama, vLLM) | [Aider](https://aider.chat) |
| Multi-provider IDE | [Continue.dev](https://continue.dev) |
| Claude + local flexibility | Aider (supports both) |
### Further Reading (External)
For those who understand the risks and want to explore anyway:
- Community discussions on r/LocalLLaMA
- LiteLLM documentation for proxy setups
- GitHub search: "claude-code proxy"
*We intentionally do not provide step-by-step instructions.*
---
*Back to [Ultimate Guide](./ultimate-guide.md#11-ai-ecosystem-complementary-tools) | [Main README](../README.md)*

View file

@ -6,7 +6,7 @@
**Written with**: Claude (Anthropic)
**Version**: 3.9.1 | **Last Updated**: January 2026
**Version**: 3.9.4 | **Last Updated**: January 2026
---
@ -22,6 +22,9 @@
| `/plan` | Enter Plan Mode (no changes) |
| `/execute` | Exit Plan Mode (apply changes) |
| `/model` | Switch model (sonnet/opus/opusplan) |
| `/teleport` | Teleport session from web |
| `/tasks` | Monitor background tasks |
| `/remote-env` | Configure cloud environment |
| `/exit` | Quit (or Ctrl+D) |
---
@ -37,6 +40,7 @@
| `Ctrl+L` | Clear screen (keeps context) |
| `Tab` | Autocomplete |
| `Shift+Enter` | New line |
| `Ctrl+B` | Background tasks |
| `Ctrl+D` | Exit |
---
@ -283,6 +287,7 @@ VERIFY: Empty email shows error, invalid format shows error
| `-p "query"` | Non-interactive mode (CI/CD) |
| `-c` / `--continue` | Continue last session |
| `-r` / `--resume <id>` | Resume specific session |
| `--teleport` | Teleport session from web |
| `--model sonnet` | Change model |
| `--add-dir ../lib` | Allow access outside CWD |
| `--permission-mode plan` | Plan mode |
@ -397,4 +402,4 @@ where.exe claude; claude doctor; claude mcp list
**Author**: Florian BRUNIAUX | [@Méthode Aristote](https://methode-aristote.fr) | Written with Claude
*Last updated: January 2026 | Version 3.9.1*
*Last updated: January 2026 | Version 3.9.4*

462
guide/cowork.md Normal file
View file

@ -0,0 +1,462 @@
# Claude Cowork: Agentic Desktop for Knowledge Work
> **Reading time**: ~15 minutes
>
> **Purpose**: Understand Cowork's capabilities, limitations, and how it complements Claude Code for team workflows.
---
> **Research Preview** (January 2026) — Limited documentation available.
> Expect bugs, no production use recommended yet.
---
## Table of Contents
- [1. Overview](#1-overview)
- [2. Who Should Use Cowork?](#2-who-should-use-cowork)
- [3. Architecture](#3-architecture)
- [4. Claude Code vs Cowork vs Projects](#4-claude-code-vs-cowork-vs-projects)
- [5. Use Cases](#5-use-cases)
- [6. Security: Handle With Care](#6-security-handle-with-care)
- [7. Known Issues & Troubleshooting](#7-known-issues--troubleshooting)
- [8. Developer ↔ Non-Developer Workflows](#8-developer--non-developer-workflows)
- [9. Availability & Roadmap](#9-availability--roadmap)
- [Sources](#sources)
---
## 1. Overview
**Cowork** is Claude's agentic desktop feature that extends Claude's autonomous capabilities to non-technical users through the Claude Desktop app. Instead of terminal commands, Cowork accesses local folders and files directly.
### What is Cowork?
- **Research preview** released January 2026 for Max subscribers (macOS only)
- Extends Claude Code's agentic architecture to knowledge workers
- ~90% of Cowork was written by Claude itself ([Anthropic blog])
- Focuses on file manipulation, organization, and document generation
### Relationship to Claude Code
Cowork shares the same backend architecture as Claude Code:
- Same model capabilities (extended thinking, agentic loops)
- Same limitations (no internet access without explicit tools)
- Different interface: Desktop app vs Terminal
**Key difference**: Cowork cannot execute arbitrary code—it manipulates files only.
---
## 2. Who Should Use Cowork?
### Good Fit
| Persona | Use Case | Why Cowork |
|---------|----------|------------|
| **Project Manager** | File organization + status reports | Multi-step automation without coding |
| **Data Analyst** | Local CSV/Excel → formatted reports | Native Excel formulas output |
| **Writer/Editor** | Research notes → structured documents | Synthesis across many sources |
| **Operations** | Receipt screenshots → expense reports | Multi-format input processing |
### Poor Fit (For Now)
| Persona | Limitation | Alternative |
|---------|------------|-------------|
| **Security-conscious enterprises** | No audit trail, no access controls | Wait for enterprise features |
| **Heavy cloud users** | No Google Drive/Dropbox confirmed | Use native apps |
| **Anyone needing reliability** | Preview = bugs, unexpected behavior | Wait for stable release |
| **Code execution needs** | Files only, no scripts | Use Claude Code |
---
## 3. Architecture
### Local-First Design
```
┌─────────────────────────────────────────────────────────────┐
│ CLAUDE DESKTOP APP │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ COWORK ││
│ │ ┌─────────────┐ ┌─────────────┐ ┌─────────────────┐ ││
│ │ │ Sub-Agent 1 │ │ Sub-Agent 2 │ │ Sub-Agent 3 │ ││
│ │ │ (Analysis) │ │ (Transform) │ │ (Organize) │ ││
│ │ └──────┬──────┘ └──────┬──────┘ └───────┬─────────┘ ││
│ │ └────────────────┴─────────────────┘ ││
│ │ ↓ ││
│ │ ┌─────────────────────────────────────────────────────┐││
│ │ │ LOCAL FOLDER SANDBOX │││
│ │ │ ~/Cowork-Workspace/ │││
│ │ │ ├── input/ (your files) │││
│ │ │ └── output/ (generated files) │││
│ │ └─────────────────────────────────────────────────────┘││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ ┌─────────────────┐ │
│ │ CHROME INTEGRATION │ ← Web tasks (with explicit action) │
│ └─────────────────┘ │
└─────────────────────────────────────────────────────────────┘
```
### Key Technical Details
| Aspect | Details |
|--------|---------|
| **Access model** | Local folder sandbox (user grants permission) |
| **Cloud connectors** | Not confirmed (no Drive, Dropbox, etc. yet) |
| **Sub-agents** | Parallel execution with fresh context per agent |
| **Code execution** | **None** - Files only (no scripts, no commands) |
| **Browser** | Chrome integration for web research tasks |
| **Context limit** | ~200K tokens (~150-500 pages per session) |
| **Output formats** | Excel (.xlsx with formulas), PowerPoint, Word, PDF, text |
### What Cowork Cannot Do
- Execute shell commands or scripts
- Access cloud storage directly (as of Jan 2026)
- Run code in any language
- Access network resources without Chrome
- Persist memory across sessions (except via files)
---
## 4. Claude Code vs Cowork vs Projects
| Aspect | Claude Code | Cowork | Projects |
|--------|-------------|--------|----------|
| **Target user** | Developers | Knowledge workers | Everyone |
| **Interface** | Terminal/CLI | Desktop app | Chat interface |
| **Access** | Shell + arbitrary code | Folder sandbox only | Documents only |
| **Execute code** | Yes (full shell) | No | No |
| **Outputs** | Code, scripts, any file | Excel, PPT, docs | Conversations |
| **Maturity** | Production-ready | **Research preview** | Production-ready |
| **Security docs** | Extensive | None yet | Standard |
| **Context** | ~200K tokens | ~200K tokens | Project-scoped |
| **Memory** | CLAUDE.md files | Via files | Project knowledge |
| **Subscription** | Usage-based | Max only (~$200/mo) | All tiers |
| **Platform** | macOS, Linux, Windows | macOS only | All |
### Decision Flow
```
Need to execute code or scripts?
├─ Yes → Claude Code
└─ No → Need file manipulation?
├─ Yes (local files) → Cowork
├─ Yes (cloud files) → Wait or use native apps
└─ No (just conversation) → Projects
```
---
## 5. Use Cases
### 5.1 File Organization
**Scenario**: Messy Downloads folder with 500+ files
```
INPUT: ~/Downloads/ (mixed PDFs, images, zips, docs)
PROMPT: "Organize my Downloads folder. Create folders by type
and date. Move files, don't copy. Show me the summary."
OUTPUT: Organized structure + summary.txt
```
**Source**: [YouTube demo - File Organization]
### 5.2 Expense Tracking
**Scenario**: Receipt screenshots → Excel report
```
INPUT: ~/Receipts/ (20 JPG/PNG receipt photos)
PROMPT: "Extract expenses from these receipts.
Create an Excel file with Date, Vendor, Amount, Category.
Add a summary sheet with totals by category."
OUTPUT: expenses.xlsx with formulas + summary sheet
```
**Source**: [LinkedIn post - Expense tracking demo]
### 5.3 Report Synthesis
**Scenario**: Scattered notes → structured document
```
INPUT: ~/Notes/ (15 markdown files, 3 PDFs)
PROMPT: "Create a project status report from these notes.
Structure: Executive Summary, Progress by Area, Risks,
Next Steps. Format as Word doc."
OUTPUT: status-report.docx
```
**Source**: [Anthropic blog]
### 5.4 Travel Planning
**Scenario**: Multi-source research → itinerary
```
INPUT: ~/Trip/ (saved webpages, flight confirmations, Airbnb PDFs)
PROMPT: "Create a day-by-day itinerary for my Tokyo trip.
Include all confirmations, local recommendations,
and a packing checklist."
OUTPUT: tokyo-itinerary.docx + checklist.xlsx
```
**Source**: [YouTube tutorial - Travel planning with Cowork]
### 5.5 Meeting Preparation
**Scenario**: Multiple docs → briefing document
```
INPUT: ~/Meeting/ (company report PDF, LinkedIn profiles, news articles)
PROMPT: "Create a briefing doc for my meeting with Acme Corp.
Include: company overview, key people, recent news,
talking points, questions to ask."
OUTPUT: acme-briefing.docx
```
---
## 6. Security: Handle With Care
> **No official security documentation exists for Cowork yet.**
> The following is community-derived best practice.
### Risk Matrix
| Risk | Severity | Description | Mitigation |
|------|----------|-------------|------------|
| **Prompt injection via files** | HIGH | Malicious files with embedded instructions | Use dedicated folder, no untrusted content |
| **Browser action abuse** | HIGH | Cowork taking unintended web actions | Review each web action before approval |
| **Local file exposure** | MEDIUM | Accidental access to sensitive folders | Minimal permission scope |
| **Data exfiltration** | MEDIUM | Sensitive data leaving local system | No credentials in workspace |
| **Incomplete operations** | LOW | Half-finished file operations | Backup before destructive ops |
### Security Best Practices
1. **Create a dedicated Cowork folder**
```
~/Cowork-Workspace/
├── input/ # Files you want processed
└── output/ # Generated files
```
Never grant access to Documents, Desktop, or home folder directly.
2. **Review task plans before execution**
- Cowork shows its plan before acting
- Read each step, especially file deletions or moves
- Reject and refine if scope seems wrong
3. **Avoid instruction-like content in files**
- Don't process files containing "ignore previous instructions..."
- Be cautious with files from unknown sources
- Especially PDFs and documents with embedded text
4. **No sensitive data in workspace**
- No API keys, passwords, tokens
- No personal financial documents
- No confidential work documents
- No credentials in any format
5. **Backup before destructive operations**
- Before "organize my folder" → backup first
- Before "rename all files" → backup first
- Use Time Machine or manual copy
6. **Browser permission caution**
- Grant Chrome access only when needed
- Review each web action Cowork proposes
- Revoke access after task completion
### What NOT to Do
```
DANGEROUS: "You have access to my Documents folder"
DANGEROUS: "Process all files in ~/"
DANGEROUS: "Here's my password file, extract credentials"
DANGEROUS: "Process this PDF from an unknown sender"
RISKY: "Delete all duplicates" (without backup)
RISKY: "Reorganize everything" (scope too broad)
```
---
## 7. Known Issues & Troubleshooting
> Based on community reports (January 2026)
### Common Issues
| Issue | Description | Workaround |
|-------|-------------|------------|
| **Incomplete tasks** | Cowork stops mid-operation | Break into smaller, explicit steps |
| **Node.js download prompts** | Unexpected download dialogs | Accept or cancel, report to Anthropic |
| **Session timeouts** | Long tasks getting interrupted | Keep app active, smaller batches |
| **Browser actions failing** | Chrome integration not working | Grant explicit permissions in System Preferences |
| **Excel formula errors** | Generated formulas don't work | Verify regional settings (comma vs semicolon) |
| **File permission errors** | "Cannot access folder" | Re-grant permissions in Desktop app settings |
### Reporting Issues
Since this is a research preview, feedback is valuable:
- **General support**: support.anthropic.com
- **Feature requests**: Through the Claude Desktop app feedback
- **Community discussion**: Reddit r/ClaudeAI
### Recovery Procedures
**If Cowork stops mid-task:**
```
1. Check ~/Cowork-Workspace/output/ for partial results
2. Review what was completed vs planned
3. Restart with explicit next step
4. "Continue from where you stopped: [describe state]"
```
**If files are in unexpected state:**
```
1. Don't let Cowork "fix" without understanding
2. Review manually what changed
3. Restore from backup if needed
4. Restart with clearer instructions
```
---
## 8. Developer ↔ Non-Developer Workflows
One of Cowork's strengths is enabling collaboration between technical and non-technical team members.
### Pattern 1: Dev Specs → PM Review
```
┌─────────────────────────────────────────────────────────────┐
│ DEVELOPER (Claude Code) │
│ │
│ > "Generate a technical spec for the new auth system. │
│ Output as markdown in ~/Shared/specs/" │
│ │
│ Output: ~/Shared/specs/auth-spec.md │
└──────────────────────────────┬──────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ PROJECT MANAGER (Cowork) │
│ │
│ > "Review the auth spec in ~/Shared/specs/. │
│ Create a stakeholder summary with timeline estimates │
│ and risk assessment. Output as Word doc." │
│ │
│ Output: ~/Shared/docs/auth-summary.docx │
└─────────────────────────────────────────────────────────────┘
```
### Pattern 2: Research → Implementation
```
┌─────────────────────────────────────────────────────────────┐
│ ANALYST (Cowork) │
│ │
│ > "Research competitors' pricing pages. Save screenshots │
│ and create a comparison matrix in Excel." │
│ │
│ Output: ~/Shared/research/pricing-comparison.xlsx │
└──────────────────────────────┬──────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ DEVELOPER (Claude Code) │
│ │
│ > "Implement a pricing page based on the competitive │
│ analysis in ~/Shared/research/. Use our design system." │
│ │
│ Output: src/pages/pricing.tsx (+ tests) │
└─────────────────────────────────────────────────────────────┘
```
### Pattern 3: Shared Context via CLAUDE.md
For teams using both tools, create a shared context file:
```markdown
# ~/Shared/CLAUDE.md
## Project: Acme Platform v2
### Conventions
- All specs in ~/Shared/specs/
- All docs in ~/Shared/docs/
- All research in ~/Shared/research/
### Current Sprint
- Auth system redesign
- Pricing page implementation
- Q1 stakeholder report
### Key Decisions
- Using Clerk for auth (see specs/auth-decision.md)
- Tailwind for styling
- Q1 deadline: March 15
```
Both Claude Code and Cowork can reference this file for context.
---
## 9. Availability & Roadmap
### Current Status (January 2026)
| Aspect | Status |
|--------|--------|
| **Subscription** | Max only (~$200/month) |
| **Platform** | macOS only |
| **Waitlist** | Available for Pro/Team plans |
| **Stability** | Research preview (expect bugs) |
### Expected Future
| Feature | Status | Notes |
|---------|--------|-------|
| Windows support | Announced | No date |
| Linux support | Announced | No date |
| Cloud connectors | Unknown | Not confirmed |
| Pro plan access | Waitlisted | Expected 2026 |
| Enterprise features | Unknown | Audit trail, SSO, etc. |
### How to Get Access
1. **Max subscribers**: Enable in Claude Desktop app settings
2. **Pro/Team subscribers**: Join waitlist at claude.ai/cowork
3. **Enterprise**: Contact Anthropic sales
---
## Sources
All information in this document is derived from:
| Source | Type | Link |
|--------|------|------|
| **Anthropic Blog** | Official | [claude.com/blog/cowork-research-preview](https://claude.com/blog/cowork-research-preview) |
| **YouTube Demo - File Org** | Community | Search "Claude Cowork file organization" |
| **LinkedIn Demos** | Community | Various posts tagged #ClaudeCowork |
| **Reddit r/ClaudeAI** | Community | Cowork megathread |
### Documentation Gaps
As of January 2026, the following official documentation is **missing**:
- Security guidelines
- Best practices guide
- API/automation documentation
- Known issues list
- Release notes / changelog
- Enterprise deployment guide
This guide will be updated as official documentation becomes available.
---
*Back to [AI Ecosystem Guide](./ai-ecosystem.md) | [Ultimate Guide](./ultimate-guide.md) | [Main README](../README.md)*

View file

@ -10,7 +10,7 @@
**Last updated**: January 2026
**Version**: 3.9.1
**Version**: 3.9.4
---
@ -174,6 +174,7 @@ Context full → /compact or /clear
- [11.2 Tool Matrix](#112-tool-matrix)
- [11.3 Practical Workflows](#113-practical-workflows)
- [11.4 Integration Patterns](#114-integration-patterns)
- [For Non-Developers: Claude Cowork](#for-non-developers-claude-cowork)
- [Appendix: Templates Collection](#appendix-templates-collection)
- [Appendix A: File Locations Reference](#appendix-a-file-locations-reference)
@ -9219,6 +9220,111 @@ Add the logout button only. Don't add session management or remember-me features
---
## 9.16 Session Teleportation
**Reading time**: 5 minutes
**Skill level**: Week 2+
**Status**: Research Preview (as of January 2026)
Session teleportation allows migrating coding sessions between cloud (claude.ai/code) and local (CLI) environments. This enables workflows where you start work on mobile/web and continue locally with full filesystem access.
### Evolution Timeline
| Version | Feature |
|---------|---------|
| **2.0.24** | Initial Web → CLI teleport capability |
| **2.0.41** | Teleporting auto-sets upstream branch |
| **2.0.45** | `&` prefix for background tasks to web |
| **2.1.0** | `/teleport` and `/remote-env` commands |
### Commands Reference
| Command | Usage |
|---------|-------|
| `%` or `&` prefix | Send task to cloud (e.g., `% Fix the auth bug`) |
| `claude --teleport` | Interactive picker for available sessions |
| `claude --teleport <id>` | Teleport specific session by ID |
| `/teleport` | In-REPL command to teleport current session |
| `/tasks` | Monitor background tasks status |
| `/remote-env` | Configure cloud environment settings |
| `Ctrl+B` | Background all running tasks (unified in 2.1.0) |
### Prerequisites
**Required for teleportation:**
- GitHub account connected + Claude GitHub App installed
- Clean git state (0 uncommitted changes)
- Same repository (not a fork)
- Branch exists on remote
- Same Claude.ai account on both environments
- CLI version 2.1.0+
### Workflow Example
```bash
# 1. Start task on web (claude.ai/code)
# "Refactor the authentication middleware"
# 2. Session works in cloud sandbox
# 3. Later, on local machine:
claude --teleport
# → Interactive picker shows available sessions
# 4. Select session, Claude syncs:
# - Conversation context
# - File changes (via git)
# - Task state
# 5. Continue work locally with full filesystem access
```
### Environment Support
| Environment | Teleport Support |
|-------------|------------------|
| CLI/Terminal | Full bidirectional |
| VS Code | Via terminal (not Chat view) |
| Cursor | Via terminal |
| Web (claude.ai/code) | Outbound only (web → local) |
| iOS app | Monitoring only |
### Current Limitations (Research Preview)
> **⚠️ Important**: Session teleportation is in research preview. Expect rough edges.
- **Unidirectional**: Web → local only (cannot teleport local → web)
- **GitHub only**: No GitLab or Bitbucket support yet
- **Subscription required**: Pro, Max, Team Premium, or Enterprise Premium
- **Rate limits**: Parallel sessions consume proportional rate limits
- **Git dependency**: Requires clean git state for sync
### Troubleshooting
| Issue | Solution |
|-------|----------|
| "Uncommitted changes" | Commit or stash changes before teleporting |
| "Branch not found" | Push local branch to remote first |
| "Session not found" | Verify same Claude.ai account on both |
| "Teleport failed" | Check internet connectivity, try again |
| Connection timeout | Use `claude --teleport <id>` with explicit ID |
### Best Practices
1. **Commit frequently** — Clean git state is required
2. **Use meaningful branch names** — Helps identify sessions
3. **Check `/tasks`** — Verify background task status before teleporting
4. **Same account** — Ensure CLI and web use same Claude.ai login
5. **Push branches** — Remote must have the branch for sync
### Environment Variables
| Variable | Purpose |
|----------|---------|
| `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` | Disable background task functionality (v2.1.4+) |
---
## 🎯 Section 9 Recap: Pattern Mastery Checklist
Before moving to Section 10 (Reference), verify you understand:
@ -9245,6 +9351,10 @@ Before moving to Section 10 (Reference), verify you understand:
- [ ] **Named Prompting Patterns**: As If, Constraint, Explain First, Rubber Duck, Incremental, Boundary
- [ ] **Mermaid Diagrams**: Generate visual documentation for architecture and flows
**Advanced Workflows**:
- [ ] **Session Teleportation**: Migrate sessions between cloud and local environments
- [ ] **Background Tasks**: Run tasks in cloud while working locally (`%` prefix)
### What's Next?
**Section 10 is your command reference** — bookmark it for quick lookups during daily work.
@ -10403,6 +10513,22 @@ claude
> **📖 Deep Dive**: For detailed integration patterns, ready-to-use prompts, and tool comparisons, see the [complete AI Ecosystem guide](./ai-ecosystem.md).
### For Non-Developers: Claude Cowork
If you work with non-technical team members, **Cowork** brings Claude's agentic capabilities to knowledge workers without requiring terminal access.
| Aspect | Claude Code | Cowork |
|--------|-------------|--------|
| Target | Developers | Knowledge workers |
| Interface | Terminal | Desktop app |
| Execute code | Yes | No (files only) |
| Outputs | Code, scripts | Excel, PPT, docs |
| Status | Production | Research preview |
**Collaboration pattern**: Developers use Claude Code for specs → PMs use Cowork for stakeholder summaries. Shared context via `~/Shared/CLAUDE.md`.
> **Availability**: Max subscribers only (~$200/mo), macOS only (Jan 2026).
> See [AI Ecosystem Section 9](./ai-ecosystem.md#9-claude-cowork-research-preview) for details.
## Further Reading
@ -10816,4 +10942,4 @@ Thumbs.db
**Contributions**: Issues and PRs welcome.
**Last updated**: January 2026 | **Version**: 3.9.1
**Last updated**: January 2026 | **Version**: 3.9.4

View file

@ -3,7 +3,7 @@
# Source: guide/ultimate-guide.md
# Purpose: Condensed index for LLMs to quickly answer user questions about Claude Code
version: "3.9.1"
version: "3.9.4"
updated: "2026-01"
# ════════════════════════════════════════════════════════════════
@ -91,18 +91,28 @@ deep_dive:
git_best_practices: 8190
subscription_limits: 1750
cost_optimization: 8047
commands_table: 9267
shortcuts_table: 9300
troubleshooting: 9426
cheatsheet: 9801
daily_workflow: 9877
# AI Ecosystem (Section 11, ~line 10156)
ai_ecosystem: 10156
ai_ecosystem_complementarity: 10170
ai_ecosystem_tool_matrix: 10196
ai_ecosystem_workflows: 10221
ai_ecosystem_integration: 10347
session_teleportation: 9223
commands_table: 9399
shortcuts_table: 9432
troubleshooting: 9558
cheatsheet: 9933
daily_workflow: 10009
# AI Ecosystem (Section 11, ~line 10271)
ai_ecosystem: 10271
ai_ecosystem_complementarity: 10285
ai_ecosystem_tool_matrix: 10311
ai_ecosystem_workflows: 10336
ai_ecosystem_integration: 10462
ai_ecosystem_detailed: "guide/ai-ecosystem.md"
ai_ecosystem_alternative_providers: "guide/ai-ecosystem.md:902"
# Cowork documentation
cowork_full: "guide/cowork.md"
cowork_section: "guide/ai-ecosystem.md:701"
cowork_comparison: "guide/cowork.md:115"
cowork_use_cases: "guide/cowork.md:140"
cowork_security: "guide/cowork.md:200"
cowork_workflows: "guide/cowork.md:270"
cowork_ultimate_guide: 10521
# ════════════════════════════════════════════════════════════════
# DECISION TREE (most important - en premier)
@ -156,6 +166,9 @@ commands:
/model: "switch: sonnet|opus|opusplan"
/mcp: "show MCP server status"
/context: "detailed token breakdown"
/teleport: "bring web session to local CLI"
/tasks: "monitor background tasks"
/remote-env: "configure cloud environment"
# ════════════════════════════════════════════════════════════════
# SHORTCUTS - see deep_dive.shortcuts_table
@ -165,6 +178,7 @@ shortcuts:
Esc×2: "rewind/undo"
Ctrl+C: "interrupt"
Ctrl+R: "retry"
Ctrl+B: "background all tasks"
"@file": "reference file"
"!cmd": "shell command"
@ -174,6 +188,7 @@ shortcuts:
cli:
"-c": "continue last session"
"-r <id>": "resume specific session"
"--teleport": "bring web session to local CLI"
"-p": "non-interactive (pipe mode)"
"--model X": "select model"
"--dangerously-skip-permissions": "auto-accept ALL (danger)"
@ -345,7 +360,7 @@ rules:
ecosystem:
this_guide:
focus: "Education - Learn & master"
unique: ["architecture docs", "TDD/SDD methodologies", "217-question quiz", "YAML index"]
unique: ["architecture docs", "TDD/SDD methodologies", "227-question quiz", "YAML index"]
complementary:
claude_code_templates:
url: "github.com/davila7/claude-code-templates"
@ -358,6 +373,11 @@ ecosystem:
url: "github.com/wesammustafa/Claude-Code-Everything"
focus: "Visual walkthrough - Screenshots, BMAD method"
install_templates: "scripts/install-templates.sh"
cowork:
description: "Claude Code for non-developers (desktop app)"
status: "Research preview - Max/macOS only (Jan 2026)"
blog: "https://claude.com/blog/cowork-research-preview"
guide: "guide/cowork.md"
# ════════════════════════════════════════════════════════════════
# ONBOARDING MATRIX - Maps user profile → content sections