massCode v6: AI assistant, MCP, and faster everyday work
massCode v6 brings a built-in AI assistant, connections to external coding agents, and performance improvements for larger libraries.
An AI assistant inside your workspace
Ask the assistant to edit snippets, organize notes, update tasks, or work with HTTP requests. It can use the open record, selected text, or find relevant content in your vault. One conversation stays with you as you switch between Code, Notes, and HTTP.
Try asking: “Add a timeout to this function and update the usage example,” or “Run this collection, explain the failed checks, and save a report in Notes.”
Connect your own AI provider account or use a local model through Ollama or LM Studio. Cloud usage is billed through your provider. You can request a preview before applying edits, and supported changes can be undone.
Your vault, connected to your coding agent
MCP support lets external coding agents search your vault, read saved examples, and save new snippets or notes. They can also create and update HTTP requests, send them, and inspect execution history.
This makes your saved knowledge useful right where you’re writing code: “Find my retry helper and use it here,” or “Save this solution as a TypeScript snippet.”
Less waiting with large libraries
In internal tests with synthetic libraries on an Apple M4 Pro:
First search fell from 13.8 to 1.9 seconds for 10,000 snippets, and from 4.4 to 0.9 seconds for 10,000 notes.
Startup with around 30,000 items took roughly 1.8–2.2 seconds, down from 4.3–4.9 seconds.
Retained search-process memory after searching 10,000 snippets and 10,000 notes dropped by 46%.
These are focused benchmark results, not guarantees for every library. Search figures measure query processing, and the memory reduction applies to the search process rather than the whole app.
Everyday improvements include draggable snippet fragment tabs, more consistent sidebar controls, and fixes for search state, navigation, and editor flicker.
Before upgrading
v6 uses Markdown Vault storage only. If you still have a SQLite library, migrate it through v5.12.0 first, using a separate, empty target directory and keeping a backup. Existing Markdown Vault users can continue using their vault. The migration guide covers the steps.
Thank you for supporting massCode
Your contributions help fund development, bug fixes, and maintenance while keeping massCode free and open source. If it has become part of your daily workflow, a one-time or recurring contribution helps support that work.