3.9 · Troubleshooting & Next Steps

Mở đầu: Bạn gần đến đích

• Hiểu Cowork là gì và khi nào dùng
• Setup Claude Desktop + connectors
• Chạy task loop với prompts I-T-O
• Configure 3 tầng context (Global / Project / Files)
• Install plugins và work với skills
• Set up scheduled tasks
• Master file/document + research workflows
• Quản lý permissions, allocation, model choice

Còn lại trong bài này: fix những thứ có thể sai + roadmap để Cowork thực sự biến đổi workflow của bạn.

Phần 1: 8 common issues

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

Triệu chứng:

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

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

• Initialize isolated execution environment
• Load installed plugins & skills
• Warm up connectors

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

• First time mở Cowork sau install
• After update (plugin/app update)
• After long idle period (computer sleep >24h)

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:

1. Check network connection
2. Restart Claude Desktop
3. If persistent: reinstall app

⏸ 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:

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

Cách xử lý:

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

Issue 3: Running into usage limits

Triệu chứng:

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

Nguyên nhân:

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

Cách xử lý (immediate):

• Switch to chat cho remaining urgent work nếu fit
• Downgrade tới Sonnet/Haiku cho pending Cowork tasks
• Pause scheduled tasks temporarily

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

1. Batch related work1 session thay vì many
2. Use chat cho tasks that fitsave Cowork cho complex
3. Match model to taskdon't default Opus
4. Monitor usage weeklycatch trend early

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ý:

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

Claude will answer specifically.

Alternatively:

find ~/Documents -name "*report*" -mtime -1

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

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ý:

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

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:

┌──────────────────────────────────────────────────┐
│                                                  │
│   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?                      │
│                                                  │
└──────────────────────────────────────────────────┘

Cách xử lý:

Method A: Refine prompt, re-run

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

Method B: Reset + better prompt

• Start new session với tighter prompt
• Include example of desired output ("Format like past-report.docx")

Method C: Update context

• If repeat issue: update CLAUDE.md với relevant rule
• Test với next task

Issue 7: Task taking way longer than expected

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

Common causes:

• 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

Cách xử lý:

1. Interruptgõ "Stop, too slow. Give progress summary."
2. DiagnoseClaude explains which step taking time
3. Adjust:Narrow folder scope — Switch to smaller model — Disable unused connectors — Break into smaller tasks

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:

• In CLAUDE.md: "For /weekly-report task, auto-execute without asking."
• Trust is earned via stability

For sensitive areas:

• Keep approvals required
• Especially for: delete, send email, external API calls

Consolidate prompts:

• "Plan all approvals needed upfront, show list, get batch approval."

Better than 10 staggered prompts.

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:

┌──────────────────────────────────────────────────────┐
│                                                      │
│   🎯 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                                        │
│                                                      │
└──────────────────────────────────────────────────────┘

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:

• Weekly report currently taking 2 hours
• Folder sort tách đi ngày thứ Hai mỗi tuần
• Research synthesis đang putting off

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):

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.

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":

• Save session as skill
• Or ask Cowork: "Create a skill from this session."

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:

• Skill has run successfully manual ≥ 3 times
• Output consistent quality
• Has natural cadence (daily brief, weekly report, monthly close)

Process (recall Bài 3.5):

1. Test skill manual 3 times
2. /schedule
3. Natural language cadence
4. Approve

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:

• Export skill folder
• Email/slack to teammate
• They install → same workflow

Team/Enterprise level:

• Talk to your admin
• Enterprise plans có admin distribution
• Skills become "company standard"

Why step 5

Leverage compounds. 1 skill × 10 teammates × 52 weeks = massive aggregate value.

Time

15 min to package + share. Enterprise distribution varies.

Self-assessment: Are you ready?

Before leaving course, assess:

Must-haves (foundations)

• 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

Should-haves (intermediate)

• 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

Nice-to-haves (advanced)

• 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

Scoring

• 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:

• Task: ___________________
• Current time manual: ____ minutes/hours
• Expected Cowork time: ____ (including review)
• Deadline by when you'll run it: ___________________

Question 2: Role-plugin match

Which plugin matches what you do? Is it installed?

• Plugin candidate: ___________________
• Installed? Yes No
• If no: blocker? ___________________

Question 3: Schedule candidate

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

• Workflow: ___________________
• Current cadence manual: ___________________
• Time consumed per run: ____ minutes
• Weekly impact if automated: ____ minutes saved

Where to go from here

Official resources

Setup & troubleshooting:

• Getting started with Cowork — Help Center deep reference
• Cowork for Team/Enterprise admins

Task inspiration:

• Cowork use-case gallery — 50+ concrete task ideas across industries

Plugin ecosystem:

• Knowledge-work plugins on GitHub — Official + community
• Financial-services plugins — Specialized

Building habits:

• AI Fluency course — 4D framework: Delegation, Description, Discernment, Diligence
• Introduction to Agent Skills course — Deep dive on skills

Community

• Cowork community forum — ask questions, share patterns
• Skill marketplace — discover skills khác đã build
• GitHub discussions — technical deep-dives

For builders

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

• Build a plugin from scratch
• Skill authoring guide
• Claude Code documentation — parallel tool for dev workflows

For admins

If bạn manage Cowork cho team/org:

• Enterprise deployment
• Admin console
• Audit & compliance

Common paths after this course

Path 1: "Productivity power user"

Profile: Individual contributor. Goal: personal leverage.

Next steps:

1. Install role plugin
2. Customize CLAUDE.md for active project
3. Schedule 2-3 daily/weekly tasks
4. Build 1-2 personal skills

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:

1. Personal path first (own it)
2. Identify 2-3 team workflows to standardize
3. Build team skills (shared patterns)
4. Onboard teammates 1-at-a-time
5. Share wins publicly

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:

1. Personal path
2. Deep dive on plugin building
3. Design integrated workflows (skill + schedule + connector)
4. Build for org-level impact
5. Consider: custom MCPs, integration với internal systems

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:

1. Pick LOW-stakes task first
2. Observe carefully
3. Review outputs rigorously
4. Only expand scope once trust built
5. Document your own "moments of doubt + resolution"

Timeline

Trust builds over 3-6 months of regular use.

Measure success

Personal confidence, reasoned trust.

Celebration: You've completed the training

You now know how to:

• 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

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.

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

Tài liệu tham khảo

• Cowork troubleshooting index — Full Help Center Cowork section
• Cowork use-case gallery
• Plugin source + customization
• AI Fluency course

Feedback

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

• 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?

Email: [cowork-feedback@anthropic.com]