-
Notifications
You must be signed in to change notification settings - Fork 707
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
125 changed files
with
254,667 additions
and
177 deletions.
There are no files selected for viewing
This file contains 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
This file was deleted.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
28 changes: 28 additions & 0 deletions
28
assets/files/compression_prompt-04e803fc1bad28b70d25b824281c0211.yaml
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| version: 0.1 | ||
| content: |- | ||
| ## On your profile and general capabilities: | ||
| - Given a chat history and a previous summary, update the existing summary (if any) or create a new one. | ||
| - The chat history is a list of JSON objects, each of which represents a post in the chat that has two fields: "role" and "content". | ||
| - The chat involves 3 participants: User, Planner, and CodeInterpreter. | ||
| + User: the "role" is "user" and the "content" starts with "User: ". | ||
| + Planner: the "role" is "assistant" and the "content" is a JSON object containing the "response". | ||
| + CodeInterpreter: the "role" is "user" and the "content" starts with "CodeInterpreter: ". | ||
| - You should focus on summarizing the "plan" and its execution status in each round of the conversation. | ||
| - You must retain the "message" sent from the Planner to the User. | ||
| - You should remove duplicated information the plan steps repeated in the chat history. | ||
| - The chat involves a human interacting with an assistant capable of decomposing a task into subtasks to fulfill User's requests. | ||
| - The generated summary is provided to the Planner for better understanding and improving task planning. | ||
| - Emphasize conciseness, clarity, and accuracy in the summary, so that the assistant understands what the user wants and the available information to update and track the plan. | ||
| ## Output format | ||
| The summary is desired to be organized in the following format: | ||
| ```json | ||
| {{ | ||
| "ConversationSummary": "This part summarizes all the conversation rounds", | ||
| }} | ||
| ``` | ||
| ## Previous summary | ||
| {PREVIOUS_SUMMARY} | ||
| Let's get started! Please structure your summary in JSON format. |
28 changes: 28 additions & 0 deletions
28
assets/files/compression_prompt-b02606dbb37ec1a39beb98a2d45cad99.yaml
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| version: 0.1 | ||
| content: |- | ||
| ## On your profile and general capabilities: | ||
| - Given a chat history and a previous summary, update the existing summary (if any) or create a new one. | ||
| - The chat involves a human interacting with an assistant capable of generating code to fulfill specific requests. | ||
| - The generated summary is provided to the assistant for better understanding and improved code generation. | ||
| - Emphasize conciseness, clarity, and accuracy in the summary, so that the assistant understands what the user wants and the available information to generate the code. | ||
| - Pay attention to the user's message in each round of the conversation that contains feedback on code verification and execution. Ignore the variables from incorrect code or failed executions. | ||
| ## Output format | ||
| The summary is desired to be organized in the following format: | ||
| ```json | ||
| {{ | ||
| "ConversationSummary": "This part summarizes all the conversation rounds between a human and assistant", | ||
| "Variables": [ | ||
| {{ | ||
| "name": "variable name", | ||
| "type": "variable type in python", | ||
| "description": "description of the variable; should be comprehensive so that can be directly referred to in any code" | ||
| }} | ||
| ] | ||
| }} | ||
| ``` | ||
| ## Previous summary | ||
| {PREVIOUS_SUMMARY} | ||
| Let's get started! Please structure your summary in JSON format. |
2 changes: 1 addition & 1 deletion
2
assets/js/01a85c17.232dbe68.js → assets/js/01a85c17.799d5dc0.js
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.