Claude Cowork & Claude Code FAQ

Claude Cowork brings Claude Code's agentic abilities to knowledge work without a terminal. You describe an outcome and Claude plans and carries out multi-step work — organising files, researching, building documents, spreadsheets and decks — in an isolated cloud environment, reaching your local files and browser through Claude Desktop. Anthropic is merging Cowork and chat into one experience ("just Claude"), rolling out on Pro and Max. More → Source: Claude Help Center

Paid plans only: Pro, Max, Team and Enterprise (where an admin enables it). Claude Desktop for macOS and Windows has it on all paid plans; web and mobile are in beta on Pro, Max and Team; the Chrome side panel is on Max and Team, rolling out to Pro. More → Source: Claude Help Center

Yes. Pro ($20/month, or $17/month billed annually), Max ($100) and Ultra ($200) include Claude Code in the terminal and in VS Code, Cursor and JetBrains IDEs, with usage shared across Claude, Cowork and Claude Code. If ANTHROPIC_API_KEY is set, Claude Code bills that key instead of your plan. More → Source: Claude Help Center

Cowork always asks for explicit permission before permanently deleting files, and Manual mode asks before other actions too. In Claude Code, deny rules in permissions (for example Bash(rm *)) block commands, plan mode explores without changing anything, and checkpoints let you undo Claude's file edits with /rewind or Esc twice — though checkpoints do not cover changes made by shell commands, so keep work in git. Source: Claude Code docs

Anthropic runs each cloud session in an isolated sandbox that cannot reach your network, screens actions in Auto mode, scans untrusted content for prompt injection and asks before deletions — but isolation does not limit what Claude can read and do through the access you grant. Its guidance: be selective with file access, avoid scheduling tasks that send messages or buy things, keep computer use away from banking and health apps, and use Manual mode for consequential work. More → Source: Claude Help Center

Type /schedule in a Cowork task or open Scheduled in the sidebar (or just describe the schedule in the new Claude experience). Scheduled tasks run remotely, even when your computer is asleep, and use your connectors, skills and plugins; a task that needs local files or apps will only run locally, and when you set one up manually you can optionally pick a folder for it to work in. They are on all paid plans. More → Source: Claude Help Center

A Markdown file of standing instructions Claude Code loads every session. It can live at the managed-policy path, ~/.claude/CLAUDE.md, ./CLAUDE.md or ./.claude/CLAUDE.md, and ./CLAUDE.local.md. Run /init to generate one. Claude Code also reads a project's AGENTS.md. It is context, not enforcement — use hooks or permission rules to guarantee behaviour. More → Source: Claude Code docs

Settings live in ~/.claude/settings.json, .claude/settings.json and .claude/settings.local.json: permissions (allow, ask, deny), env, model, hooks and more, all listed in the official settings reference. Keys such as autoApprove or bash.allowedCommands that circulate online do not exist. More → Source: Claude Code docs

Hooks are commands configured under hooks in settings.json that run on events such as PreToolUse and PostToolUse, with a matcher for which tools they apply to. A PreToolUse hook can return a deny decision to block a call — the reliable way to enforce a rule. More → Source: Claude Code docs

The default suits most work: high on most models, medium on Opus 5.5, Sonnet 5.5 and Haiku 5.5 (Anthropic says Opus 5.5 at medium matches Opus 5 at high), xhigh on Opus 4.7. Use xhigh for harder problems and max only after testing — it can overthink. /effort sets it; ultrathink in a prompt deepens one turn. More → Source: Claude Code docs

Claude Code documents five approaches: subagents inside a session, agent view (claude agents) for background sessions, agent teams (experimental, off by default) with a shared task list, projects at claude.ai/code, and dynamic workflows for dozens to hundreds of agents. Use git worktrees to keep parallel sessions' file changes apart. More → Source: Claude Code docs

Use --bare: minimal mode skips auto-discovery of hooks, skills, custom commands, subagents, plugins, MCP servers, auto memory and CLAUDE.md so scripted calls start faster. For CI, combine claude -p with --permission-mode dontAsk and an exact --allowedTools list. Source: Claude Code docs

In Claude, Customize > Skills and Customize > Plugins (Discover) — Anthropic skills, partner skills from companies such as Notion, Figma and Atlassian, and Anthropic's plugin library, also published on GitHub. Plugins you add sync to Claude Code (v2.1.273+) when you sign in with your Claude account. More → Source: Claude Help Center

Not as a built-in feature. Some developers use git branches and a handoff file as a convention. Claude Code’s own parallel-work tools are subagents, worktrees and dynamic workflows; Kilo Code, a third-party agent, can import both Claude Code and Codex sessions with /resume-claude and /resume-codex. More → Source: Claude Code docs

Anthropic has not documented a mechanism; users attribute it to token-by-token generation. Practical fixes: read the whole reply before acting, ask for the plan first, and use extended thinking or a higher effort level for complex work. More → Source: Claude Help Center

Users report it follows mentions of tiredness or late hours; Anthropic has not documented it. Add a standing rule in Settings > General > Instructions for Claude (or Settings > Cowork > Global instructions) asking it not to comment on your schedule or rest. More → Source: Claude Help Center

On Team and Enterprise plans, an Owner turns on Code Review in Admin settings > Claude Code on claude.ai, installs the Claude GitHub App and picks a review level (Quick, Standard or Deep). Tune what it flags with REVIEW.md and CLAUDE.md in the repository. On any plan, run /code-review in your session to review your branch locally. More → Source: Claude Code docs