Yamakawa Code

A Claude Code–style chat sidebar for VS Code, powered by any OpenAI-compatible endpoint.

Features

• Sidebar chat view with a refined, Claude-inspired UI.
• Streaming responses with a smooth typewriter effect.
• Markdown rendering (headings, lists, code blocks, inline code, links).
• Per-workspace conversation history with one-click clear.
• Multi-provider support: OpenAI-compatible, Anthropic, Gemini, and Ollama.
• In-sidebar presets for OpenAI, Claude, Gemini, DeepSeek, Kimi, OpenRouter, xAI, Groq, Ollama, and custom OpenAI-compatible endpoints.
• Select one or more local SKILL.md, Markdown, or text instruction files; enabled skills persist per workspace.
• Review every AI write, patch, or deletion in VS Code's native red/green diff editor before it is applied.
• Search the official MCP Registry, install npm/stdio or connect Streamable HTTP servers, and expose their tools to any configured model.
• File attachments in chat (images and text files).
• Configurable provider, base URL, model, system prompt, and temperature.

Defaults

• Provider: openai
• Base URL: https://api.openai.com/v1
• Model: gpt-5.2

Configuration

Open Settings and search for Yamakawa Code to customize:

• yamakawaCode.provider
• yamakawaCode.baseUrl
• yamakawaCode.model
• yamakawaCode.apiKey
• yamakawaCode.systemPrompt
• yamakawaCode.temperature
• yamakawaCode.workspaceTools

API key fallback by provider (when yamakawaCode.apiKey is empty):

• openai: OPENAI_API_KEY -> OHMYGPT_API_KEY
• anthropic: ANTHROPIC_API_KEY -> CLAUDE_API_KEY
• gemini: GEMINI_API_KEY -> GOOGLE_API_KEY -> GOOGLE_GENERATIVE_AI_API_KEY
• ollama: no API key required

The provider picker can store separate keys for separate API endpoints in VS Code SecretStorage.

Skills and safe code updates

• Click the sparkle button beside the attachment button and choose one or more skill files.
• Enabled skills appear as removable chips and are re-read for every request.
• When a model proposes a workspace change, Yamakawa Code opens a Before ↔ Proposed diff.
• Choose Apply changes to write it or Reject to leave the workspace untouched.

MCP discovery and installation

• Click the link/plug button in the composer or view title.
• Search the official MCP Registry by server name and inspect its description, version, source package, and repository.
• Yamakawa Code currently supports local npm packages over stdio and remote Streamable HTTP servers.
• npm servers are downloaded through npx only after explicit confirmation.
• Secrets requested by registry metadata are stored in VS Code SecretStorage.
• The model can use search_mcp, request install_mcp, and call discovered mcp__... tools. Installation and every MCP tool call require user approval.

The official Registry is metadata, not a security endorsement. Review the package and repository before installing. OAuth-only remote servers and PyPI/OCI packages are not yet supported.

Development

npm install
npm run compile

One-Command Setup (For New Contributors)

After cloning this repository, people only need to run one command to set up:

python3 scripts/bootstrap_project.py

Or:

npm run bootstrap

What each helper script is for:

• scripts/bootstrap_project.py: install dependencies and compile the project.
• scripts/update_github.py: commit + pull --rebase + push safely.
• scripts/publish_extension.py: build and publish the VS Code extension.

Release

Create an installable VSIX without publishing:

npm install -g @vscode/vsce
npm run compile
vsce package

The generated file is named yamakawa-code-0.3.1.vsix. Install it from VS Code with Extensions: Install from VSIX....

Set Marketplace token first:

export VSCE_PAT=your_marketplace_pat

Then use one command:

npm run release:patch

Or publish through Python helper:

python3 scripts/publish_extension.py --bump patch

Other version bumps:

npm run release:minor
npm run release:major

Press F5 in VS Code to launch the Extension Development Host.