chore: sync content to repo (#10490)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
2026-10-26 11:18:29 +01:00
1 parent 06f38b7539
commit e52acc9a80
@@ -1,6 +1,6 @@
 # Channels

-Claude Code channels are MCP server plugins that push messages, alerts, and webhooks into your running Claude Code session, allowing Claude to react to events while you're away from the terminal. Channels enable two-way communication through platforms like Telegram, Discord, and iMessage. You install them as plugins, configure credentials, and pair your account so Claude can receive and respond to messages in real-time. Unlike web sessions that spawn fresh instances, events arrive in your already-open session, making channels ideal for always-on setups where you run Claude in a background process.
+Channels are MCP server plugins that push messages, alerts and webhooks into a Claude Code session that is already running. They support platforms like Telegram, Discord and iMessage, so Claude can react to events while you are away from the terminal. You install a channel as a plugin, set up its credentials and pair your account. Because events arrive in your open session instead of starting a new one, channels fit always-on setups.

 Visit the following resources to learn more:

@@ -1,6 +1,6 @@
 # Headless mode

-Headless mode in Claude Code, enabled by the `-p` (or `--print`) flag, transforms the interactive terminal assistant into a programmable Unix-style utility designed for automation and CI/CD pipelines.
+Headless mode runs Claude Code without the interactive interface by passing the -p (or --print) flag with a prompt. It is part of the Agent SDK and is meant for scripts and CI/CD pipelines. Output can be plain text, json or stream-json, and --json-schema forces the result into a defined structure. Flags like --allowedTools, --permission-mode and --bare control which tools can run and how fast the session starts. For full programmatic control with callbacks and message objects, the Python and TypeScript Agent SDK packages offer the same agent loop.

 Visit the following resources to learn more:

@@ -1,9 +1,8 @@
-# Channels
+# Mobile

-To use Claude Code with mobile apps through channels, you install a pre-built channel plugin for your messaging platform, like Telegram, Discord, or iMessage. The plugin runs locally on your computer and polls the platform's API for new messages. When someone sends you a message on the mobile app, the plugin receives it and forwards it to Claude Code, which can then read and respond. You configure the plugin in your MCP config file, and Claude Code spawns it automatically. The plugin acts as a bridge between the mobile app and Claude Code, so you can chat with Claude through your phone without exposing any URLs to the internet.
+Claude Code on mobile lets you start and follow coding sessions from your phone. Cloud sessions run on Anthropic infrastructure, and Remote Control lets you continue a session running on your own computer from the phone or tablet. This makes it possible to check progress, answer a permission prompt, or send a new task while you are away from your desk.

 Visit the following resources to learn more:

- [@official@Push events into a running session with channels](https://code.claude.com/docs/en/channels)
- [@official@Channels reference](https://code.claude.com/docs/en/channels-reference)
- [@video@Claude Code Channels in 8 Minutes](https://www.youtube.com/watch?v=QZXaAc80OL0)
+- [@official@Claude Code on mobile](https://code.claude.com/docs/en/mobile)
+- [@official@Continue local sessions from any device with Remote Control](https://code.claude.com/docs/en/remote-control)
@@ -1,6 +1,6 @@
 # Modes

-Permission modes are settings that control the level of autonomy the AI has when interacting with your computer. By default, the system operates in Default Mode, where it must ask for your approval before it edits any files or executes shell commands. You can cycle through other levels of authority, such as Accept-Edits Mode, which allows the AI to modify files automatically while still prompting you for terminal commands, or Plan Mode, which restricts the AI to read-only tools so it can research and outline a strategy without making any actual changes. For advanced workflows, specialized states like Delegate Mode exist to limit a "lead" agent to coordinating other sub-agents, while the high-risk Bypass-Permissions Mode removes all approval prompts entirely for use in secure, isolated environments.
+Modes set the level of autonomy Claude Code has in a session. Manual mode asks before edits and shell commands, Accept Edits mode approves file changes and common filesystem commands automatically, and Plan mode keeps Claude read-only while it outlines a strategy. Auto mode has a classifier model check actions in the background instead of prompting you, dontAsk denies every call that would prompt, and Bypass Permissions removes all checks. You switch between modes during a session with the mode shortcut, or you start in one with the --permission-mode flag.

 Visit the following resources to learn more:

@@ -1,6 +1,6 @@
 # Permission Modes

-Claude Code features several permission modes that define the balance between autonomy and safety during your session, ranging from Plan mode, which restricts Claude to a read-only state for exploration and strategy without any tool execution, to BypassPermissions mode (often called "YOLO mode"), which grants the AI full autonomy to run any command or edit any file without interruption.
+Permission modes control how much Claude Code can do without asking you first. Manual (default) only runs reads without approval, acceptEdits also allows file edits and common filesystem commands, and plan restricts Claude to research and planning. auto lets a separate classifier model review each action and block risky ones, and it is the built-in starting mode in interactive sessions on recent versions. dontAsk denies anything that would prompt, and bypassPermissions runs everything and should only be used in isolated containers or VMs.

 Visit the following resources to learn more:

@@ -1,8 +1,9 @@
 # Scaling Claude Code

-Claude Code offers several ways to parallelize work across multiple agents or sessions: subagents, agent view, agent teams, and worktrees. Subagents are delegated workers that handle a side task within their own context and return a summary, keeping the main conversation clean. Agent view lets you dispatch independent sessions to the background and monitor them from a single screen. Agent teams coordinate multiple sessions through a shared task list and inter-agent messaging, managed by a lead agent. Worktrees isolate parallel sessions into separate git checkouts so they never conflict over the same files.
+Claude Code can split work across several agents or sessions. Subagents handle a side task in their own context and return a summary. Agent view lets you send independent sessions to the background and watch them from one screen. Agent teams coordinate multiple sessions through a shared task list and direct messages, led by one lead agent. Worktrees give each parallel session its own git checkout so they never edit the same files. For larger jobs, dynamic workflows orchestrate many subagents from a rerunnable script, and sessions can message each other directly.

 Visit the following resources to learn more:

 - [@official@Run agents in parallel](https://code.claude.com/docs/en/agents)
- [@official@Agent view](https://code.claude.com/docs/en/agent-view)
+- [@official@Agent view](https://code.claude.com/docs/en/agent-view)
+- [@official@Orchestrate teams of Claude Code sessions](https://code.claude.com/docs/en/agent-teams)
@@ -1,6 +1,6 @@
 # Scheduling Jobs

-Scheduled tasks let you run prompts automatically on a schedule in Claude Code. You can use the `/loop` command to repeat a prompt at regular intervals (like every 5 minutes or every 2 hours) while your session is open. You can also set one-time reminders for specific times. The tasks run in the background and stop when you close Claude Code. If you need tasks to keep running after you close the program, you should use Cloud or Desktop scheduled tasks instead.
+Scheduling jobs means running Claude Code prompts automatically, without you starting them each time. There are three options. /loop repeats a prompt inside an open session, desktop scheduled tasks run on your machine, and cloud scheduled tasks (formerly called routines) run on Anthropic infrastructure even when your laptop is closed. A cloud task can start from a schedule, an API call, or a GitHub event such as a new pull request. You create them with the /schedule command or on the web.

 Visit the following resources to learn more:

@@ -4,6 +4,6 @@ Claude Code offers multiple interfaces to cater to diverse development workflows

 Visit the following resources to learn more:

+- [@course@Claude 101](https://anthropic.skilljar.com/claude-101)
 - [@official@Use Claude Code everywhere](https://code.claude.com/docs/en/overview#use-claude-code-everywhere)
- [@article@Claude Cowork vs. Code vs. Chat: When to use each](https://roadmap.sh/claude-code/vs-cowork-vs-chat)
- [@course@Claude 101](https://anthropic.skilljar.com/claude-101)
+- [@article@Claude Cowork vs. Code vs. Chat: When to use each](https://roadmap.sh/claude-code/vs-cowork-vs-chat)