Tool
Cline
An open-source coding agent that can live in your editor or CLI, edit files, run commands with approval, and talk to the model provider you configure.
What it is
Cline is an AI coding agent (VS Code extension, with CLI/JetBrains surfaces in the project) that can create/edit files, run terminal commands, and use tools with human-in-the-loop approval. The GitHub repo cline/cline is under Apache License 2.0. You typically bring your own API keys or local endpoint; an optional hosted “Cline” provider is a separate commercial path.
What it replaces
It replaces copy-paste chat and some proprietary IDE agents when you want an auditable Apache-2.0 client pointed at models you choose (including local). It does not replace judgment — autonomous edits still need review.
License
Apache License 2.0 for the open-source client. Maintainers have clarified that cline.bot Terms of Service apply to the optional hosted API provider path, not to BYO-key/local use of the Apache-2.0 extension. Read both if you flip that dropdown.
Where it falls over
- Agent loops can spend API money quickly; local models trade cost for quality.
- Tool use + shell approval fatigue → people click through and regret it.
- Extension vs hosted ToS confusion — know which provider mode you are in.
- Complex repos still require human architecture; the agent is not a staff engineer.
Who it's for
Developers who want an open agent client, BYO models, and editor integration without going full proprietary IDE. Teams should standardize provider mode and approval habits.
Verdict
Use Cline when Apache-2.0 + BYO keys match your constraints. Keep hosted Cline API ToS out of the story unless you actually use that provider. Review every risky tool call.