Scheduled Tasks
Type /schedule or click Scheduled in the sidebar. Set tasks to run daily, weekly, or on any cadence. App must stay open — dedicate an old machine as your always-on Cowork station.
Daily Briefing
Schedule for 6 AM every weekday: check urgent Slack DMs, scan Gmail, review today's calendar, output a briefing with urgent items, prep notes, conflicts, and top 3 priorities. Ready by 8 AM.
Workspace Map
Create a workspace-map.md with your full folder structure and instructions for how Claude should navigate it. Pattern: skill file + new posts + successful posts per platform.
CONTEXT.md Everywhere
Drop a CONTEXT.md in every Project with core business context — who you are, clients, tone, non-negotiables. Two minutes of setup, permanent payoff. Claude never has to ask who you are.
Permission Controls
Set each tool to Allow (auto), Ask (confirms first), or Block (never). Best default: let Claude read everything automatically, confirm before posting or sending.
Mobile Workaround
Push your workspace to a private GitHub repo. Open Claude Code on mobile and pull that repo for context — or use Dispatch to remotely access files on your desktop machine. Sync back to desktop for heavy execution.
Multi-Machine Sync
Projects don't cloud-sync yet. Workaround: keep your working folder in Dropbox, Google Drive, or iCloud. Files travel; task history doesn't — but that's most of the value.
Scaling to a Team
On Team or Enterprise, skills and plugins are shared across seats automatically. For full project sharing — context files, instructions, examples — keep the workspace folder in a private GitHub repo and have teammates clone it.
Safety Defaults
Add to Global Instructions: never delete files without confirmation, never modify files outside output folder, show plan before executing, ask rather than assume. Back up before your first real task.
Usage Strategy
Use Haiku or Sonnet as your daily driver for routine tasks — fast, cheap, good enough. Switch to Opus only when you need deep reasoning or complex multi-step work. Save tokens for where they compound.
New Chats > Long Threads
Inside a Project, start a new chat for each task. You get shared memory across all chats, but each session stays lean. One long chat = bloated context, messy history, harder for Claude to know what "done" looks like. Short chats, clear scope, shared memory.
Level Up to Claude Code
Once you've mastered Cowork, Claude Code runs in the terminal and can build entire projects. Same philosophy, more power. Install: curl -fsSL https://claude.ai/install.sh | bash