{"slug": "i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching", "title": "I Built an AI Coding Assistant Because I Got Tired of Context Switching", "summary": "Creation of Coda AI, a VS Code extension designed to eliminate the workflow friction of constantly switching between a code editor and a browser to use AI tools. Unlike basic AI assistants, Coda understands the entire project structure, can autonomously inspect code, propose changes, and execute commands while keeping the user in control through approval prompts. It also supports multiple AI providers and the Model Context Protocol (MCP) for flexible, external tool integration.", "body_md": "AI coding tools are everywhere. And yet, my workflow kept breaking the same way:\nWrite code → leave VS Code → open browser → ask AI → copy response → come back → repeat.\nEvery switch costs focus. Those interruptions add up.\nI wanted an assistant that lived inside the editor and could handle real development work — not just answer questions. So I built Coda AI.\nCoda AI is a VS Code extension with:\nHere's what I focused on when building it.\nCoda understands your project structure — not just the file you have open. It uses your actual codebase as context, so responses are grounded in your real code, not generic examples.\nInstead of asking:\n\"How do I fix this?\"\nYou hand it a task and let it run:\nThe agent can inspect code, propose changes, execute commands, and iterate — with approval prompts for sensitive actions so you stay in control.\nOne thing that consistently bothered me about AI tooling: you adopt a workflow, then you're stuck with one provider.\nCoda supports:\nIf a better model ships tomorrow, your workflow doesn't need to change.\nThis was one of my favourite parts to build.\nCoda supports the Model Context Protocol (MCP), so the agent can work with external tools automatically:\nNo hardcoded integrations. You plug in what you need.\nDeveloper tooling isn't only about adding intelligence. It's about reducing friction.\nThe fewer times you leave flow state, the better the tool.\nIntelligence without integration is just another tab to switch to.\nCoda is still early, and I'm actively improving it.\nIf you're a developer, I'd genuinely value your input:\nWhat would make an AI coding assistant actually useful in your day-to-day workflow?\nDrop your thoughts in the comments — critical feedback welcome.\n🔗 Install on the VS Code Marketplace\nBuilt by a developer who got tired of switching tabs. Shipping, not just talking about it.", "url": "https://wpnews.pro/news/i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching", "canonical_source": "https://dev.to/maeba96/i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching-2e9b", "published_at": "2026-05-20 06:19:47+00:00", "updated_at": "2026-05-20 06:32:19.544756+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "large-language-models", "products", "open-source"], "entities": ["Coda AI", "VS Code", "Model Context Protocol", "MCP"], "alternates": {"html": "https://wpnews.pro/news/i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching", "markdown": "https://wpnews.pro/news/i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching.md", "text": "https://wpnews.pro/news/i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching.txt", "jsonld": "https://wpnews.pro/news/i-built-an-ai-coding-assistant-because-i-got-tired-of-context-switching.jsonld"}}