editor-code-assistant/eca

AI Summary: This GitHub issue proposes adding support for custom hooks, similar to Anthropic's implementation, to allow users to inject logic at specific points. Suggested hook events include `preToolCall`, `postToolCall`, `prePrompt`, and `postPrompt`, which are noted as straightforward to integrate. The issue also raises a UX question about how to inform users when a hook is executing, potentially via a customizable system message.

AI Summary: The issue requests adding Nix/flake support for the application to enable installation via Nix. An attempt to create a flake failed because the build process lacked network access to fetch Clojure's Git dependencies, which needs to be addressed for successful packaging.

AI Summary: The issue describes a bug where the user interface icon for a running toolCall (specifically ECA) remains in a "loading" state even after the user has initiated a stop command. This creates a misleading visual indication that the process is still active, and the suggested resolution is to update the icon to clearly reflect a "stopped" status.

AI Summary: The user is requesting a new feature to enable the ECA application, specifically its `hato-client`, to route its API calls through an HTTP/HTTPS proxy. They note that the application currently does not respect standard environment variables like `HTTP_PROXY` or `HTTPS_PROXY`, which is a critical requirement for users operating in corporate environments that mandate proxy usage for external network access.

AI Summary: The `repoMap` feature, which provides file context to an LLM using `git ls-files`, becomes too large for huge projects, leading to inefficient LLM processing. The issue proposes implementing a heuristic to truncate or reduce the number of files in the `repoMap` to a more manageable size.

AI Summary: Implement a feature to resume previous chats in the Editor Code Assistant (ECA) application. This involves saving chat history globally (e.g., in ~/.cache/eca/projects), and adding a command (e.g., `/resume`) to allow users to select and resume a previous chat session. The user interface for selecting the chat needs to be designed.

AI Summary: Implement dynamic loading of model information for the Editor Code Assistant (ECA) project, replacing the current hardcoded values with data fetched from the models.dev API. This involves modifying the Clojure codebase to retrieve and parse JSON data from the API and integrate it into the ECA's database.

AI Summary: Implement unit and integration tests for the core functionality of the ECA (Editor Code Assistant) project. Unit tests should cover core components, while integration tests (future work) should verify interaction with other systems, potentially mirroring the approach of clojure-lsp's integration tests.

AI Summary: Implement support for LLMs that offer 'thinking' or 'reasoning' capabilities within the Editor Code Assistant (ECA) project. This involves enhancing the ECA to handle and display the reasoning process of these LLMs, allowing users to see the LLM's thought process before generating a response, improving context awareness and preventing undesired outputs.

AI Summary: Improve the context handling in the Editor Code Assistant (ECA) project to prevent exceeding the LLM's context window limit. This involves researching and implementing either a repo-map approach (similar to Aider) or an embedding vector approach (similar to Cursor) to selectively send relevant code snippets to the LLM, rather than sending entire files.

AI Summary: Refactor the existing README documentation for the Editor Code Assistant (ECA) project into separate, more organized documentation files within a `docs/` folder, potentially using a tool like mkdocs-material to generate a website for improved accessibility and readability.