Replies: 1 comment
-
|
Hi @Wolfe-Jam , I don't think that Claude Desktop support is monitoring these discussions - I would take a look at the support options here instead: https://support.claude.com/en/articles/9015913-how-to-get-support |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Discussion Topic
Hey Anthropic MCP team,
Flagging a model behavior issue: When users request file creation, Claude Desktop
generates fake files with fabricated content in container paths and offers
downloads, rather than calling available MCP tools that would create accurate
files in the user's actual project directory.
What's happening:
offers download
context)
correct location)
Impact:
Users unknowingly operate with fabricated project context. Desktop creates
convincingly wrong output instead of using MCP to generate correct output from
actual project analysis.
Core question:
Why is Claude Desktop behaving like Claude.ai? Users install Desktop specifically
for MCP integration. If the model defaults to web behavior (container files,
fabricated content), what's the differentiator?
Workaround:
We've built Projects convention path resolution and guide tools to work around
this, but ideally this should be a global model fix benefiting all MCP servers.
Related issues: #2410, #1016, #1520
Ask:
Could the model be prompted to default to MCP tools for file operations when
available? This would leverage Desktop's core differentiator and prevent fake
file generation across the MCP ecosystem.
Happy to provide session transcripts or fake vs. real file comparisons if
helpful.
Thanks for building MCP!
Beta Was this translation helpful? Give feedback.
All reactions