gpterm 0.6.1 → 0.6.3
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.
- checksums.yaml +4 -4
- data/README.md +1 -1
- data/config/prompts.yml +6 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 0a21b914e291d4d6a0310355fb6412d746368437335af64bf7e9746ac6016983
|
|
4
|
+
data.tar.gz: db7ea2ddae831143d371dfc9ee316f601d757994cb46bf0e5247357d8b73dba6
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: a13a1d835c3a807cee3c35379d60462c13426eaf379487c41129583cdb06631f215d044d1cd9cb89fe0c5112a57fefa9fbbfea2edeb31930d2d6f2cfc0e64591
|
|
7
|
+
data.tar.gz: c80160ccddc42a5292c951fa2b7aa8056abff75a2f8bb972dfca2318ac5211b23619dd2b52bacb0e8a9b72ff2033e60f6eb1676bf0cf559bec5e33f069cc387d
|
data/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
**WARNING:** `gpterm` has very few guardrails. If used indiscriminately, it can wipe your entire system or leak information.
|
|
4
4
|
|
|
5
|
-
|
|
6
6
|
|
|
7
7
|
`gpterm` is a powerful, flexible and dangerous command-line tool designed to help you generate commands for your terminal using OpenAI's Chat Completions. It will not execute commands without your consent, but please do check which commands it is presenting before you let it execute them. Like so:
|
|
8
8
|
|
data/config/prompts.yml
CHANGED
|
@@ -20,6 +20,8 @@ system: |
|
|
|
20
20
|
- The response MUST keep in mind that each line of the response will be executed in the shell in a subshell, and the output of each command will be captured
|
|
21
21
|
- The commands MUST NOT contain any placeholders which the user is expected to replace with their own values
|
|
22
22
|
- If a command needs to be run in another directory, the command to change directory MUST be part of that command. To execute a command in a different directory, you must chain the cd command with the command you want to run, like so: `cd /path/to/directory && command`. You will need to do the same for any command that requires a different working directory, even if you have used cd in a previous command
|
|
23
|
+
- The commands MUST NOT involve any multi-line strings, heredocs, loops, conditionals or anything which necessitates running multiple lines in a single command. So no << EOF or anything like that
|
|
24
|
+
- Each command MUST BE executable on a single line in the shell
|
|
23
25
|
|
|
24
26
|
When responding with an INSTRUCTION CODE indicating that no commands can be generated or are necessary:
|
|
25
27
|
- The response MUST start with $$ and end with $$, and be a single line with only alphanumeric characters and underscores
|
|
@@ -38,7 +40,7 @@ system: |
|
|
|
38
40
|
- The response MUST start with $$ and end with $$, and be a single line with only alphanumeric characters and underscores
|
|
39
41
|
- The response MUST match one of the codes provided in the prompt
|
|
40
42
|
info_gathering: |
|
|
41
|
-
Your FIRST response should be a list of commands that will be automatically executed to gather more information about the user's system. For this response,
|
|
43
|
+
Your FIRST response should be a list of commands that will be automatically executed to gather more information about the user's system. For this response, additional rules apply:
|
|
42
44
|
- The response MUST NOT contain any plain language instructions, and must not start with or end with backticks to indicate code.
|
|
43
45
|
- The commands MUST NOT make any changes to the user's system.
|
|
44
46
|
- The commands MUST NOT make any changes to any files on the user's system.
|
|
@@ -49,6 +51,9 @@ info_gathering: |
|
|
|
49
51
|
- The commands MAY gather information about the user's system, such as the version of a software package, or the contents of a file.
|
|
50
52
|
- The commands CAN pipe their output into other commands.
|
|
51
53
|
- The commands SHOULD tend to gather more verbose information INSTEAD OF more concise information.
|
|
54
|
+
- The commands in this response MUT NOT accomplish the user's goal.
|
|
55
|
+
- The commands in this should ONLY be used to collect more information
|
|
56
|
+
- If you already know the command to accomplish the goal and do not need to collect information, you MUST respond with the $$no_gathering_needed$$ INSTRUCTION CODE.
|
|
52
57
|
|
|
53
58
|
This will help you to provide a more accurate response to the user's goal.
|
|
54
59
|
|