deanlu.ai

Introduction to Claude Cowork

8 min read

Source Snapshot

Garden Card

This note is a Quartz-ready onboarding map for Claude Cowork, focused on delegation, projects, connectors, skills, plugins, browser use, and review discipline.

这篇笔记是一张面向 Claude Cowork 的 Quartz 入门地图，重点是委托、项目、连接器、技能、插件、浏览器使用和复核纪律。

  • Core question: What changes when Claude moves from chat partner to coworker? 核心问题：当 Claude 从聊天伙伴变成协作同事时，工作方式有什么变化？

  • Operational value: It explains how to hand over real deliverables while keeping scope and approval clear. 运营价值：它说明如何把真实交付物交给 Claude，同时保持范围和审批清晰。

  • Best connection: How to Use Claude Cowork Effectively, Agent SDK Core Concepts, SDK Demo Learning Map 最适合连接的内容：Cowork 使用方法、SDK 核心概念和 Demo 学习路线。

1. Executive Summary

Claude Cowork shifts the mental model from question-and-answer chat to delegated work. The user describes an outcome, names the inputs, and lets Claude plan and execute the work arc across local files, connectors, browser context, and tools.

Claude Cowork 把使用心智从问答聊天转向委托工作。用户描述目标、指定输入，让 Claude 跨本地文件、连接器、浏览器上下文和工具规划并执行完整工作。

The course emphasizes smallest useful folders, connector setup, permission modes, projects, skills, plugins, Claude in Chrome, scheduled tasks, and human review of final artifacts.

课程强调最小可用文件夹、连接器设置、权限模式、项目、技能、插件、Claude in Chrome、定时任务和最终交付物复核。

  • Main idea: Delegation beats step-by-step prompting for real work. 主要观点：真实工作中，委托比逐步提示更有效。

  • Why now: AI assistants are moving into files, apps, browsers, and recurring workflows. 为什么现在重要：AI 助手正在进入文件、应用、浏览器和周期性工作流。

  • Where it applies: Reports, proposals, meeting follow-ups, data synthesis, and cross-app research. 可以应用的场景：报告、方案、会议跟进、数据综合和跨应用研究。

Decision Signal

Give Claude a complete work package: deliverable, inputs, nuance, scope, and review boundary.

2. Key Technical Terms

Use these terms to describe Claude Cowork’s working model.

这些术语可以描述 Claude Cowork 的工作模式。

  • Cowork / 协作工作模式: A delegated working session where Claude plans and executes toward a deliverable.

    Claude 围绕交付物进行规划和执行的委托式工作会话。

  • Project / 项目: Scoped workspace with instructions, context, scheduled tasks, and accumulated memory.

    包含指令、上下文、定时任务和累积记忆的限定工作区。

  • Connector / 连接器: Integration that lets Claude search or use external apps such as email, calendar, Slack, Drive, or CRM.

    让 Claude 搜索或使用邮件、日历、Slack、Drive、CRM 等外部应用的集成。

  • Skill / 技能: Reusable playbook for a recurring process.

    面向重复流程的可复用操作手册。

  • Plugin / 插件: Packaged set of skills, connectors, and subagents around a role or process.

    围绕角色或流程打包的技能、连接器和子智能体集合。

3. Core Notes

3.1 Problem

Many users treat Cowork like Chat and feed it one small question at a time. That underuses its ability to plan across files, apps, and tools.

很多用户把 Cowork 当成 Chat，一次只问一个小问题。这没有充分利用它跨文件、应用和工具规划工作的能力。

  • Unclear deliverables produce vague outputs. 交付物不清会产生模糊输出。

  • Oversized folders create noise and risk. 过大的文件夹会带来噪声和风险。

  • Missing context leads to avoidable clarifying loops. 缺少上下文会导致本可避免的澄清循环。

3.2 Mechanism

A strong Cowork prompt names the deliverable, inputs, date range or folder, relevant nuance, and review expectations.

强 Cowork 提示会说明交付物、输入、日期范围或文件夹、相关细节和复核期望。

  • Use the smallest folder that contains the work. 使用包含任务所需内容的最小文件夹。

  • Connect only the apps relevant to the task. 只连接与任务相关的应用。

  • Interrupt early if the plan goes wrong. 如果计划方向错误，尽早打断。

3.3 Evidence

The course organizes Cowork around modules for setup, first tasks, global instructions, projects, skills, plugins, Chrome, scheduling, and dispatch.

课程围绕设置、首次任务、全局指令、项目、技能、插件、Chrome、定时任务和 dispatch 组织 Cowork 学习路径。

  • Projects carry standing context for a stream of work. 项目为一条工作流保留长期上下文。

  • Skills teach Claude a repeatable process. 技能教 Claude 执行可重复流程。

  • Claude in Chrome bridges tools without dedicated connectors. Claude in Chrome 连接没有专用连接器的工具。

3.4 Boundary

Cowork still requires human review. The file may be finished, but facts, business judgment, permanent actions, and sensitive outputs need inspection.

Cowork 仍需要人工复核。文件可能已经完成，但事实、业务判断、永久性操作和敏感输出需要检查。

  • Default to asking before unfamiliar actions. 不熟悉的操作默认先询问。

  • Review final artifacts like a colleague’s draft. 像审阅同事草稿一样审阅最终交付物。

  • Scheduled tasks only work when the required desktop environment is available. 定时任务需要所需桌面环境可用才会运行。

4. Concept Map

Use wikilinks to connect this note into the broader Quartz graph.

使用双向链接把这篇笔记接入更大的 Quartz 知识网络。

flowchart LR
  A["Outcome"] --> B["Inputs"]
  B --> C["Nuance"]
  C --> D["Cowork Plan"]
  D --> E["Tool Execution"]
  E --> F["Artifact"]
  F --> G["Human Review"]
  G --> H["Skill or Project Memory"]

Diagram labels stay in English for rendering consistency and easier reuse across published pages.

图中的标签保持英文，便于 Quartz 渲染后跨页面复用，也方便技术读者快速识别。

5. My Take

Cowork is most useful when the human manages delegation quality. The better the outcome, inputs, and review boundary are defined, the less the user has to stitch work together manually.

Cowork 的价值取决于人如何管理委托质量。目标、输入和复核边界越清楚，用户越不需要手工拼接流程。

  • What changed my thinking: Cowork works best with whole work packages, not isolated prompts. 改变我理解的地方：Cowork 最适合完整工作包，而不是孤立提示。

  • What I may do next: Turn recurring deliverables into projects and skills. 下一步可能行动：把周期性交付物做成项目和技能。

  • What still needs verification: Current plan requirements, connector availability, and permission behavior. 仍需要验证的内容：当前套餐要求、连接器可用性和权限行为。

Reuse Path

Convert this note into a first-task prompt checklist for Cowork onboarding.

References

Graph View

Backlinks