DevSpeak — AI Technical Translation

Stop explaining. Start communicating.

Transform informal stakeholder requirements into formal, audience-specific technical specifications — directly in your editor.

Screenshots

Welcome Screen	Full Editor with Output

Translation Panel	Settings & Controls

Features

Translation Workflow

DevSpeak implements a three-stage Stateful Translation Workflow. Understanding the distinction is important for effective use:

• The Translate Selection command sends the selection to the panel for Stage 2 (Translation Execution); CodeLens actions and DevSpeak: Optimize Text run Stage 1 (Lexical Optimization)
• The Refinement Panel is a Stage 3 tool — it modifies generated output, not raw input
• For the full architectural reference, see ARCHITECTURE.md

Getting Started

1. Install — search for DevSpeak in the Extensions Marketplace, or install the .vsix manually.
2. Sign In — run DevSpeak: Login from the Command Palette (Ctrl+Shift+P).
   • OAuth (Google / GitHub) requires a free DevSpeak account at devspeak.dev.
   • Or paste a dsk_live_ API key (Developer tier and above).
3. Translate — select text → Cmd+Shift+T (Ctrl+Shift+T), or open the sidebar and type directly.

Extension Settings

Where settings are saved

Editing a setting in the DevSpeak panel writes it to your user settings, except Custom Instructions — those are written to the current workspace's .vscode/settings.json so project-specific terminology and codebase paths do not follow you into unrelated projects. When no folder is open, they fall back to user settings.

A value you write directly into a settings.json always wins over the panel's last remembered state, and is picked up without a reload. The most specific scope applies: folder, then workspace, then user. Setting devspeak.customInstructions to "" means "no instructions", not "fall back".

Custom Instructions set on your DevSpeak account are applied when the current workspace has no instructions of its own; a workspace value is never overwritten by your account value.

Commands

Requirements

• VS Code 1.85 or later (also works in Cursor and Windsurf)
• A DevSpeak account or API key — sign up free at devspeak.dev

Cross-Platform Compatibility

This extension targets extensionKind: ["ui"] and uses standard VS Code APIs. It is verified to work in:

• Visual Studio Code (desktop and web)
• Cursor (via .vsix sideload or Open VSX)
• Windsurf (via .vsix sideload)

Telemetry

DevSpeak can collect anonymous usage data to learn which features are used and where requests fail. It is off unless you opt in. After your first successful translation, DevSpeak asks once; you can also turn it on or off anytime with the devspeak.telemetry.enabled setting. Your VS Code telemetry setting always wins: nothing is sent unless telemetry.telemetryLevel is all, whatever the DevSpeak setting says.

What is collected: which DevSpeak features and commands you use, the settings you choose (audience, context, format, tone), character counts, request durations, a closed error category (for example, network or rate_limited), your plan tier when a feature is not included in it, the editor family (VS Code, Cursor, Windsurf, VSCodium), the operating system, and the extension version.

What is never collected: the text you translate or optimize, generated output, refinement feedback, files or file names, paths, email addresses, your account identifier, or API keys.

Usage data is tied to a random identifier generated on this install. It is not linked to your DevSpeak account, and it is replaced when you turn telemetry off. Events are sent to DevSpeak, which forwards them to Google Analytics with advertising use disabled. Every event and property is listed in telemetry.json; run code --telemetry to see them alongside VS Code's own. See the Privacy Policy.

Telemetría

DevSpeak puede recopilar datos de uso anónimos para saber qué funciones se usan y dónde fallan las solicitudes. Está desactivado salvo que des tu consentimiento. Tras tu primera traducción exitosa, DevSpeak lo pregunta una sola vez; también puedes activarlo o desactivarlo cuando quieras con la configuración devspeak.telemetry.enabled. Tu configuración de telemetría de VS Code siempre prevalece: no se envía nada a menos que telemetry.telemetryLevel sea all, diga lo que diga la configuración de DevSpeak.

Qué se recopila: qué funciones y comandos de DevSpeak usas, la configuración que eliges (audiencia, contexto, formato, tono), recuentos de caracteres, la duración de las solicitudes, una categoría de error cerrada (por ejemplo, network o rate_limited), tu plan cuando una función no está incluida en él, la familia de editor (VS Code, Cursor, Windsurf, VSCodium), el sistema operativo y la versión de la extensión.

Qué nunca se recopila: el texto que traduces u optimizas, el resultado generado, los comentarios de refinamiento, archivos o nombres de archivo, rutas, direcciones de correo, el identificador de tu cuenta ni claves de API.

Los datos de uso se asocian a un identificador aleatorio generado en esta instalación. No está vinculado a tu cuenta de DevSpeak y se reemplaza cuando desactivas la telemetría. Los eventos se envían a DevSpeak, que los reenvía a Google Analytics con el uso publicitario desactivado. Cada evento y propiedad aparece en telemetry.json; ejecuta code --telemetry para verlos junto a los de VS Code. Consulta la Política de Privacidad.

Feedback & Issues

File issues at github.com/juanjaragavi/devspeak.

License

Apache-2.0