Cline 桌面版 v0.0.31：支持通过 SSH 在远程主机运行 agent，子 agent 并行执行

Official release notes (https://github.com/cline/cline/releases/tag/desktop-v0.0.31) - Cline can now work on a remote machine over SSH, with the app itself staying local. Add and test a host under **Settings → Remote**, then pick it from the environment selector beside the workspace picker on the welcome screen — saving or testing a profile does not activate it. The connection opens at the remote user's home directory; **Add project…** in the workspace picker browses that machine for a project, and **Local** disconnects. Agent tools, workspace discovery, Git metadata, and session persistence all run on the host while approvals and live session events return to the desktop, because only the authenticated Cline Hub protocol is forwarded through the tunnel. SSH config aliases work: leave **Port** blank to use the alias's own configuration, or enter one to override it. Recent and last-used workspaces are remembered separately per host. Host metadata lives at `~/.cline/data/settings/remote-environments.json` (mode `0600`) and records an identity-file path, never private-key contents; the host key must already be trusted by your SSH client, and unknown or changed keys are rejected. On first connect Cline uploads a self-contained helper to `~/.cline/remote/` — no `apt`, `npm`, root access, global CLI install, or public port — and caches it for faster reconnects, leaving any existing Cline CLI hub on that account running. Linux x64 and arm64 hosts are supported (32-bit Raspberry Pi operating systems are not; macOS hosts need a locally built helper via `CLINE_REMOTE_HELPER_BINARY`). File attachments and opening a remote file in a local editor are not available in remote sessions yet — text, images, file mentions and search, Git branch operations, session history, and remote agent tools are - Sub-agents spawned in the same step now run at the same time instead of one after another, so delegating three independent pieces of work takes as long as the slowest one rather than the sum of all three. Tools that must run in order still do, and only back-to-back parallel calls overlap **Full Changelog**: https://github.com/cline/cline/compare/desktop-v0.0.30...desktop-v0.0.31 Repository README (current repository documentation, not release changes) Cline The open source coding agent in your IDE, terminal, & desktop. Docs Discord r/cline Feature Requests Join us! ### CLI Run Cline in your terminal. Interactive chat or fully headless for CI/CD and scripting. ``` npm i -g cline ``` Learn more ### Desktop App Cline as a native app for macOS and Windows. Run agent sessions in any folder, schedule routines, and manage models, plugins, and MCP servers. Download for macOS and Windows ### VS Code Extension AI coding assistant in your editor. Create files, run commands, browse the web, and use tools with human-in-the-loop approval. Install from VS Marketplace ### JetBrains Plugin The same Cline experience in IntelliJ IDEA, PyCharm, WebStorm, GoLand, and the rest of the JetBrains family. Install from JetBrains Marketplace ### SDK Build your own AI agents and integrations powered by the same engine that runs the CLI, desktop app, VS Code extension, and JetBrains plugin. Custom tools, multi-agent teams, connectors, scheduled automations, and more. ``` npm install @cline/sdk ``` Documentation --- ## Index | Product | Description | Location | CHANGELOG | |---------|------------|--------------|--------------| | **SDK** | Node.js programmatic agent API and extension exports. | [`sdk/`](https://github.com/cline/cline/tree/main/sdk) | [CHANGELOG.md](https://github.com/cline/cline/blob/main/sdk/CHANGELOG.md) | | **CLI** | Terminal UI, headless mode, shell commands, and CLI-specific flows. | [`apps/cli/`](https://github.com/cline/cline/tree/main/apps/cli) | [CHANGELOG.md](https://github.com/cline/cline/blob/main/apps/cli/CHANGELOG.md) | | **VS Code Extension** | The Marketplace extension and extension host integration. | [`/`](https://github.com/cline/cline/tree/main) (WIP migrating) | [CHANGELOG.md](https://github.com/cline/cline/blob/main/CHANGELOG.md) | | **Desktop App** | Native macOS and Windows app (Tauri shell, Bun sidecar, Next.js UI). | [`apps/examples/desktop-app/`](https://github.com/cline/cline/tree/main/apps/examples/desktop-app) | [CHANGELOG.md](https://github.com/cline/cline/blob/main/apps/examples/desktop-app/CHANGELOG.md) | | **JetBrains Plugin** | JetBrains-hosted client that talks to the shared agent core. | Currently we are not open-sourcing JetBrains plugins | - | | **Docs site** | Public documentation pages. | [`docs/`](https://docs.cline.bot/) | - | ## Edits Code Across Your Project Cline reads your project structure, understands the relationships between files, and makes coordinated changes across your codebase. It monitors linter and compiler errors as it works, fixing issues like missing imports, type mismatches, and syntax errors before you even see them. In VS Code and JetBrains, every edit shows up as a diff you can review, modify, or revert. All changes are tracked with checkpoints, so you can easily undo the agent's work. ## Runs Bash Commands Cline executes commands directly in your terminal and watches the output in real time. Install packages, run build scripts, execute tests, deploy applications, manage databases. For long-running processes like dev servers, Cline continues working in the background and reacts to new output as it appears, catching compile errors, test failures, and server crashes as they happen. ## Plan and Act Toggle between Plan mode and Act mode. In Plan mode, Cline explores your codebase, asks clarifying questions, and lays out a strategy. Once you're aligned, switch to Act mode and Cline executes the plan. Every file edit and terminal command requires your approval, so you stay in control of what actually changes. Or toggle auto-approve and let Cline run autonomously. ## Rules and Skills Define project-specific rules in `.clinerules` files that guide how Cline works in your codebase: coding standards, architecture conventions, deployment procedures, testing requirements. Rules are picked up automatically by the CLI, VS Code extension, and JetBrains plugin. Use skills to let the model load specific rules when needed. ## Works With Every Model Cline is not locked to a single AI provider. Use whichever model fits your workflow: | Provider | Models | |----------|--------| | Anthropic | Claude Opus, Sonnet, Haiku | | OpenAI | GPT series models | | Google | Gemini series models | | OpenRouter | 200+ models from any provider | | Vercel AI Gateway | Route to many providers through one gateway | | AWS Bedrock | Claude, Llama, and more | | Azure / GCP Vertex | All hosted models | | Cerebras / Groq | Fast inference models | | Ollama / LM Studio | Run local models on your machine | | Any OpenAI-compatible API | Self-hosted or third-party endpoints | ## Extend With Plugins or MCP Servers Extend Cline's capabilities with plugins. Using the SDK, register tools and lifecycle hooks programmatically through the plugin system for logging, auditing, policy enforcement, or adding domain-specific capabilities. Simple plugin example below. ```typescript import { Agent, createTool } from "@cline/sdk" const deployTool = createTool({ name: "deploy", description: "Deploy the current branch to staging.", inputSchema: { type: "object", properties: { env: { type: "string" } }, required: ["env"] }, execute: async (input) => { // your deployment logic }, }) const agent = new Agent({ tools: [deployTool], /* ... */ }) ``` ...or use [MCPs](https://github.com/modelcontextprotocol) to connect to databases, query APIs, manage cloud infrastructure, and interact with external systems. Use [community-built servers](https://github.com/modelcontextprotocol/servers) or ask Cline to create custom tools on the fly. In the CLI, manage servers with `cline mcp`. ## Multi-Agent Teams Coordinate multiple agents working together on complex tasks. A coordinator agent breaks the work into subtasks and delegates to specialist agents, each with their own tools and context. Team state persists across sessions so you can pick up where you left off. ```bash cline --team-name auth-sprint "Plan and implement user authentication with tests" ``` ## Scheduled Agents Run agents on cron schedules for recurring automations. Daily PR summaries, weekly dependency checks, codebase health reports. Schedules persist across restarts and run independently of any terminal session. ```bash cline schedule create "PR summary" \ --cron "0 9 * * MON-FRI" \ --prompt "List all open PRs and their review status" \ --workspace /path/to/repo ``` ## Connect to Slack, Telegram, Discord, and More Chat with your agent from any messaging platform: Telegram, Slack, Discord, Google Chat, WhatsApp, and Linear. Each conversation thread maps to an agent session with full context. Set up access control to restrict who can interact with your agent. ```bash # Connect to Telegram cline connect telegram -k $BOT_TOKEN # Connect to Slack through webhook cline connect slack --bot-token $SLACK_TOKEN --signing-secret $SECRET --base-url $URL # Connect to Slack using socket mode cline connect slack --bot-token $SLACK_TOKEN --app-token $SLACK_APP_TOKEN ``` ## Headless CLI for CI/CD Run Cline with zero interaction for scripting and automation. Pipe input, get JSON output, chain commands, integrate into CI/CD pipelines. ```bash cline "Run tests and fix any failures" git diff origin/main | cline "Review these changes for issues" cline --json "List all TODO comments" | jq -r 'select(.type == "agent_event" and .event.text) | .event.text' ``` ## Contributing Start with the [Contributing Guide](CONTRIBUTING.md). Join our [Discord](https://discord.gg/cline) and head to the `#contributors` channel to connect with other contributors. Check our [careers page](https://cline.bot/join-us) for full-time roles. ## License [Apache 2.0 © 2026 Cline Bot Inc.](./LICENSE)