You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Packages a complete .NET solution into a ZIP archive and uploads it to cloud storage. "+
850
-
"ONLY call when the user explicitly confirms they want to download. "+
851
-
"Include all files needed to run: .csproj with correct NuGet references (use Version=\"*\" for MaIN.NET/MaIN.Skills.* — never a guessed version number), Program.cs, and any supporting files. "+
852
-
"Do NOT call proactively.",
853
-
new
854
-
{
855
-
type="object",
856
-
properties=new
857
-
{
858
-
archiveName=new{type="string",description="ZIP filename, e.g. MyAgent.zip"},
859
-
files=new
860
-
{
861
-
type="array",
862
-
description="Files to include in the archive",
863
-
items=new
864
-
{
865
-
type="object",
866
-
properties=new
867
-
{
868
-
path=new{type="string",description="Relative path inside the zip, e.g. MyAgent/Program.cs"},
- MCP has 3 integration styles: direct prompt, agent pipeline step, RAG knowledge source
1256
1244
1257
-
TOOL ECONOMY: You have 7 tool slots. list_docs (1) → read app-template doc + maybe 1 more (2) → answer. Never read the same file twice. Propose artifact counts as 1 slot.
1245
+
TOOL ECONOMY: You have 10 tool slots. list_docs (1) → read app-template doc + maybe 1 more (2) → show_file × N files (N) → propose_artifact_generation (1) = done. Never read the same file twice.
1258
1246
1259
1247
TOOLS — use them every time, no improvising:
1260
1248
1. list_docs — discover what files exist
@@ -1348,17 +1336,17 @@ that text directly into agent.ProcessAsync($"...the user's request...\n\n{extrac
1348
1336
— NOT a type called "FileTypeFilter").
1349
1337
1350
1338
ARTIFACTS — MANDATORY ORDER, NO EXCEPTIONS:
1351
-
1. Write out EVERY file of the complete solution directly in your response TEXT first — minimum
1352
-
.csproj + Program.cs, each as its own fenced code block immediately preceded by a line
1353
-
"File: <path>". Nothing omitted, nothing summarized. THIS IS THE ONLY WAY THE USER SEES YOUR CODE.
1354
-
2. ONLY THEN, in that same response, may you call propose_artifact_generation as an optional
1355
-
convenience download. Calling it without first writing the code blocks in step 1 is a hard
1356
-
failure — a tool call is not a substitute for showing the code.
1357
-
3. Only propose when the solution is complete and runnable (has .csproj + Program.cs + runs with 'dotnet run').
1358
-
4. generate_artifact: ONLY when the user explicitly confirms they want the download. Package the full project.
1359
-
5. After generate_artifact succeeds, do NOT include the download URL in your text — the UI shows a download card. Just confirm it's ready.
1360
-
1361
-
RESPONSE RULE: ALWAYS write text in your response. When proposing an artifact, include a brief explanation of what you built. When generating an artifact, confirm it's ready in 1 sentence. Never return an empty text response.
1339
+
1. Call show_file once for EVERY file in the solution — minimum .csproj + Program.cs.
1340
+
This is the ONLY way the user sees your code. Do NOT write fenced code blocks in your
1341
+
text. Do NOT combine files or skip any file.
1342
+
2. After all show_file calls, write 1-2 sentences in your text describing what you built.
1343
+
3. Call propose_artifact_generation to offer the download. Only call when the solution
1344
+
is complete and runnable (has .csproj + Program.cs, runs with 'dotnet run').
1345
+
4. The UI packages the shown files into a ZIP when the user clicks download — you do NOT
1346
+
need to call any generate tool. Never confirm or mention downloading in your text.
1347
+
1348
+
RESPONSE RULE: ALWAYS write text in your response. Keep it to 1-3 sentences — the code is
1349
+
shown via show_file tiles, so your text is just the summary. Never return an empty text response.
0 commit comments