Troubleshooting & Next Steps

Phần 1: 8 common issues

🔄 Issue 1: "Cowork đang preparing your workspace..." — chờ lâu

Triệu chứng:

Nguyên nhân: Cowork getting its environment ready before starting. Bao gồm:

Khi nào thường xảy ra:

Cách xử lý: Đợi. Đây là expected, thường 10-60 giây. Không kill app — khởi động lại còn lâu hơn.

Nếu >3 phút vẫn stuck:

⏸ Issue 2: Task stopped mid-run

Triệu chứng:

Task chạy được 30%, panel shows "Task paused" hoặc stops updating.

Nguyên nhân phổ biến:

Key distinction:

• Initialize isolated execution environment
• Load installed plugins & skills
• Warm up connectors
• First time mở Cowork sau install
• After update (plugin/app update)
• After long idle period (computer sleep >24h)
• Check network connection
• Restart Claude Desktop
• If persistent: reinstall app

⏳ Cowork is preparing your workspace...
(hiển thị 30+ giây)

⏸ Issue 2: Task stopped mid-run

Cách xử lý:

📊 Issue 3: Running into usage limits

Triệu chứng:

• Check Claude Desktop is open
• Check network connectivity
• If open + connected: click "Resume" trong task panel
• Nếu task doesn't resume after 5 min: "Run again" với same prompt

🛌 Sleep computer     → Session SURVIVES, picks back up
❌ Quit app           → Session PAUSES, resumes on reopen

📊 Issue 3: Running into usage limits

Nguyên nhân:

Cowork uses more allocation than chat. Long-running tasks với Opus use most.

Cách xử lý (immediate):

Cách xử lý (preventive — recall từ Bài 3.8):

Longer-term: Upgrade plan nếu usage consistently hits ceiling.

🤔 Issue 4: Can't find file Cowork said it made

Triệu chứng:

Cowork ends task with "File saved to report.docx" — but you can't find it.

Common causes:

Cách xử lý:

• Switch to chat cho remaining urgent work nếu fit
• Downgrade tới Sonnet/Haiku cho pending Cowork tasks
• Pause scheduled tasks temporarily
• Batch related work — 1 session thay vì many
• Use chat cho tasks that fit — save Cowork cho complex
• Match model to task — don't default Opus
• Monitor usage weekly — catch trend early

⚠️ You've reached your weekly allocation limit.
    Resets: Friday 23:59 UTC

🤔 Issue 4: Can't find file Cowork said it made

Claude will answer specifically.

Alternatively:

Prompt: "Where did you save the output file? Give me 
         exact absolute path."

Phần 1: 8 common issues (tiếp)

Preventive: Always end prompts với "Save to [absolute path]".

🔌 Issue 5: Connector not working

Triệu chứng: Cowork says "I don't have access to Gmail" dù bạn đã connect.

Common causes:

Cách xử lý:

💬 Issue 6: Output không match expectation

Triệu chứng: Task xong nhưng kết quả khác expected — wrong format, wrong focus, wrong length.

Diagnostic questions:

Cách xử lý:

Method A: Refine prompt, re-run

• Customize → Connectors → [Tool] → "Disconnect"
• Re-connect → follow OAuth flow carefully
• Verify in new prompt: "Check my calendar for tomorrow" (cho Calendar connector)

┌──────────────────────────────────────────────────┐
│                                                  │
│   1. Prompt có specific không?                   │
│      - Input → Transformation → Output clear?    │
│                                                  │
│   2. Context (CLAUDE.md / Global) có up to date? │
│      - Rules aligned với task?                   │
│                                                  │
│   3. Skill/plugin trigger đúng không?            │
│      - Intended skill matched description?       │
│                                                  │
│   4. Clarifying questions bạn trả lời sao?       │
│      - Chose default wrong?                      │
│                                                  │
└──────────────────────────────────────────────────┘

# macOS/Linux
find ~/Documents -name "*report*" -mtime -1

# Windows PowerShell
Get-ChildItem -Path "C:\" -Include "*report*" -Recurse -Force

💬 Issue 6: Output không match expectation

Method B: Reset + better prompt

Method C: Update context

🐢 Issue 7: Task taking way longer than expected

Triệu chứng: Simple-looking task running 20+ phút.

Common causes:

Cách xử lý:

🔒 Issue 8: Permission prompt fatigue / approvals pile up

Triệu chứng: Too many approval prompts → click yes blindly.

Why it's risky: Approval fatigue defeats safety gates.

Cách xử lý:

For specific workflows bạn trust:

For sensitive areas:

Consolidate prompts:

Better than 10 staggered prompts.

• Start new session với tighter prompt
• Include example of desired output ("Format like past-report.docx")
• If repeat issue: update CLAUDE.md với relevant rule
• Test với next task
• Complex task underneath: What looks simple has many steps
• Too many files: Folder có 500 files all read
• Subagents spawn unintended: Task auto-parallelized when not needed
• Network slow: Each connector call slow
• Model overkill: Opus slower than Sonnet
• Interrupt — gõ "Stop, too slow. Give progress summary."
• Diagnose — Claude explains which step taking time
• Adjust:
• Narrow folder scope
• Switch to smaller model
• Disable unused connectors
• Break into smaller tasks
• In CLAUDE.md: "For /weekly-report task, auto-execute without asking."
• Trust is earned via stability
• Keep approvals required
• Especially for: delete, send email, external API calls
• "Plan all approvals needed upfront, show list, get batch approval."

"Revise output: focus on [specific aspect], format as 
[specific format], length [specific]."

Decision tree — Diagnose any issue

Cowork acting strange?
        │
        ▼
   ┌─────────────┐
   │ App open &  │  No  ┌──────────────┐
   │ connected?  ├─────▶│ Open app /   │
   │             │      │ check network│
   └──────┬──────┘      └──────────────┘
          │Yes
          ▼
   ┌─────────────┐
   │  Task       │  Stuck ┌────────────────┐
   │  progress?  ├───────▶│ Interrupt,     │
   │             │        │ ask Claude     │
   └──────┬──────┘        │ what happening │
          │Moving         └────────────────┘
          ▼
   ┌─────────────┐
   │  Output     │  Bad  ┌──────────────────┐
   │  quality?   ├──────▶│ Refine prompt,   │
   │             │       │ check context    │
   └──────┬──────┘       └──────────────────┘
          │Good
          ▼
   ┌─────────────┐
   │  Can find   │  No   ┌──────────────┐
   │  output     ├──────▶│ Ask Claude    │
   │  file?      │       │ for path      │
   └──────┬──────┘       └──────────────┘
          │Yes
          ▼
   ┌─────────────┐
   │  Review     │  Fail ┌──────────────┐
   │  quality    ├──────▶│ Note patterns,│
   │  OK?        │       │ improve prompt│
   └──────┬──────┘       │ next time     │
          │Pass          └──────────────┘
          ▼
     Task done ✓

Phần 2: What to do next — 5-step sequence

Cowork value unlocks progressively. Don't stay at "first task" level. Here's the sequence:

Take these at whatever pace fits your work. The sequence matters more than the timing.

Step 1: Install a plugin

Action: Browse plugin library, pick one matching your role, install.

Why first: Plugin gives you ready-made skills — don't start from zero.

Depth: Open plugin folder. Read ONE of the skill files. See that it's readable text, written the way you'd brief a teammate.

Time: 15 phút (install + explore + run 1 skill).

Step 2: Run something real

Action: Pick a task từ actual work — something that matters, even if small.

What you're looking for: That moment — bạn come back from doing something else, and finished file is there.

Why this matters: Abstract understanding ≠ lived experience. First real task shifts mindset.

Examples:

Time: 30 min to 2 hours (first task includes learning).

Step 3: Make a skill

Action: Build your first custom skill.

Two paths:

Path A — Build brand-guidelines skill:

If you produce branded output (decks, reports, emails):

Every future creation references this skill. Consistency automatic.

Path B — Next time pattern:

Next time you run a task and realize "I'll run this again":

Why step 3: Moves from "using Cowork" to "building FOR Cowork". Personal leverage.

Time: 30-60 min initial, iterative refinement over weeks.

Step 4: Schedule it

Action: Put skill onto schedule.

Criteria for scheduling:

Process (recall Bài 3.5):

If app closed when task due: Runs as soon as app reopens.

Why step 4: Unlocks "runs without you" value. Work happens in background.

Time: 5 min to set up, pays forever.

Step 5: Share it

Action: Package skill cho teammate, or make available broadly.

Personal level:

Team/Enterprise level:

Why step 5: Leverage compounds. 1 skill × 10 teammates × 52 weeks = massive aggregate value.

Time: 15 min to package + share. Enterprise distribution varies.

• Weekly report currently taking 2 hours
• Folder sort tách đi ngày thứ Hai mỗi tuần
• Research synthesis đang putting off
• Save session as skill
• Or ask Cowork: "Create a skill from this session."
• Skill has run successfully manual ≥ 3 times
• Output consistent quality
• Has natural cadence (daily brief, weekly report, monthly close)
• Test skill manual 3 times
• /schedule
• Natural language cadence
• Approve
• Export skill folder
• Email/slack to teammate
• They install → same workflow
• Talk to your admin
• Enterprise plans có admin distribution
• Skills become "company standard"

┌──────────────────────────────────────────────────────┐
│                                                      │
│   🎯 GOAL: Have a skill you trust running            │
│            on a schedule                             │
│                                                      │
│   1. Install plugin                                  │
│        ↓                                             │
│   2. Run something real                              │
│        ↓                                             │
│   3. Make a skill                                    │
│        ↓                                             │
│   4. Schedule it                                     │
│        ↓                                             │
│   5. Share it                                        │
│                                                      │
└──────────────────────────────────────────────────────┘

Build skill: brand-guidelines
- My brand colors: #... (hex)
- My fonts: [font name]
- Tone: [description]
- Logo placement: [rules]
- Reference file: /brand-assets/logo-v2.png

Apply this skill when creating any deck, report, email draft.

Self-assessment: Are you ready?

Before leaving course, assess:

Must-haves (foundations)

Should-haves (intermediate)

Nice-to-haves (advanced)

Scoring

• [ ] Claude Desktop installed, paid plan active
• [ ] At least 1 folder designated as Cowork working folder
• [ ] At least 3 connectors setup
• [ ] Global Instructions có 5 sections
• [ ] At least 1 Project CLAUDE.md created
• [ ] Ran at least 1 real task successfully
• [ ] Know cách switch between Opus/Sonnet/Haiku
• [ ] Know where usage dashboard is
• [ ] Installed 1 plugin matching your role
• [ ] Explored plugin folder, read 1 SKILL.md
• [ ] Built or customized 1 skill
• [ ] Know difference between CLAUDE.md vs skill vs slash command
• [ ] Successfully used Cowork cho file/document task
• [ ] Ran research/analysis task with signal-seeking prompt
• [ ] Scheduled task running successfully for >1 week
• [ ] Built personal skill from scratch
• [ ] Shared skill with teammate
• [ ] Have confidence reviewing Cowork outputs critically
• [ ] Integrated Cowork into weekly workflow habits
• All must-haves + 3+ should-haves: Ready to scale. Pick your "first real task" from Step 2 above.
• Missing must-haves: Revisit relevant bài (CLAUDE.md → 3.4, connectors → 3.2, skills → 3.5).
• Only 1-2 must-haves: Start from Bài 3.1 setup again. Practice hands-on before moving forward.

Lesson reflection questions

Answer these honestly to consolidate learning:

Question 1: First real task

What's the first real task you'll hand to Cowork?

Be specific:

Question 2: Role-plugin match

Which plugin matches what you do? Is it installed?

Question 3: Schedule candidate

What workflow — one bạn already run manually — would save you the most time if it ran on a schedule?

• Task: ___________________
• Current time manual: ____ minutes/hours
• Expected Cowork time: ____ (including review)
• Deadline by when you'll run it: ___________________
• Plugin candidate: ___________________
• Installed? ☐ Yes ☐ No
• If no: blocker? ___________________
• Workflow: ___________________
• Current cadence manual: ___________________
• Time consumed per run: ____ minutes
• Weekly impact if automated: ____ minutes saved

Where to go from here

Official resources

Setup & troubleshooting:

Task inspiration:

Plugin ecosystem:

Building habits:

Community

For builders

If bạn want build plugins / skills beyond consuming:

For admins

If bạn manage Cowork cho team/org:

• Getting started with Cowork — Help Center deep reference
• Cowork for Team/Enterprise admins
• Cowork use-case gallery — 50+ concrete task ideas across industries
• Knowledge-work plugins on GitHub — Official + community
• Financial-services plugins — Specialized
• AI Fluency course — 4D framework: Delegation, Description, Discernment, Diligence
• Introduction to Agent Skills course — Deep dive on skills
• Cowork community forum — ask questions, share patterns
• Skill marketplace — discover skills khác đã build
• GitHub discussions — technical deep-dives
• Build a plugin from scratch
• Skill authoring guide
• Claude Code documentation — parallel tool for dev workflows
• Enterprise deployment
• Admin console
• Audit & compliance

Common paths after this course

Path 1: "Productivity power user"

Profile: Individual contributor. Goal: personal leverage.

Next steps:

Timeline: First win < 1 week. Steady state ~1 month.

Measure success: Time saved/week. Target: 5-10 hours.

Path 2: "Team champion"

Profile: Lead/manager. Goal: team adoption.

Next steps:

Timeline: Personal in month 1. Team onboarded month 2-3.

Measure success: Team hours saved collectively. Adoption rate.

Path 3: "Workflow architect"

Profile: Technical operator. Goal: design systems.

Next steps:

Timeline: 3-6 months to ship org-level systems.

Measure success: Systems deployed × people impacted.

Path 4: "AI skeptic turned believer"

Profile: Started skeptical. Now cautiously exploring.

Next steps:

Timeline: Trust builds over 3-6 months of regular use.

Measure success: Personal confidence, reasoned trust.

• Install role plugin
• Customize CLAUDE.md for active project
• Schedule 2-3 daily/weekly tasks
• Build 1-2 personal skills
• Personal path first (own it)
• Identify 2-3 team workflows to standardize
• Build team skills (shared patterns)
• Onboard teammates 1-at-a-time
• Share wins publicly
• Personal path
• Deep dive on plugin building
• Design integrated workflows (skill + schedule + connector)
• Build for org-level impact
• Consider: custom MCPs, integration với internal systems
• Pick LOW-stakes task first
• Observe carefully
• Review outputs rigorously
• Only expand scope once trust built
• Document your own "moments of doubt + resolution"

Celebration: You've completed the training

You now know how to:

Now pick something real and hand it over.

The gap between knowing và doing là where real learning happens. Every teammate we've seen master Cowork had their "aha moment" on a real task, not a tutorial.

Pick yours. Run it. Come back và refine.

• ✅ Describe a task
• ✅ Review a plan
• ✅ Let work run
• ✅ Review the output
• ✅ Know where Cowork fits alongside chat
• ✅ Teach it once so you don't explain it again

Tóm tắt bài học

🎯 8 common issues có decision tree rõ ràng — symptom → likely cause → specific fix

🎯 Next steps sequence: Install → Run real → Make skill → Schedule → Share — progressive leverage unlock

🎯 "First real task" là kickstart — abstract knowledge chưa thành skill until applied

🎯 Self-assessment checklist để verify readiness — must-haves / should-haves / nice-to-haves

🎯 4 paths forward tùy goal: Power user / Team champion / Workflow architect / Skeptic-turned-believer

🎯 Resources available beyond course — Help Center, AI Fluency, plugin ecosystem, community

Feedback

Course này sẽ improve liên tục với feedback của bạn. Share:

Email: [cowork-feedback@anthropic.com]

Bản quyền 2026 Anthropic. Mọi quyền được bảo lưu.

• Phần nào clear nhất?
• Phần nào cần more examples?
• Use case nào bạn wish có?
• Common issue nào chưa được covered?