Short answer: in VS Code, open the Cline sidebar (extension ID saoudrizwan.claude-dev), click the chat input, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak a complete task spec, press the hotkey again, then send. Cline proposes file edits, terminal commands, and browser steps; you approve each action.
Cline is an open-source (Apache 2.0) autonomous coding agent: VS Code extension (primary), JetBrains plugin, and a growing CLI (apps/cli). You bring your own API key (Anthropic, OpenAI, OpenRouter, Bedrock, Gemini, Ollama, etc.). Cline is free to install; you pay your provider for tokens.
Cline vs inline Copilot
Cline is agent-first: multi-file edits, terminal runs, MCP tools, optional browser use (Puppeteer), and checkpoints to roll back. It is not the same as gray inline completions. Short chat prompts produce shallow plans; long dictated specs match how Cline is designed to work.
Surfaces and modes
| Surface | AICHE workflow |
|---|---|
| Cline chat input | Main task and follow-ups |
| Plan mode | Dictate exploration goals before Act |
| Act mode | Dictate execution after you approve a plan |
.clinerules |
Edit rule files with AICHE in VS Code like any other file |
| MCP Marketplace | Configure servers in UI; dictate "use the Postgres MCP read-only" in the task |
| CLI (preview) | Terminal prompt field: same hotkey when the CLI has focus |
Human-in-the-loop: Cline shows intended commands and diffs before running. Dictate explicit approval rules in the first message ("ask before npm publish", "run unit tests automatically").
How it works
- Install Cline from the VS Marketplace (or JetBrains / CLI per cline/cline).
- Open the Cline icon in the Activity Bar. Set API Provider and model in Cline settings (gear).
- Click the chat text box at the bottom of the Cline panel.
- Toggle ⌃+⌥+R / Ctrl+Alt+R, speak 45 to 120 seconds: goal, files, tests, non-goals.
- Toggle again. AICHE inserts cleaned text.
- Send. Approve or reject each tool call Cline proposes.
Project rules: Add .clinerules in the repo root for coding standards, test commands, and architecture constraints. Cline loads them automatically; mention "follow .clinerules" in dictated prompts when you add new conventions.
Also runs in: VS Code forks such as Cursor and Windsurf (same extension install flow as VS Code per Cline's repo). Focus that editor's Cline sidebar input; same hotkey.
Cost honesty
Cline has no subscription, but heavy Act loops on premium models can exceed flat-rate IDE plans. Cline shows token usage in the sidebar. Voice does not change token math; it helps you send fewer underspecified retries.
What you get with AICHE
- Custom vocabulary for domain terms Cline should see in transcripts.
- Software Development profile (Pro) for identifiers and CLI flags.
- Audio discarded immediately after processing, within 1 second.
FAQ
Q: Does AICHE click Cline's Approve buttons?
A: No. You approve tools and edits in Cline's UI.
Q: Cline vs Claude Code extension?
A: Claude Code extension is Anthropic's collaborative assistant. Cline is BYOK and often more autonomous. See /works-with/claude-code for terminal Claude Code.
Q: MCP setup?
A: Use Cline's MCP UI. AICHE only supplies natural-language task text.
Related
Try it: Plan mode on an unfamiliar folder, dictate "map modules and test entrypoints only", then Act mode with a single implementation step after you read the plan.