intelligencedev / eternal Goto Github PK

The current implementation does not correctly format large code blocks as they are being generated due to the closing tag not being generated by LLM. We need a method to close the blocks as the code is being generated so they display properly from the start.

We also need a copy button on the top right of the block so the end user can easily copy the code.

The copy button will need to be implemented in the chat template:

https://github.com/intelligencedev/eternal/blob/main/public/templates/chat.html

We need to implement a code runner solution that is sandboxed in a secure environment. Most applications in this space use a container for this purpose but there may be other options. We should explore an option that does not require a third party OS install such as WASM, but that may not be ideal. Some options to research:

• WASM
• MicroVM
• Container
• A secure sandbox like Firejail or similar alternatives that works across Linux, Mac and Windows. This is unlikely, but just leaving here for reference.

We also want to be able to execute code generated by the LLM via the frontend by triggering an event using a play button that gets injected into code blocks. That may need to be a separate issue but let's leave the idea here for now.

The tooling is there to apply custom prompt templates during inference workflows. While the model configs contain local templates that could be configured via the config.yml, we should add more advanced templates such as Chain of Thought, etc. to prepare for the advanced agent workflows that will be reimplemented soon.

Eternal currently requires some manual tweaking to build properly due to the lack of proper automation for the build process. This issue serves as a generic reminder that we need to put this on autopilot and have a CI pipeline built to automatically build and publish new releases.

When a model finishes downloading it should trigger a callback to update its state in the DB and frontend so we do not have to restart the application to be able to use it.

Implement the image generation feature. The obvious choice is Stable Diffusion but there is more competition in that space. We will start with Stable Diffusion, but also investigate how we could potentially add support for other image gen models and backends.

Eternal will require third party application installations for the various tools that will not be embedded. Currently, the web tool requires a headless Chrome install. Chromium would be ideal but it has not been tested yet. We need a method to detect if this app is installed in the end user's OS, and if not, install it.

The Go ChromeDP package may have methods to do this. Otherwise we will implement our own.

If its possible to do this via the package, then the implementation should go in the web tool:

https://github.com/intelligencedev/eternal/blob/main/pkg/web/web.go

Otherwise, a generic method in the main app will suffice to run the process for any third party dependency.