Cline 3.48.0: Skills and Websearch Now Live

TL;DR

• Cline 3.48.0 adds Skills (reusable domain knowledge modules) and websearch tooling for real-time lookups
• Skills load on-demand, so you can package extensive knowledge without burning context tokens
• Websearch lets Cline fetch current docs and API references as clean text instead of launching a browser
• Available now on VS Code, Cursor, and Windsurf marketplaces

What Dropped

Cline 3.48.0 introduces two major features: Skills, a system for packaging reusable domain knowledge that loads on-demand, and websearch tooling that lets Cline search and fetch web content as text. The release also adds Gemini thinking support, Katcoder to the model list, and fixes a regression affecting the diff view.

The Dev Angle

Skills work like progressive onboarding. Instead of dumping all documentation at once, each skill is a directory with a SKILL.md file containing metadata and instructions. Cline sees only the skill name and description initially. When your request matches what a skill does, Cline loads the full instructions. This means you can maintain dozens of skills—release workflows, code review checklists, API patterns, debugging guides for specific frameworks—without context overhead.

Skills live in two places: global skills in ~/.cline/skills/ (or C:\Users\USERNAME\.cline\skills\ on Windows) apply to all projects, while project skills in .cline/skills/ are workspace-specific. The key is writing clear descriptions in the SKILL.md frontmatter—that's what triggers Cline to activate the skill when relevant.

Websearch tooling is available to Cline provider users with credits. Unlike the browser tool (which launches a headless browser and parses screenshots), websearch fetches content as clean text. When Cline needs to check current documentation, look up an API reference, or find recent information, it searches and retrieves that content directly. No browser overhead, no visual interpretation, faster and cheaper.

Together, Skills and websearch create a powerful combination: Skills encode your institutional knowledge and workflows; websearch keeps Cline current with information that changes over time.

Should You Care?

If you're already using Cline: Skills are worth setting up if you have repeatable workflows, domain-specific patterns, or institutional knowledge you want to codify. The on-demand loading means zero performance penalty for skills you don't use. Websearch is automatic for Cline provider users—it activates when Cline determines it needs external information.

If you're on the free tier or using Claude API directly: Skills work for you, but websearch requires the Cline provider with credits. The browser tool remains available as an alternative.

The real win: Skills let you scale Cline's knowledge without scaling context consumption. If you've been hesitant to give Cline access to extensive documentation because of token costs, Skills solve that problem. Pair them with websearch and you get an agent that knows your workflows and can stay current with the outside world.

Getting Started

Enable Skills in Settings → Features → Enable Skills. You'll see a new Skills tab in the rules and workflows panel. Create a skill by adding a .cline/skills/ directory in your project with a SKILL.md file. Start simple: document one workflow, one checklist, or one set of patterns. Websearch activates automatically for Cline provider users.

Full details are in the Skills documentation.

Update Now

Cline 3.48.0 is available on the VS Code Marketplace, Cursor, and Windsurf. Update through your extension manager or reinstall from the marketplace.

Source: Cline