Speedpost IntelliCode

Speedpost IntelliCode is a local-first, bring-your-own-key coding assistant for VS Code. It focuses on cautious coding workflows: explicit provider setup, bounded context, safe diff previews, terminal command approval, local project rules, metadata-only usage tracking, and local quality gates.

This MVP has no Speedpost backend, hosted account, billing system, cloud sync, team sync, or telemetry pipeline.

What It Does

• Opens a Speedpost IntelliCode sidebar for provider setup, chat, project state, proposed edits, usage, terminal approvals, rules, and quality gates.
• Supports BYOK provider configuration for OpenAI, Anthropic, Google Gemini, OpenRouter, and local Ollama.
• Stores provider API keys with VS Code SecretStorage, not normal settings or workspace files.
• Sends chat, selected-code, active-file, terminal-error, and quality-analysis requests only through the configured provider flow.
• Blocks or warns on sensitive files, secret-like content, large active files, unsafe rules, and large estimated requests.
• Scans repository metadata with ignore handling; relevant-file selection is metadata-first and explainable.
• Creates in-memory proposed edits, opens VS Code diff previews, and requires approval before applying changes.
• Suggests test/build/lint commands, then routes execution through explicit terminal approval.
• Tracks usage metadata locally, including estimated tokens and known/unknown cost status.
• Validates .devphase/rules.md and includes only a bounded safe summary in prompt flows.
• Suggests and runs quality gates through the same terminal approval model.

What It Does Not Do

• It does not run an autonomous agent.
• It does not silently edit files or silently run terminal commands.
• It does not install dependencies automatically.
• It does not provide billing, subscriptions, user accounts, cloud storage, or team features.
• It does not guarantee provider price accuracy; unknown remote pricing is shown as unknown.
• It does not store prompts, responses, source snapshots, API keys, or raw terminal logs in usage history.

Supported Providers

• OpenAI
• Anthropic
• Google Gemini
• OpenRouter
• Ollama

Remote providers require your own API key. Ollama uses a local endpoint and does not require a provider API key in Speedpost IntelliCode.

Installation

Install from the VS Code Marketplace when available, then open a workspace and click the Speedpost IntelliCode Activity Bar icon.

For local VSIX testing, build the package:

npm.cmd install
npm.cmd run package:vsix

Install the generated VSIX:

code --install-extension dist\speedpost-intellicode-0.0.1.vsix

For a cleaner manual test profile:

code --user-data-dir .vscode-test\manual-user-data --extensions-dir .vscode-test\manual-extensions --install-extension dist\speedpost-intellicode-0.0.1.vsix
code --user-data-dir .vscode-test\manual-user-data --extensions-dir .vscode-test\manual-extensions .

Getting Started

1. Open a project folder in VS Code.
2. Open the Speedpost IntelliCode activity bar view or run Speedpost IntelliCode: Open Sidebar Chat.
3. Run Speedpost IntelliCode: Select Provider.
4. Run Speedpost IntelliCode: Select Model.
5. For remote providers, run Speedpost IntelliCode: Set Provider API Key.
6. Optionally run Speedpost IntelliCode: Create Project Rules File and edit .devphase/rules.md.
7. Use sidebar chat or command palette actions.

Main Commands

Provider and setup:

• Speedpost IntelliCode: Open Sidebar Chat
• Speedpost IntelliCode: Open Settings
• Speedpost IntelliCode: Select Provider
• Speedpost IntelliCode: Select Model
• Speedpost IntelliCode: Set Provider API Key
• Speedpost IntelliCode: Delete Provider API Key
• Speedpost IntelliCode: Show Provider Status
• Speedpost IntelliCode: Test Provider Connection

Editor actions:

• Speedpost IntelliCode: Explain Selected Code
• Speedpost IntelliCode: Fix Selected Code
• Speedpost IntelliCode: Refactor Selected Code
• Speedpost IntelliCode: Generate Tests for Selected Code
• Speedpost IntelliCode: Add Comments to Selected Code
• Speedpost IntelliCode: Explain Active File
• Speedpost IntelliCode: Summarize Active File
• Speedpost IntelliCode: Find Issues in Active File

Safe edits:

• Speedpost IntelliCode: Preview Proposed Edit
• Speedpost IntelliCode: Apply Proposed Edit
• Speedpost IntelliCode: Reject Proposed Edit
• Speedpost IntelliCode: List Proposed Edit Queue
• Speedpost IntelliCode: Clear Proposed Edit Queue

Project, terminal, rules, usage, and quality:

• Speedpost IntelliCode: Scan Project
• Speedpost IntelliCode: Find Relevant Files
• Speedpost IntelliCode: Suggest Test Command
• Speedpost IntelliCode: Suggest Build Command
• Speedpost IntelliCode: Suggest Lint Command
• Speedpost IntelliCode: Run Pending Command With Approval
• Speedpost IntelliCode: Analyze Terminal Error
• Speedpost IntelliCode: Create/Open/Validate/Summarize/Reset Project Rules File
• Speedpost IntelliCode: Show Usage Summary
• Speedpost IntelliCode: Open Usage Limit Settings
• Speedpost IntelliCode: Suggest Quality Gates
• Speedpost IntelliCode: Run Quality Gates
• Speedpost IntelliCode: Show Quality Report
• Speedpost IntelliCode: Review Project Rules Compliance
• Speedpost IntelliCode: Review Diff Safety

Settings

Important settings are under Speedpost IntelliCode:

• devphase.provider
• devphase.model
• devphase.openai.baseUrl
• devphase.openrouter.baseUrl
• devphase.ollama.baseUrl
• devphase.localFirstMode
• devphase.telemetry.enabled
• devphase.maxContextFiles
• devphase.costTracking.enabled
• devphase.usage.*

The devphase.* setting keys and .devphase/rules.md workspace file path remain stable in this MVP for compatibility with the existing local workflow. The visible product name, Marketplace identity, commands, sidebar, and icon are Speedpost IntelliCode.

Do not put API keys in settings. Use Speedpost IntelliCode: Set Provider API Key so VS Code SecretStorage handles them.

Privacy And Security

Speedpost IntelliCode is local-first, but selected provider requests can send user-approved prompt content to the provider you configure. The extension has no Speedpost-hosted backend in the MVP.

Built-in safeguards include SecretStorage for keys, telemetry disabled by default, sensitive context blocking, safe rules summaries, sanitized terminal output, explicit terminal approval, and diff preview before apply.

Local Development

Install dependencies:

npm.cmd install

Compile:

npm.cmd run compile

Lint:

npm.cmd run lint

Run extension tests:

npm.cmd test

Package a local VSIX:

npm.cmd run package:vsix

Debug from VS Code:

1. Open this folder in VS Code.
2. Press F5.
3. Choose the extension launch configuration if prompted.
4. Use the Speedpost IntelliCode activity bar view or command palette in the Extension Development Host.

Troubleshooting

• If the sidebar does not open, run Speedpost IntelliCode: Open Sidebar Chat from the Command Palette.
• If remote chat fails, confirm provider, model, and API key setup.
• If Ollama fails, confirm the local Ollama server is running and devphase.ollama.baseUrl is correct.
• If a proposed edit cannot be applied, preview the diff first and confirm the target file has not changed since proposal creation.
• If terminal output is not captured, VS Code shell integration may be unavailable; select or paste terminal output before running error analysis.
• If usage cost is unknown, the selected provider/model does not have local pricing metadata.

Known Limitations

The most important MVP limitations are that proposed edits are single-file and in memory, terminal output capture depends on VS Code shell integration, remote pricing is not guessed, and provider behavior depends on the provider/model you configure.