wcgw 2.1.1__tar.gz → 2.1.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of wcgw might be problematic. Click here for more details.
- {wcgw-2.1.1 → wcgw-2.1.2}/PKG-INFO +1 -1
- {wcgw-2.1.1 → wcgw-2.1.2}/gpt_instructions.txt +2 -1
- {wcgw-2.1.1 → wcgw-2.1.2}/pyproject.toml +1 -1
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/anthropic_client.py +4 -3
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/mcp_server/server.py +4 -3
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/openai_client.py +2 -1
- {wcgw-2.1.1 → wcgw-2.1.2}/uv.lock +1 -1
- {wcgw-2.1.1 → wcgw-2.1.2}/.github/workflows/python-publish.yml +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/.github/workflows/python-tests.yml +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/.github/workflows/python-types.yml +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/.gitignore +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/.python-version +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/.vscode/settings.json +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/README.md +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/gpt_action_json_schema.json +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/openai.md +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/__init__.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/__init__.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/__init__.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/__main__.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/cli.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/common.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/computer_use.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/diff-instructions.txt +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/mcp_server/Readme.md +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/mcp_server/__init__.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/openai_utils.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/sys_utils.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/client/tools.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/relay/serve.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/relay/static/privacy.txt +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/src/wcgw/types_.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/static/claude-ss.jpg +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/static/computer-use.jpg +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/static/example.jpg +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/static/rocket-icon.png +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/static/ss1.png +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/tests/test_basic.py +0 -0
- {wcgw-2.1.1 → wcgw-2.1.2}/tests/test_tools.py +0 -0
|
@@ -5,7 +5,8 @@ Instructions:
|
|
|
5
5
|
- You should use the provided bash execution, reading and writing file tools to complete objective.
|
|
6
6
|
- First understand about the project by getting the folder structure (ignoring .git, node_modules, venv, etc.)
|
|
7
7
|
- Always read relevant files before editing.
|
|
8
|
-
- Do not provide code snippets unless asked by the user, instead directly edit the code.
|
|
8
|
+
- Do not provide code snippets unless asked by the user, instead directly add/edit the code.
|
|
9
|
+
- Do not install new tools/packages before ensuring no such tools/package or an alternative already exists.
|
|
9
10
|
|
|
10
11
|
Instructions for `Initialize`:
|
|
11
12
|
- Always call this at the start of the conversation.
|
|
@@ -185,7 +185,7 @@ def loop(
|
|
|
185
185
|
- Send send_specials=["Enter"] to recheck status of a running program.
|
|
186
186
|
- Only one of send_text, send_specials, send_ascii should be provided.
|
|
187
187
|
- This returns within 5 seconds, for heavy programs keep checking status for upto 10 turns before asking user to continue checking again.
|
|
188
|
-
- Programs don't hang easily, so most likely explanation for no output is usually that the program is still running, and you need to check status again
|
|
188
|
+
- Programs don't hang easily, so most likely explanation for no output is usually that the program is still running, and you need to check status again using ["Enter"].
|
|
189
189
|
|
|
190
190
|
""",
|
|
191
191
|
),
|
|
@@ -246,7 +246,7 @@ def loop(
|
|
|
246
246
|
description="""
|
|
247
247
|
- Capture screenshot of the linux os on docker.
|
|
248
248
|
- All actions on UI using mouse and keyboard return within 0.5 seconds.
|
|
249
|
-
* So if you're doing something that takes longer for UI to update like heavy page loading, keep checking UI for update
|
|
249
|
+
* So if you're doing something that takes longer for UI to update like heavy page loading, keep checking UI for update using ScreenShot upto 10 turns.
|
|
250
250
|
* Notice for smallest of the loading icons to check if your action worked.
|
|
251
251
|
* After 10 turns of no change, ask user for permission to keep checking.
|
|
252
252
|
* If you don't notice even slightest of the change, it's likely you clicked on the wrong place.
|
|
@@ -287,7 +287,8 @@ Instructions:
|
|
|
287
287
|
- You should use the provided bash execution, reading and writing file tools to complete objective.
|
|
288
288
|
- First understand about the project by getting the folder structure (ignoring .git, node_modules, venv, etc.)
|
|
289
289
|
- Always read relevant files before editing.
|
|
290
|
-
- Do not provide code snippets unless asked by the user, instead directly edit the code.
|
|
290
|
+
- Do not provide code snippets unless asked by the user, instead directly add/edit the code.
|
|
291
|
+
- Do not install new tools/packages before ensuring no such tools/package or an alternative already exists.
|
|
291
292
|
|
|
292
293
|
System information:
|
|
293
294
|
- System: {uname_sysname}
|
|
@@ -105,7 +105,7 @@ async def handle_list_tools() -> list[types.Tool]:
|
|
|
105
105
|
- Send send_specials=["Enter"] to recheck status of a running program.
|
|
106
106
|
- Only one of send_text, send_specials, send_ascii should be provided.
|
|
107
107
|
- This returns within 3 seconds, for heavy programs keep checking status for upto 10 turns before asking user to continue checking again.
|
|
108
|
-
- Programs don't hang easily, so most likely explanation for no output is usually that the program is still running, and you need to check status again
|
|
108
|
+
- Programs don't hang easily, so most likely explanation for no output is usually that the program is still running, and you need to check status again using ["Enter"].
|
|
109
109
|
""",
|
|
110
110
|
),
|
|
111
111
|
ToolParam(
|
|
@@ -165,7 +165,7 @@ async def handle_list_tools() -> list[types.Tool]:
|
|
|
165
165
|
description="""
|
|
166
166
|
- Capture screenshot of the linux os on docker.
|
|
167
167
|
- All actions on UI using mouse and keyboard return within 0.5 seconds.
|
|
168
|
-
* So if you're doing something that takes longer for UI to update like heavy page loading, keep checking UI for update
|
|
168
|
+
* So if you're doing something that takes longer for UI to update like heavy page loading, keep checking UI for update using ScreenShot upto 10 turns.
|
|
169
169
|
* Notice for smallest of the loading icons to check if your action worked.
|
|
170
170
|
* After 10 turns of no change, ask user for permission to keep checking.
|
|
171
171
|
* If you don't notice even slightest of the change, it's likely you clicked on the wrong place.
|
|
@@ -243,7 +243,8 @@ async def handle_call_tool(
|
|
|
243
243
|
- You should use the provided bash execution, reading and writing file tools to complete objective.
|
|
244
244
|
- First understand about the project by getting the folder structure (ignoring .git, node_modules, venv, etc.)
|
|
245
245
|
- Always read relevant files before editing.
|
|
246
|
-
- Do not provide code snippets unless asked by the user, instead directly edit the code.
|
|
246
|
+
- Do not provide code snippets unless asked by the user, instead directly add/edit the code.
|
|
247
|
+
- Do not install new tools/packages before ensuring no such tools/package or an alternative already exists.
|
|
247
248
|
|
|
248
249
|
|
|
249
250
|
Additional instructions:
|
|
@@ -228,7 +228,8 @@ Instructions:
|
|
|
228
228
|
- You should use the provided bash execution, reading and writing file tools to complete objective.
|
|
229
229
|
- First understand about the project by getting the folder structure (ignoring .git, node_modules, venv, etc.)
|
|
230
230
|
- Always read relevant files before editing.
|
|
231
|
-
- Do not provide code snippets unless asked by the user, instead directly edit the code.
|
|
231
|
+
- Do not provide code snippets unless asked by the user, instead directly add/edit the code.
|
|
232
|
+
- Do not install new tools/packages before ensuring no such tools/package or an alternative already exists.
|
|
232
233
|
|
|
233
234
|
System information:
|
|
234
235
|
- System: {uname_sysname}
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|