A free, open-source developer workspace. Snippets, notes, HTTP requests, calculations, and dev tools in one local-first app.
Repo massCodeIO/massCode, read from GitHub 5 h ago. massCodeIO has not joined Take My Repo.
The Command Palette can now find records by meaning, not only by the words they contain. It works across languages too: дорожная карта (Russian for "roadmap") finds a note named Orbit roadmap. Results by words appear as you type, and results by meaning are added below them after a short pause without reordering what is already shown. Each result shows why it was found (Matches the name, Has your words, By meaning, Words and meaning) and a short excerpt with matched words highlighted. Weaker matches are grouped under Possibly related, and create actions stay pinned at the bottom of the palette.
Run Turn on semantic search from the Command Palette to download the built-in model (~210 MB). It runs offline, so your records and queries stay on this computer. massCode indexes snippets, notes and HTTP requests in the background and shows progress in the space rail. The index is not synced with your vault. The AI assistant uses the same search when it looks for records in the vault. Semantic search is not available on Intel Macs.
The MCP server can now edit and organize your vault, not only read and create items. New tools let an agent update notes and snippets, move items to Trash and restore them, create, rename, move and delete folders, move items between folders, list the folder structure and read note backlinks. create_note and create_snippet now accept a folder and tags.
Changes to existing items require the new Allow MCP to modify existing items preference. It is off by default for new users and turned on automatically if you already had MCP enabled. Edits are checked against the current revision of an item, so an agent cannot overwrite changes it has not seen. MCP never deletes items permanently and deletes only empty folders.
Full Changelog: v6.2.1...v6.3.1
This release replaces v6.2.0, which was not published by the maintainer. On October 11, 2026, an attacker used a leaked GitHub token to publish a malicious v6.2.0 build that collected credentials, browser data and crypto wallets. It was available from 2026-10-11 20:35 UTC until about 2026-10-12 00:05 UTC.
v6.2.1 is built from the restored code and contains no other changes since v6.1.0. If you are on v6.2.0, updating to this version removes the malicious build.
If you ran v6.2.0, treat every secret on that machine as compromised: rotate SSH keys, GitHub, npm and cloud tokens and saved browser passwords, and move funds from any crypto wallet on that machine. You can check whether the malware ran by looking for the .runtime file in the massCode data folder. Details and instructions: #978.
v6.1.0 and earlier are not affected.
Full Changelog: v6.1.0...v6.2.1
The AI assistant now supports OpenRouter. Enter your OpenRouter API key to use models from many vendors through a single account, with requests billed to your OpenRouter balance. The model list includes only models with tool calling support, and model IDs use the vendor/model format, for example anthropic/claude-sonnet-5.5.
See the AI Assistant guide for setup.
Full Changelog: v6.0.0...v6.1.0
The built-in AI assistant carries out tasks across Code, Notes, and HTTP. Ask it to edit and format snippets, organize notes, update tasks, or run API workflows. Attach an open record or selected text, or let it find the relevant records in your vault. One conversation stays with you as you switch spaces.
You can combine related steps in a single request:
Requested edits apply directly. Ask for a preview to inspect changes before applying them. Sending HTTP requests and running collections require confirmation; changes to an HTTP draft still need Save. The assistant waits for action results before continuing dependent steps. You can answer its questions, adjust an active task, queue another request, or stop it. Task Undo reverses supported changes while preserving unrelated manual edits; it cannot reverse network requests, exported files or permanent deletion.
Connect your own OpenAI, Anthropic, Google Gemini, DeepSeek, Mistral, or xAI account, or use a local model through Ollama or LM Studio. Actions require a model with tool calling support. Cloud providers receive the context used for the task and bill through your API account. For local processing, use a model running on your computer.
See the AI Assistant guide for setup and examples.
Connect external coding agents to your massCode vault through Model Context Protocol. Search and read snippets, notes, and HTTP requests, or save a solution as a new snippet or note without leaving your coding workflow.
Agents can also create HTTP collections and requests, update or move saved requests, preview their settings, send them using the active environment, and inspect saved execution history. Enable API integrations and MCP access in Preferences, then connect your client with an integration token. MCP is off by default and runs locally while massCode is open.
See the MCP guide for setup and supported tools.
Searching large libraries and filtering HTTP collections now take less time. Here are the results with 10,000 items in each space.
| Action | Library size | Before | After | Time reduction |
|---|---|---|---|---|
| First search in Code | 10,000 snippets | 13,792 ms | 1,947 ms | 85.88% |
| First search in Notes | 10,000 notes | 4,424 ms | 876 ms | 80.20% |
| Search after editing a snippet¹ | 10,000 snippets | 12,376 ms | 1.62 ms | 99.99% |
| Search after editing a note¹ | 10,000 notes | 4,434 ms | 0.75 ms | 99.98% |
| Filter HTTP requests by an exact name | 10,000 requests | 22,110–24,014 ms | 7–13 ms | 99.94–99.97% |
| Clear the filter to show all HTTP requests | 10,000 requests | 18,755 ms | 11–17 ms | 99.91–99.94% |
¹ Search time after an edit has finished saving; saving time is excluded. First-search results include preparing the search index.
Startup checks and initial search indexing now run in smaller batches. You can switch spaces while the first search is being prepared, or change your query without an older result replacing the new one. Notes also skips unnecessary startup scans when there are no legacy attachments to migrate.
In focused tests with 10,000 items per space, the longest measured processing pauses during first-search preparation fell from 3,224 to 33 ms in Code and from 673 to 11 ms in Notes. These measure interruptions to the app's ability to handle other work, not the total search time or input-to-screen delay.
Startup was measured again using the build from before the optimization work and the current build, with identical saved items and library copies. Each value is the median of three launches.
| Library size | Opened space | Before | After | Time reduction |
|---|---|---|---|---|
| 3,000 items (1,000 per space) | Code | 1.24 s | 1.07 s | 13.8% |
| 3,000 items (1,000 per space) | Notes | 1.26 s | 1.09 s | 13.9% |
| 3,000 items (1,000 per space) | HTTP | 1.41 s | 1.12 s | 20.8% |
| ~30,000 items (10,000 per space) | Code | 4.33 s | 1.83 s | 57.7% |
| ~30,000 items (10,000 per space) | Notes | 4.44 s | 1.91 s | 57.0% |
| ~30,000 items (10,000 per space) | HTTP | 4.86 s | 2.15 s | 55.9% |
With 10,000 snippets and 10,000 notes, retained search-process JavaScript memory fell from 1,036 to 560 MiB, a 46% reduction in a focused before/after test. This measures memory after searching both spaces, not the total memory of the entire app.
MacBook Pro with Apple M4 Pro (12-core CPU), 24 GB unified memory, macOS 27.0 (26A428), Electron 34.1.1. Production benchmark builds on Apple Silicon.
Internal tests used synthetic libraries on the machine above, without clearing the OS file cache. Search and HTTP figures compare initial and latest recorded results from separate sessions; responsiveness and memory figures come from focused before/after tests of those improvements. Search timings use three-run medians; HTTP ranges cover a small number of interactions. Memory was measured after garbage collection in one diagnostic pair.
Search timings measure query processing, and HTTP timings measure list updates, not full input-to-screen latency. Startup compares the original and current builds across 36 alternating launches, with a fresh copy of the same test profile and vault and an equally warmed file cache for each run. Timings run from application initialization to the selected item's open event, not actual screen paint. The larger vault includes four additional HTTP test records (30,004 total). The final Notes search includes loading content that the original version loaded in advance. Results depend on library content and hardware.
v6 uses Markdown Vault storage only. SQLite support and the built-in legacy migration have been removed. Existing Markdown Vault users can continue using their vault.
If your library is still a v4 massCode.db, back it up and migrate it with massCode v5.12.0 before opening it in v6. Use a separate, empty target directory: the v5 migration replaces Code content in the selected vault. Verify your migrated folders, snippets, and tags, then select that vault in v6.
For a v3 db.json library, first convert it with v4.7.1, then migrate through v5.12.0. See the storage and migration guide for the full steps.
Enter.Cmd+L on macOS or Ctrl+L on Windows and Linux to focus the AI assistant, or close it when the chat already has focus.Full Changelog: v5.12.0...v6.0.0
Plan notes, snippets, and HTTP requests directly from the internal link picker in Notes. Insert a placeholder for an item you intend to create and keep writing without interrupting your work.
When you are ready, hold Cmd on macOS or Ctrl on Windows/Linux and click the placeholder to create the item and open it in Notes, Code, or HTTP. The placeholder becomes a regular link, and Back takes you to your note.
The new Note inspector brings Outline, Links, and Annotations into a resizable panel beside your note. Navigate headings or drag entire sections to reorder and nest them in Raw and Live Preview.
Inspect linked items, external addresses, planned placeholders, and missing targets in one place. Filter links by status or space, jump to their occurrences, and find Todo, Note, Important, and Warning callouts as you write.
Back and Forward now share a session history across Notes, Code, and HTTP. Items opened from lists, search, Command Palette, Recent, and internal links all become part of the same navigation path.
Revisit items across spaces using the editor buttons or History menu. Returning to a note restores its scroll position, and deleted items are skipped.
Full Changelog: v5.11.0...v5.12.0
HTTP gets a redesigned workspace with searchable, resizable sidebar sections, collection and folder dashboards, and independently controlled panels. Collections and folders now provide inherited headers, authentication, variables, scripts, and checks, so you can configure common API settings once and reuse them across requests.
Request content now uses explicit Save instead of autosave. Send runs the current draft without saving it, and navigating away prompts you to save or discard changes. Request names still save automatically. A new Binary body mode lets you send a local file as the complete request body.
Check response status, timing, headers, and JSON values with no-code assertions, or write pre-request scripts and JavaScript tests. Extract response values into temporary variables to pass tokens and IDs between requests. The Variables inspector shows inherited defaults, environment values, overrides, and unresolved references in one place.
Run entire collections or folders in sequence with the Runner. Reorder steps, choose whether to continue on failure, and inspect each request's assertions, extraction, and test results. Each run uses isolated temporary variables, keeping your saved environment and manual Session values intact.
Send GraphQL queries and mutations with dedicated document and variables editors, syntax validation, and operation selection. GraphQL works with scripts, assertions, extraction, and the Runner, which recognizes GraphQL errors even when the server returns HTTP 200.
Connect to WebSocket endpoints, configure headers and authentication, exchange text or JSON messages, and inspect incoming and outgoing traffic. Save connection settings and message drafts, and reuse environment and Session variables across servers.
Inspect network traffic and script logs in the new Console, detach it into a separate window, or use multiple built-in Terminal sessions alongside your requests. Request History retains request and response snapshots for inspecting earlier sends, with configurable retention and redaction of known secrets and credential-like fields.
A persistent cookie jar includes search, inline editing, and raw Set-Cookie editing. Global transport defaults and per-request overrides cover HTTP/2, timeouts, response size limits, TLS verification, URL encoding, and redirects. Bulk text editing makes key-value tables faster to fill and update.
Expanded Postman import preserves collection and folder scopes, shared settings, scripts, and supported bodies, including GraphQL and binary file references. Supported Postman and Bruno scripts are adapted to the mc API, and supported Bruno assertions become response checks. Import previews flag compatibility issues before you run the imported workflow.
Generate request code from the current draft with 29 generators across 20 language and runtime targets, including Node.js, Python, Swift, cURL, HTTPie, and Wget. Previews account for inherited settings and applicable cookies, with control over variable interpolation and masking of secret and Session values.
Search within the current snippet in Code or the current note in Notes. A dedicated search panel highlights matches, shows the match count, and lets you move between results with buttons or the keyboard.
Full Changelog: v5.10.0...v5.11.0