fix: serve agent instructions via MCP manifest#24
Open
nlang wants to merge 1 commit intoForLoopCodes:mainfrom
Open
fix: serve agent instructions via MCP manifest#24nlang wants to merge 1 commit intoForLoopCodes:mainfrom
nlang wants to merge 1 commit intoForLoopCodes:mainfrom
Conversation
|
@nlang is attempting to deploy a commit to the ForLoopCodes' projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Problem
Agent instructions were served as an MCP Resource fetched from Vercel on demand.
Clients that don't auto-read Resources (e.g. Claude Code) never saw them.
The
instructionsfield in the server manifest is auto-loaded by clients on connect —no explicit Resource read needed.
Changes
agent-instructions.md(new file)Agent-focused workflow guidance: when to use which tool, execution rules, anti-patterns.
Intentionally excludes contributor/architecture docs and formatting conventions that
belong in INSTRUCTIONS.md, not in the agent's context.
src/index.tsagent-instructions.mdat startup viaimport.meta.url-based path resolutionnpx, global install, local install, and directnode build/index.jsinstructionsin McpServer optionsThe existing Resource endpoint stays — clients that do read Resources still get them.