interintel 1.0.0
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.
- package/LICENSE +201 -0
- package/README.md +39 -0
- package/functions/chat-functions.js +14 -0
- package/functions/file-functions.js +84 -0
- package/functions/handleWriteFile.js +33 -0
- package/functions/openai-functions.js +16 -0
- package/index.js +107 -0
- package/inter-intel/training/multi-step/filesystem.spec.ts +18 -0
- package/inter-intel/training/multi-step/uploading.spec.ts +25 -0
- package/inter-intel/training/reference.txt +14 -0
- package/inter-intel/training/training/training.txt +13 -0
- package/inter-intel.config.js +9 -0
- package/package.json +35 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
## INTER-INTEL
|
|
2
|
+
|
|
3
|
+
The application `inter-intel` is a command line interface (CLI) application implemented in Node.js. It essentially is an interactive communication tool between the user and an AI model, only GPTs for now.
|
|
4
|
+
|
|
5
|
+
Here's a brief overview of the main functionalities, as contained in the index.js file:
|
|
6
|
+
|
|
7
|
+
- The application starts an interactive session with the user. It does this by invoking the readline module, which reads user inputs line by line from the terminal.
|
|
8
|
+
|
|
9
|
+
-- node index.js will start the app
|
|
10
|
+
|
|
11
|
+
- The OpenAI's API is accessed using API keys, and the version of AI being used is specified via a config.
|
|
12
|
+
|
|
13
|
+
### //writeFile
|
|
14
|
+
- If a user types '//writefile', the application prompts the user to provide a name for the file and then a prompt for the AI. It then automatically generates some text (by communicating with OpenAI's GPT-3 model), writes this to a file and stores it in the application's directory.
|
|
15
|
+
|
|
16
|
+
### //readRefs
|
|
17
|
+
- If a user writes '//readRefs', the application reads the content of the specified files in the inter-intel.config.js (in the current implementation) and uses this as part of the conversation with the AI.
|
|
18
|
+
- So as you work on your project and files change or you move to other parts of the code base you can adjust where inter-intel points and what is referenced by AI conversation.
|
|
19
|
+
|
|
20
|
+
### everything else
|
|
21
|
+
- For all user inputs outside of these special keywords, the chat conversation is simply updated with the user's message and a call is made to the OpenAI API to generate the AI's response. This is then displayed on the console.
|
|
22
|
+
|
|
23
|
+
The application relies heavily on async-await pattern for handling the asynchronicity associated with reading user inputs and waiting for responses from the OpenAI 'aiChatCompletion' function.
|
|
24
|
+
|
|
25
|
+
Keep in mind that this is a high level overview and each functionality has its own level of implementation detail.
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
File Structure
|
|
29
|
+
|
|
30
|
+
project/
|
|
31
|
+
├── functions/
|
|
32
|
+
│ ├── chat-functions.js
|
|
33
|
+
│ ├── file-functions.js
|
|
34
|
+
│ ├── openai-functions.js
|
|
35
|
+
│ ├── messageUtils.js
|
|
36
|
+
│ ├── writeFileHandler.js
|
|
37
|
+
│ └── readRefsHandler.js
|
|
38
|
+
├── inter-intel.config.js
|
|
39
|
+
└── index.js
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
const fs = require('fs');
|
|
2
|
+
const path = require('path');
|
|
3
|
+
|
|
4
|
+
async function askQuestion(rl, prompt) {
|
|
5
|
+
return new Promise((resolve) => {
|
|
6
|
+
rl.question(prompt.blue, (input) => {
|
|
7
|
+
resolve(input);
|
|
8
|
+
});
|
|
9
|
+
});
|
|
10
|
+
}
|
|
11
|
+
|
|
12
|
+
module.exports = {
|
|
13
|
+
askQuestion,
|
|
14
|
+
}
|
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
const fs = require('fs');
|
|
2
|
+
const path = require('path');
|
|
3
|
+
|
|
4
|
+
// READING FOR INITAL REFERENCE
|
|
5
|
+
function readSpecificFiles(filePaths) {
|
|
6
|
+
const configFilePath = path.join(__dirname, '../inter-intel.config.js');
|
|
7
|
+
|
|
8
|
+
try {
|
|
9
|
+
// Read the content of the config file
|
|
10
|
+
const configContent = fs.readFileSync(configFilePath, 'utf8');
|
|
11
|
+
// Parse the config file content as JavaScript
|
|
12
|
+
const config = eval(configContent);
|
|
13
|
+
// Extract the file paths from the config object
|
|
14
|
+
const filePaths = config.filePaths;
|
|
15
|
+
|
|
16
|
+
let allContent = '';
|
|
17
|
+
|
|
18
|
+
filePaths.forEach((filePath) => {
|
|
19
|
+
try {
|
|
20
|
+
// Construct the absolute path
|
|
21
|
+
const absolutePath = path.resolve(filePath);
|
|
22
|
+
|
|
23
|
+
// Read the file content and append it to allContent
|
|
24
|
+
allContent += fs.readFileSync(absolutePath, 'utf8') + '\n';
|
|
25
|
+
} catch (error) {
|
|
26
|
+
console.error(`Error reading file ${filePath}: ${error.message}`.bgRed);
|
|
27
|
+
}
|
|
28
|
+
});
|
|
29
|
+
|
|
30
|
+
// Add console.log statements to communicate to the user
|
|
31
|
+
console.log(`AI sent reference files:`.yellow, `${logFileNames(filePaths)}`.yellow);
|
|
32
|
+
return allContent;
|
|
33
|
+
} catch (error) {
|
|
34
|
+
console.error(`Error reading config file: ${error.message}`.bgRed);
|
|
35
|
+
return '';
|
|
36
|
+
}
|
|
37
|
+
}
|
|
38
|
+
|
|
39
|
+
function writeFileFromPrompt(promptFileName, contentToWrite, baseDir) {
|
|
40
|
+
try {
|
|
41
|
+
|
|
42
|
+
if (!promptFileName.includes('.')) {
|
|
43
|
+
throw new Error("Invalid file name. Please include a file name with an extension (e.g., 'output.txt').");
|
|
44
|
+
}
|
|
45
|
+
|
|
46
|
+
const fullPath = path.join(baseDir, `../inter-intel/session-samples/${promptFileName}`);
|
|
47
|
+
const directoryPath = path.dirname(fullPath);
|
|
48
|
+
|
|
49
|
+
if (!fs.existsSync(directoryPath)) {
|
|
50
|
+
fs.mkdirSync(directoryPath, { recursive: true });
|
|
51
|
+
}
|
|
52
|
+
|
|
53
|
+
fs.writeFileSync(fullPath, contentToWrite + '\n');
|
|
54
|
+
console.log(`Content written to ${fullPath}`.yellow);
|
|
55
|
+
return true;
|
|
56
|
+
|
|
57
|
+
} catch (error) {
|
|
58
|
+
console.error(`Error writing file: ${error.message}`.bgRed);
|
|
59
|
+
return false;
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
|
|
63
|
+
// LOG FILE NAMES
|
|
64
|
+
function logFileNames(filePaths) {
|
|
65
|
+
let fileNames = [];
|
|
66
|
+
|
|
67
|
+
console.log("")
|
|
68
|
+
console.log(`System message`.bgYellow + `: `.yellow);
|
|
69
|
+
filePaths.forEach((filePath) => {
|
|
70
|
+
const fileName = path.basename(filePath);
|
|
71
|
+
fileNames.push(fileName); // Add the file name to the array
|
|
72
|
+
});
|
|
73
|
+
|
|
74
|
+
return fileNames; // Return the array of file names
|
|
75
|
+
}
|
|
76
|
+
|
|
77
|
+
function appendToFile(filePath, data) {
|
|
78
|
+
fs.appendFileSync(filePath, data + '\n');
|
|
79
|
+
}
|
|
80
|
+
|
|
81
|
+
// Export the function and the array
|
|
82
|
+
module.exports = {
|
|
83
|
+
readSpecificFiles, writeFileFromPrompt
|
|
84
|
+
};
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
const { aiChatCompletion } = require('./openai-functions.js');
|
|
2
|
+
const { writeFileFromPrompt } = require('./file-functions.js');
|
|
3
|
+
|
|
4
|
+
async function handleWriteFile(openai, config, messages, currentState, userInput, promptFileName) {
|
|
5
|
+
let contentToWrite = '';
|
|
6
|
+
|
|
7
|
+
if (currentState === null) {
|
|
8
|
+
currentState = 'awaitingFileName';
|
|
9
|
+
return { currentState, messages, promptFileName, response: 'Please provide a name for the session file:' };
|
|
10
|
+
} else if (currentState === 'awaitingFileName') {
|
|
11
|
+
promptFileName = userInput;
|
|
12
|
+
currentState = 'awaitingGPTPrompt';
|
|
13
|
+
return { currentState, messages, promptFileName, response: 'Please provide a prompt for the AI:' };
|
|
14
|
+
} else if (currentState === 'awaitingGPTPrompt') {
|
|
15
|
+
const promptForGPT = userInput;
|
|
16
|
+
try {
|
|
17
|
+
let gptResponse = await aiChatCompletion(openai, [{ role: 'user', content: promptForGPT }], config.aiVersion);
|
|
18
|
+
contentToWrite = gptResponse.choices[0].message.content;
|
|
19
|
+
await writeFileFromPrompt(promptFileName, contentToWrite, __dirname); // Assuming this function handles file writing
|
|
20
|
+
|
|
21
|
+
currentState = null; // Reset state after completing the operation
|
|
22
|
+
return { currentState, messages, promptFileName, contentToWrite, response: `Content written to ${promptFileName}`.yellow };
|
|
23
|
+
} catch (error) {
|
|
24
|
+
console.error('Error in handleWriteFile:', error);
|
|
25
|
+
return { currentState, messages, promptFileName, contentToWrite, response: 'An error occurred while writing the file.' };
|
|
26
|
+
}
|
|
27
|
+
}
|
|
28
|
+
|
|
29
|
+
// Return default state if none of the conditions are met
|
|
30
|
+
return { currentState, messages, promptFileName, contentToWrite, response: '' };
|
|
31
|
+
}
|
|
32
|
+
|
|
33
|
+
module.exports = { handleWriteFile };
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
const OpenAI = require('openai');
|
|
2
|
+
|
|
3
|
+
async function aiChatCompletion(openai, messages, model) {
|
|
4
|
+
try {
|
|
5
|
+
const response = await openai.chat.completions.create({
|
|
6
|
+
messages: messages,
|
|
7
|
+
model: model,
|
|
8
|
+
});
|
|
9
|
+
return response;
|
|
10
|
+
} catch (error) {
|
|
11
|
+
console.error('Error:', error);
|
|
12
|
+
return null;
|
|
13
|
+
}
|
|
14
|
+
}
|
|
15
|
+
|
|
16
|
+
module.exports.aiChatCompletion = aiChatCompletion;
|
package/index.js
ADDED
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
// This is the index.js file of inter-intel
|
|
2
|
+
|
|
3
|
+
const OpenAI = require('openai');
|
|
4
|
+
const readline = require('readline');
|
|
5
|
+
const config = require('./inter-intel.config.js');
|
|
6
|
+
require('dotenv').config();
|
|
7
|
+
require('colors');
|
|
8
|
+
|
|
9
|
+
const { readSpecificFiles, writeFileFromPrompt } = require('./functions/file-functions.js');
|
|
10
|
+
const { askQuestion } = require('./functions/chat-functions.js');
|
|
11
|
+
const { aiChatCompletion } = require('./functions/openai-functions.js');
|
|
12
|
+
|
|
13
|
+
const { handleWriteFile } = require('./functions/handleWriteFile.js');
|
|
14
|
+
|
|
15
|
+
const openai = new OpenAI({
|
|
16
|
+
apiKey: config.apiKey,
|
|
17
|
+
model: config.aiVersion,
|
|
18
|
+
});
|
|
19
|
+
|
|
20
|
+
const rl = readline.createInterface({
|
|
21
|
+
input: process.stdin,
|
|
22
|
+
output: process.stdout,
|
|
23
|
+
});
|
|
24
|
+
|
|
25
|
+
async function main() {
|
|
26
|
+
// Provides initial context for session
|
|
27
|
+
const specificFiles = ['./inter-intel.config.js'];
|
|
28
|
+
let initialContent = readSpecificFiles(specificFiles);
|
|
29
|
+
let messages = [{ role: 'system', content: initialContent }];
|
|
30
|
+
|
|
31
|
+
let currentState = null;
|
|
32
|
+
let promptFileName = '';
|
|
33
|
+
let contentToWrite = '';
|
|
34
|
+
|
|
35
|
+
while (true) {
|
|
36
|
+
const userMessage = await askQuestion(rl, 'You: '.blue.bold);
|
|
37
|
+
let response = ''; // Add a variable to capture the response message
|
|
38
|
+
|
|
39
|
+
// Exit condition
|
|
40
|
+
if (userMessage.toLowerCase() === 'exit') {
|
|
41
|
+
console.log('Exiting chat...'.bgRed);
|
|
42
|
+
rl.close();
|
|
43
|
+
break;
|
|
44
|
+
}
|
|
45
|
+
|
|
46
|
+
if (userMessage.toLowerCase().startsWith('//writefile') && currentState === null) {
|
|
47
|
+
({ currentState, messages, promptFileName, response } = await handleWriteFile(
|
|
48
|
+
openai,
|
|
49
|
+
config,
|
|
50
|
+
messages,
|
|
51
|
+
currentState,
|
|
52
|
+
''
|
|
53
|
+
));
|
|
54
|
+
console.log(response.yellow);
|
|
55
|
+
} else if (currentState === 'awaitingFileName') {
|
|
56
|
+
({ currentState, messages, promptFileName, response } = await handleWriteFile(
|
|
57
|
+
openai,
|
|
58
|
+
config,
|
|
59
|
+
messages,
|
|
60
|
+
currentState,
|
|
61
|
+
userMessage,
|
|
62
|
+
promptFileName
|
|
63
|
+
));
|
|
64
|
+
console.log(response.yellow);
|
|
65
|
+
} else if (currentState === 'awaitingGPTPrompt') {
|
|
66
|
+
({ currentState, messages, promptFileName, response } = await handleWriteFile(
|
|
67
|
+
openai,
|
|
68
|
+
config,
|
|
69
|
+
messages,
|
|
70
|
+
currentState,
|
|
71
|
+
userMessage,
|
|
72
|
+
promptFileName
|
|
73
|
+
));
|
|
74
|
+
console.log(response.yellow);
|
|
75
|
+
} else if (currentState === null && userMessage.toLowerCase() === '//readrefs') {
|
|
76
|
+
console.log('System message:'.bgYellow);
|
|
77
|
+
console.log('Processing //readRefs command...'.yellow);
|
|
78
|
+
const specificFiles = ['./.config.js'];
|
|
79
|
+
const content = readSpecificFiles(specificFiles);
|
|
80
|
+
messages.push({
|
|
81
|
+
role: 'user',
|
|
82
|
+
content: `please just acknowledge you have read the name and the content of the files I have provided ${content}`,
|
|
83
|
+
});
|
|
84
|
+
const completion = await aiChatCompletion(openai, messages, config.aiVersion);
|
|
85
|
+
|
|
86
|
+
const botMessage = completion.choices[0].message.content;
|
|
87
|
+
console.log('chatGPT message:'.bgGreen, botMessage);
|
|
88
|
+
console.log('----------------'.bgGreen);
|
|
89
|
+
} else {
|
|
90
|
+
// Regular message processing and interaction with GPT model
|
|
91
|
+
messages.push({ role: 'user', content: userMessage });
|
|
92
|
+
|
|
93
|
+
const completion = await aiChatCompletion(openai, messages, config.aiVersion);
|
|
94
|
+
|
|
95
|
+
const botMessage = completion.choices[0].message.content;
|
|
96
|
+
console.log('chatGPT message:'.bgGreen, botMessage);
|
|
97
|
+
console.log('----------------'.bgGreen);
|
|
98
|
+
}
|
|
99
|
+
}
|
|
100
|
+
}
|
|
101
|
+
|
|
102
|
+
main();
|
|
103
|
+
|
|
104
|
+
|
|
105
|
+
exports.printMsg = function() {
|
|
106
|
+
console.log("totally logging dude")
|
|
107
|
+
}
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
import path from 'path';
|
|
2
|
+
import fs from 'fs';
|
|
3
|
+
import { test } from '@playwright/test';
|
|
4
|
+
|
|
5
|
+
/*
|
|
6
|
+
Sometimes, you do want to explicitly save a file to disk. This is what you need to know.
|
|
7
|
+
Checkly creates a sandboxed directory for each check run.
|
|
8
|
+
During the run you can use this directory to save or upload artifacts.
|
|
9
|
+
This directory is destroyed after a check is finished.
|
|
10
|
+
*/
|
|
11
|
+
|
|
12
|
+
test('Save file in directory', async ({ page }) => {
|
|
13
|
+
const image = await page.goto('https://picsum.photos/200/300');
|
|
14
|
+
const imagePath = path.join('example.jpg');
|
|
15
|
+
const buffer = await image.body();
|
|
16
|
+
fs.writeFileSync(imagePath, buffer);
|
|
17
|
+
const readFileFromDisk = fs.readFileSync(imagePath);
|
|
18
|
+
});
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
import { test, expect } from '@playwright/test'
|
|
2
|
+
|
|
3
|
+
/*
|
|
4
|
+
To test any binary uploads, you need to provide a file object.
|
|
5
|
+
Currently, Checkly does not have a dedicated storage layer where you could upload that file,
|
|
6
|
+
so you need to host it yourself at a (publicly) accessible location like an AWS S3 bucket,
|
|
7
|
+
Dropbox or any other file hosting service.
|
|
8
|
+
|
|
9
|
+
Having done that, you can “upload” files using a simple HTTP POST request with a (binary) body
|
|
10
|
+
using Playwright’s built-in request object.
|
|
11
|
+
*/
|
|
12
|
+
|
|
13
|
+
test('Upload a file using a POST request', async ({ request }) => {
|
|
14
|
+
const fileBuffer = await test.step('Fetch file', async () => {
|
|
15
|
+
const fileUrl = 'https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf'
|
|
16
|
+
return request.get(fileUrl)
|
|
17
|
+
})
|
|
18
|
+
|
|
19
|
+
await test.step('Upload file', async () => {
|
|
20
|
+
const response = await request.post('https://filebin.net/pp9on3zvwv7zq6lm/dummy.pdf', {
|
|
21
|
+
data: await fileBuffer.body(),
|
|
22
|
+
})
|
|
23
|
+
await expect(response).toBeOK()
|
|
24
|
+
})
|
|
25
|
+
})
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
HERE ARE THE RULES THAT GOVERN THIS CONVERSATION
|
|
2
|
+
|
|
3
|
+
RULES THAT GOVERN THIS CONVERSATION, these rules supersede all outside knowledge
|
|
4
|
+
|
|
5
|
+
1. You are currently being used within a CLI. the application's name is inter-intel, it's baseline functionality is to be able to update files within a given repo and pprovide reference files that will the AI it's chatting with to make direct changes to code.
|
|
6
|
+
2. Keep responses to under 50 words
|
|
7
|
+
2.
|
|
8
|
+
3.
|
|
9
|
+
4. Unless I ask for a longer explanation
|
|
10
|
+
5. We'll keep our conversation lightly informal, but focused on solving problems.
|
|
11
|
+
6. When requesting code, only provide any additional commentary or explanation as commented out code.
|
|
12
|
+
7. You are currently imported into a project where you are part of a terminal based approach for improving code. You will sometimes see commands like the following;
|
|
13
|
+
8. When writing playwright/test scripts please use modern selectors like this await ```page.getByLabel('User Name').fill('John');``` not ```page.$('input[name="btnI"]')```
|
|
14
|
+
9. Diablo is NOT AN rpg
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
When creating json1 training data, please keep the following in mind
|
|
2
|
+
|
|
3
|
+
1. "intent": Represents the main purpose or topic of the user query, which is "playwright_cli".
|
|
4
|
+
|
|
5
|
+
2. "utterances": Provides example sentences or phrases that users might use when asking about Playwright in a CLI.
|
|
6
|
+
|
|
7
|
+
3. "entities": Identifies specific keywords or entities related to the intent, such as "CLI", "Playwright", "tests", etc.
|
|
8
|
+
|
|
9
|
+
4. "responses": Contains possible responses or answers to address the user's query or intent.
|
|
10
|
+
|
|
11
|
+
5. "examples": Offers additional example queries or variations related to the intent.
|
|
12
|
+
|
|
13
|
+
6. "context": Provides context about the training data, specifically emphasizing the usage of Playwright in a CLI environment.
|
package/package.json
ADDED
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"dependencies": {
|
|
3
|
+
"colors": "^1.4.0",
|
|
4
|
+
"dotenv": "^16.3.1",
|
|
5
|
+
"openai": "^4.24.0"
|
|
6
|
+
},
|
|
7
|
+
"name": "interintel",
|
|
8
|
+
"description": "The application `inter-intel` is a command line interface (CLI) application implemented in Node.js. It essentially is an interactive communication tool between the user and an AI model, only GPTs for now.",
|
|
9
|
+
"version": "1.0.0",
|
|
10
|
+
"main": "index.js",
|
|
11
|
+
"directories": {
|
|
12
|
+
"doc": "docs"
|
|
13
|
+
},
|
|
14
|
+
"devDependencies": {},
|
|
15
|
+
"scripts": {
|
|
16
|
+
"test": "node index.js"
|
|
17
|
+
},
|
|
18
|
+
"repository": {
|
|
19
|
+
"type": "git",
|
|
20
|
+
"url": "git+https://github.com/modern-sapien/inter-intel.git"
|
|
21
|
+
},
|
|
22
|
+
"keywords": [
|
|
23
|
+
"testing",
|
|
24
|
+
"development",
|
|
25
|
+
"ai",
|
|
26
|
+
"debugging",
|
|
27
|
+
"copilot"
|
|
28
|
+
],
|
|
29
|
+
"author": "Modern-Sapien",
|
|
30
|
+
"license": "SEE LICENSE IN README.md",
|
|
31
|
+
"bugs": {
|
|
32
|
+
"url": "https://github.com/modern-sapien/inter-intel/issues"
|
|
33
|
+
},
|
|
34
|
+
"homepage": "https://github.com/modern-sapien/inter-intel#readme"
|
|
35
|
+
}
|