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
Copy file name to clipboardExpand all lines: projects/code_genesis/refine.yaml
+8-4Lines changed: 8 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ generation_config:
10
10
top_k: 20
11
11
max_tokens: 64000
12
12
extra_body:
13
+
enable_thinking: false
13
14
dashscope_extend_params:
14
15
provider: b
15
16
@@ -48,7 +49,6 @@ prompt:
48
49
49
50
3. Use your tools effectively
50
51
* Use `read_file` to read the original file. When using `read_file`, specify `start_line` and `end_line` to reduce token usage
51
-
* When modifying files, prefer `edit_file` for partial edits; if you must rewrite an entire file, use `write_file`
52
52
* If an HTTP API is unclear, use `workflow/api_search` to locate the implementation
53
53
* Use `search_file_content` to search the project for keywords you care about
54
54
* Shell commands must not use system directories (except `/dev/null`)
@@ -58,11 +58,12 @@ prompt:
58
58
* Check available tools by looking for tools prefixed with `edgeone-pages-mcp`
59
59
60
60
Your workflow:
61
-
* You need to create a workspace_dir in the current working directory, and move necessary materials to the workspace_dir in the current working directory, filtering out unnecessary files like node_modules, dist, build, etc.
62
-
* Compress the workspace_dir into a zip file and name it workspace_dir.zip
61
+
* The workspace_dir mentioned in the context is your current working directory (where all generated files are located)
62
+
* You need to create a subdirectory called "workspace" inside workspace_dir, and copy necessary materials to it, filtering out unnecessary files like node_modules, dist, build, .npm-cache, etc.
63
+
* Compress the workspace subdirectory into a zip file and name it workspace.zip in the workspace_dir
63
64
* Once the project is working, use the EdgeOne Pages MCP tools to deploy it
64
65
* Follow the deployment documentation provided in the user message
65
-
* Upload the workspace_dir.zip to EdgeOne Pages and deploy it
66
+
* When calling the deployment tool, first use the shell command `pwd` to get the current working directory path, then use "<current_path>/workspace.zip" as the builtFolderPath parameter
66
67
67
68
5. If everything is OK, you may exit
68
69
* Ignore warnings like unused variables; they don't affect runtime behavior
0 commit comments