ykdojo / kaguya Goto Github PK

You need ChatGPT's plugin dev access to set this up.

Mention this and maybe add a link to their waitlist too.

This should be ok to do since readMultipleFiles can be used for reading a single file. The new endpoint should be called readFiles.

Now that OpenAI has Custom Instructions (a persistent instruction for new conversations), we should show a recommended custom instruction on README.

Currently, I have this:

When editing a file, use search and replace and NOT updateWholeFile unless we're dealing with a very small file. Confirm with me before you edit a file.

When you have output from Kaguya, there's no need to repeat everything from there. Instead, you can summarize it concisely.

When you want to use executeCommand in a subdirectory, make sure to cd there first every time.

I might refine it as I go, but it should be good enough for now.

Move the API endpoints section into a separate file and add more details about how to get started with Kaguya - install it as a ChatGPT plugin and move all files you want ChatGPT to have access to, to the FILES directory.

• Best to keep each file under 100 lines of code, particularly for writing
• Writing more than ~80 lines of code at once is not recommended. It's slow and it might not even be able to finish the task.
• You can have it read more code though. However, reading more than 500-600 lines of code at once is not recommended.
• If the target file you want to edit is long, you may want to explicitly ask it to use search and replace.
• It may not get the intention of your instructions right away. It's meant to be a conversational tool.
• If the assistant starts hallucinating, it may be helpful to start a new conversation or limit the length of each file being loaded.

We have Next.js's default index page on the index page.

We should change that

I was exploring how Kaguya can be added as plugin at https://open-assistant.io/ or gpt4all

Can someone help me out?

Running the docker application on Windows 10 produces the following error:

> hako-next@0.1.0 dev /kaguya
> if [ -f /.dockerenv ]; then next dev; else echo 'Error: Please run this script inside a Docker container.' && exit 1; fi
Watchpack Error (watcher): Error: EACCES: permission denied, watch '/root'
Watchpack Error (initial scan): Error: EACCES: permission denied, scandir '/root'
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
error - Project directory could not be found, restart Next.js in your new directory

I am attempting to integrate Kaguya with GPTs as an action, but I am encountering an issue related to the HTTP and HTTPS protocols.

Steps to Reproduce:

1. I ran the Kaguya plugin and successfully accessed it at http://localhost:3000.

2. I copied the contents from http://localhost:3000/openapi.yaml and pasted it into GPTs actions.

3. Upon doing so, I received the following warnings:

   Warnings
   None of the provided servers is under the root origin https://localhost
   Server URL http://localhost:3000 is not under the root origin https://localhost; ignoring it
   

Issue:
It appears that there is a protocol mismatch issue, as Kaguya is running on HTTP and GPTs actions seem to require HTTPS. As a result, the server URL is being ignored due to not being under the root origin https://localhost.

Questions:

1. Has anyone successfully integrated Kaguya as an action in GPTs?
2. Although Kaguya is originally intended as a ChatGPT plugin, I believe there should be a close similarity in its integration with GPTs. If it is indeed feasible to run it as a GPTs action, how should the yaml be modified to address the HTTP/HTTPS protocol mismatch?

Any guidance or suggestions on resolving this issue would be greatly appreciated. Thank you for your support and for the development of this innovative tool.

Best regards,

The demo videos should be right after the initial intro so that we can show people the potential of this project more quickly.

So people can ask questions about it.

It'd probably be integrated into this server: https://discord.com/invite/nNtVfKddDD

There is an error here
https://github.com/ykdojo/kaguya/blob/master/pages/api/deleteDirectory.js#L5

It tries to modify directoryPath right in parameters
I guess ChatGPT wrote that :D

I just changed it from to

function deleteDirectoryRecursively(path.join(process.cwd(), 'FILES', directoryPath)) {

to

function deleteDirectoryRecursively(directoryPath) {
  directoryPath = path.join(process.cwd(), 'FILES', req.query.directoryPath);

The pinned messages on #kaguya channel on our Discord (https://discord.com/invite/nNtVfKddDD) should be a good reference for this.

Rather than a POST operation

Apply for ChatGPT developer permissions？

this makes sense given the files. however, this means the app is not built. Am i correct? I wanted to use this but it seems the code is missing lol

if I am just super early or something, that is cool! just now sure what is going on here as there is not any code representative of your demos. Am I doing something wrong?

I've been trying to run this and for the life of me I cannot figure out a fix. I'm positive I'm overlooking something.

This is the output when I run the docker.sh:

0.72 Setting up python3.9-minimal (3.9.2-1) ...
30.79 Traceback (most recent call last):
30.79   File "/usr/lib/python3.9/py_compile.py", line 215, in <module>
30.79     sys.exit(main())
30.79   File "/usr/lib/python3.9/py_compile.py", line 207, in main
30.79     compile(filename, doraise=True)
30.79   File "/usr/lib/python3.9/py_compile.py", line 172, in compile
30.79     importlib._bootstrap_external._write_atomic(cfile, bytecode, mode)
30.79   File "<frozen importlib._bootstrap_external>", line 126, in _write_atomic
30.79 PermissionError: [Errno 13] Permission denied: '/usr/lib/python3.9/__pycache__/__future__.cpython-39.pyc.139771950211344'
30.79 dpkg: error processing package python3.9-minimal (--configure):
30.79  installed python3.9-minimal package post-installation script subprocess returned error exit status 1
30.80 Errors were encountered while processing:
30.80  python3.9-minimal
30.85 E: Sub-process /usr/bin/dpkg returned an error code (1)
------
ERROR: failed to solve: executor failed running [/bin/sh -c apt-get update &&     apt-get install -y wget gnupg &&     wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - &&     echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" | tee /etc/apt/sources.list.d/google-chrome.list &&     apt-get update &&     apt-get install -y     python3 python3-pip git curl build-essential gfortran ffmpeg firefox-esr unzip     google-chrome-stable &&     apt-get clean &&     rm -rf /var/lib/apt/lists/*]: exit code: 100
docker: invalid reference format: repository name must be lowercase.
See 'docker run --help'.

It seemed to keep hanging and erroring out at:

=> [ 6/16] RUN apt-get update && apt-get install -y python3 python3-pip git curl build-essential gfortran && apt-get clean && rm -rf /var/lib/apt/lists/*

Any ideas on what could be going on?

=> => writing image sha256:0d5e90bae6e6ca47d571e4e99542de91525e1643d6fcddabc41aae053ddbef21 0.0s
=> => naming to docker.io/library/kaguya 0.0s

[email protected] dev /kaguya
if [ -f /.dockerenv ]; then next dev; else echo 'Error: Please run this script inside a Docker container.' && exit 1; fi

Watchpack Error (watcher): Error: EACCES: permission denied, watch '/root'
Watchpack Error (initial scan): Error: EACCES: permission denied, scandir '/root'
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
[Error: EACCES: permission denied, mkdir '/kaguya/.next'] {
errno: -13,
code: 'EACCES',
syscall: 'mkdir',
path: '/kaguya/.next'
}