Stay on track
Keep main-session history and familiar controls for titles, models and CLI restarts while working on the current task.
VS Code extension / LLS CCAI
Connect your AI workflow
inside your editor.
Claude Code Config Helper brings local Claude CLI, model providers, parallel sessions and developer tools into VS Code. Switch fewer windows and keep more context.
Local test build 3.2.76 · Check Marketplace for the published version · Bring your own model provider
my-project / Visual Studio Code
PARALLEL SESSION↗ · ↻
Understand data, investigate issues
Inspect the test database’s order tables;
analyze read-only, without changing data.
analyze read-only, without changing data.
Check structure, then relationships.Use configured MCP tools to gather information
and organize findings in a separate context.
and organize findings in a separate context.
↗ mcp · mysql / inspect schema
Continue this task…↑
src / order-service.tsTypeScript
✓ Files, diagnostics and tools in one workspace
MAIN SESSION✎ · ＋ · ↻
Focus on the current task
Implement the order lookup API from the plan;
preserve the existing API behavior.
preserve the existing API behavior.
Start with the existing implementation.Read the code, break down the changes,
then check diagnostics and tests.
then check diagnostics and tests.
✓ read → edit → diagnostics
Describe what you want to build…↑
LLS CCAI · Separate sessions / separate settingsClaude CLI + MCP · Your workspace, your workflow
Two conversations. One workspace.
Room for main and supporting tasks.
Implement a feature in one session and research or review in another. Keep separate contexts instead of one long conversation.
Help when needed
Click parallel session or the top plus button to open an independent session on the left. Click again to resume it, not create another.
Keep code at the center
Files, browser tabs and docs keep the normal editor area. Opening settings or hiding the left panel does not stop its task.
Separate sessions do not isolate files. Both can edit the same workspace: divide work by file or module and review diffs.
Built around real tasks
The features you need, within reach.
Clear steps from installation
Three setup steps cover CLI validation, providers and workspace models. Downloads use the official source unless you explicitly choose the China mirror.
Different models for different tasks
Use separate models for regular tasks, task flows and compaction. Thinking levels include Auto, Low, Medium, High and XHigh, subject to provider support.
Keep moving from your plan
Organize a plan into task-flow steps and continue execution. Human review of tool actions, code quality and final results is still required.
Usage you can see
Inspect input, output, cache reads/writes and context usage. Figures depend on provider responses and do not replace billing checks.
Connect existing MCP tools
Workspace .mcp.json follows CLI loading rules; VS Code MCP configuration can also be connected. Your configuration controls strict mode.
Work in your language
Available in Simplified Chinese, Traditional Chinese, English, Japanese, Korean, French and German, including common actions and setup guidance.
Choose your connections
The extension organizes your workflow.
MCP adds the tools.
Use the extension and MCP together or separately. SSH, MySQL, SQL Server, Redis and API Debug provide connections for different stages of development.
Know the boundaries first
- A working local CLI and your own model provider are required.
- API calls may incur provider charges. No model credits are included.
- API keys use VS Code SecretStorage; model requests still go to your configured provider.
- bypass skips CLI permission checks. Use only in trusted workspaces.
- Usage attribution may be limited when gateways reuse response IDs.
Build more. Switch less.
Start with one extension, add tools as needed, and try them in a test environment first.