docs: RELEASE-NOTES.md for v1.0.4 (MCP support + live step limit) - #59
Merged
Conversation
Rewrites the rolling release notes for v1.0.4 — MCP tool support and its security model (SHA-256 launch-trust gate, per-call approval, autopilot never silently running third-party tools), the 'AI: Manage MCP Servers…' command, /mcp visibility, and the autopilot live-step-limit fix (#54). Verified against docs/MCP.md and the shipped surfaces; full extension suite 27/0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the rolling release notes to document LevelCode v1.0.4, focusing on the newly shipped MCP tool support (including its security/trust model and user-facing surfaces) and the autopilot live step-limit behavior.
Changes:
- Rewrites
RELEASE-NOTES.mdfor v1.0.4 with MCP support highlights, security model details, and UI entry points (/mcp, Manage MCP Servers). - Adds/updates test coverage notes and the full changelog compare link for v1.0.4.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Spawning an MCP server is at least as dangerous as running a shell command, so every edge is gated: | ||
|
|
||
| ### A slimmer footer | ||
| - **A launch gate for repo servers.** A `.levelcode/mcp.json` server asks before it ever runs, showing you the **literal command, arguments, and environment** — no summarizing. Approve once and it's remembered, but trust is bound to a **SHA-256 fingerprint of exactly what would run**: change the command, an argument, *or* an env var and it asks again — so a repo can't get `npx …server-filesystem` approved and then quietly swap in `curl … | sh` under the same name. With no window to ask in (a headless or test context) it **fails closed** and simply doesn't start. |
|
|
||
| A new **`AI: Manage MCP Servers…`** command (and a link at the foot of `/mcp`) lets you: | ||
|
|
||
| - **Add or remove a server** through a prompt instead of hand-editing settings — it writes your global settings only, never a repo's, so adding one can never weaken the launch gate above. The arguments box takes a real command line and splits it quote-aware, so `-y @modelcontextprotocol/server-filesystem "/Users/me/My Documents"` stays one path. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewrites the rolling
RELEASE-NOTES.mdfor v1.0.4 — the release that adds MCP tool support (with its security model) plus the autopilot live-step-limit fix.Highlights documented
server__toolnamespacing; two trust tiers (mcp.serversstarts, a repo's.levelcode/mcp.jsonnever auto-starts).AI: Manage MCP Servers…— add/remove (global tier only), revoke trust, and thecommand changed — needs approvalstale-approval wording./mcpvisibility + the new MCP-tools line in the context meter.Notes
docs/MCP.mdand the shipped surfaces (extension.js,mcpConfig.js,chat.html,package.json).compare/v1.0.3...v1.0.4link (and a GitHub Release) needs thev1.0.4tag to be cut — the notes describe exactly what's merged ondevelopsince v1.0.3.🤖 Generated with Claude Code